Agile Today
by agile-today.org in Other
Project management methodology graph: route planning, stage-gate decisions and plan checks.
https://agile-today.org/api/mcp?src=mcp-registry- Tools
- 8
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 412 ms
- 1.4 s slowest 5%
- Last check
- Passed
- 1 h ago, next in 5 h
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"agile-today": {
"type": "http",
"url": "https://agile-today.org/api/mcp?src=mcp-registry"
}
}
}8 tools
- 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…
- 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…
- 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…
- 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)…
- 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.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 1 h ago | Passed | 200 | 292 ms |
| 10 h ago | Passed | 200 | 294 ms |
| 19 h ago | Passed | 200 | 413 ms |
| 29 h ago | Passed | 200 | 262 ms |
| 38 h ago | Passed | 200 | 623 ms |
Show 10 older checks
| 2 days ago | Passed | 200 | 1.1 s |
| 2 days ago | Passed | 200 | 1.4 s |
| 3 days ago | Passed | 200 | 280 ms |
| 3 days ago | Passed | 200 | 423 ms |
| 4 days ago | Passed | 200 | 658 ms |
| 4 days ago | Passed | 200 | 412 ms |
| 4 days ago | Passed | 200 | 266 ms |
| 5 days ago | Passed | 200 | 1.4 s |
| 5 days ago | Passed | 200 | 1.4 s |
| 6 days ago | Passed | 200 | 634 ms |