org.agile-today/agile-today · v2.3.2 · ecommerce
Agile Today is healthy: it completed an MCP handshake in 2429 ms and exposes 8 tools.
Project management methodology graph: route planning, stage-gate decisions and plan checks.
Endpoint: https://agile-today.org/api/mcp?src=mcp-registry (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 8 |
| Latency | 2429 ms |
| Last checked (UTC) | 2026-10-16T19:30:44.969Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T19:30:44.969Z | Healthy | 2429 | |
| 2026-10-15T13:00:17.475Z | Healthy | 1544 |
list_context | Call first. Returns the context dimensions and flags (with defaults and how many rules each flag drives), stages, gates, evidence states and levels, the gate outcome precedence and the suggested workflow. |
plan_project | Route from presale to closure for a project context. Default is compact (ids by strength + a names dictionary, core items and gate evidence for all stages, about 6–10k characters). Ask for one stage with stages:['st.design'] and format:'full' for reasons, avoid texts and gate details. 'core' = do it |
check_gate | Evaluates gate g.g0 … g.g10 against your evidence. Outcome precedence: Stop > Recycle > Hold > Conditional go > Go, with the rule that fired (outcome_reason). Critical evidence missing or stale → Hold; required non-critical missing, or a waiver without a reason or an approver who decides at this gat |
when_to_use | For one event, practice, technique, notation, tool, artifact or antipattern: does it fit this context (fits / avoid / not_applicable / antipattern), its strength and why, alternatives and their group advice, risks, and which gates require it. |
check_mix | For a set of ids: antipatterns in the set and detected by rules, conflicts, redundant alternatives (e.g. seven estimation methods), items to avoid or not applicable here, risks, missing inputs and suggested additions. ok = no antipatterns, conflicts, avoid or not-applicable items; a detected pattern |
validate_plan | Checks an ordered list of steps (stages, gates, events, practices, techniques, notations, artifacts). Errors: empty plan, unknown ids, non-step types, stage order (analysis and design work planned early is only a warning 'early'; building before G3–G5 is an order error), contract after delivery gate |
search_graph | Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated). Returns total and the best matches. |
explain_node | One node with its description, conditions, source, level and its links grouped by type, each with a link id (Lxxxx) to cite. Filter with link_types, direction and limit. |