Search / org.agile-today/agile-today
Agile Today
R0· no sign-inProject management methodology graph: route planning, stage-gate decisions and plan checks.
v2.3.2 · active · website · descriptor JSON · versions
Search / org.agile-today/agile-today
R0· no sign-inProject management methodology graph: route planning, stage-gate decisions and plan checks.
v2.3.2 · active · website · descriptor JSON · versions
{
"mcpServers": {
"agile-today": {
"type": "http",
"url": "https://agile-today.org/api/mcp?src=mcp-registry"
}
}
}claude mcp add --transport http agile-today https://agile-today.org/api/mcp?src=mcp-registry[mcp_servers.agile-today]
url = "https://agile-today.org/api/mcp?src=mcp-registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"agile-today": {
"type": "remote",
"url": "https://agile-today.org/api/mcp?src=mcp-registry",
"enabled": true
}
}
}{
"mcpServers": {
"agile-today": {
"type": "http",
"url": "https://agile-today.org/api/mcp?src=mcp-registry"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=agile-today&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYWdpbGUtdG9kYXkub3JnL2FwaS9tY3A%2Fc3JjPW1jcC1yZWdpc3RyeSJ9"
}{
"servers": {
"agile-today": {
"type": "http",
"url": "https://agile-today.org/api/mcp?src=mcp-registry"
}
}
}{
"mcpServers": {
"agile-today": {
"httpUrl": "https://agile-today.org/api/mcp?src=mcp-registry"
}
}
}extensions:
"agile-today":
enabled: true
name: "agile-today"
type: streamable_http
uri: "https://agile-today.org/api/mcp?src=mcp-registry"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every useauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations8 of 8 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 4,897 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes7 tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageexplain_nodechangedinput schemasearch_graphchangedinput schemavalidate_planchangedinput schemacheck_mixchangedinput schemawhen_to_usechangedinput schemacheck_gatechangedinput schemaplan_projectchangedinput schemaFull history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website +reachable +uptime-100% +updated-15d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://agile-today.org/api/mcp?src=mcp-registry streamable-http | none | yes | 100% | 318 ms | 2026-07-28 | 2026-10-20 |
check_gateread-only | 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 gate → Conditional go; a waiver with both → Go with the Waiver modifier (under regulation a waived critical artifact stays Conditional go until the deviation is recorded with the quality approval); optional gaps are notes. Modifiers: Work started without the gate, Overdue, Stale, Waiver. gate.deciders decide, gate.advisors take part. A disproved key product hypothesis is a Recycle, not a Stop: pass earlier_stage_invalid:true with invalid_stage:'st.discovery'. At G8 (go / no-go), work_started_beyond:true means production was changed before the decision: Hold (R3), not a Go with a modifier. Call without evidence to list what the gate needs. Returns a receipt hash of the inputs. |
check_mixread-only | 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 of severity warning (e.g. output over outcome on a client contract) does not change ok. |
explain_noderead-only | 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. |
list_contextread-only | 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_projectread-only | 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 here (context rule, flag or gate-critical artifact), at most 8 work items per stage (producers of the gate's critical artifacts first, then context rules, then flags). |
search_graphread-only | Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated). Returns total and the best matches. |
validate_planread-only | 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 gates, a gate after the step it authorises (G8 after the cutover), antipatterns, avoid or not-applicable items. Warnings: duplicates, redundant alternatives, early work, a cutover with no G8 or go / no-go meeting before it, antipatterns of severity warning. 'Shadow start' looks at the order: G4 or G5 must come before the first build step. 'expected' lists gate evidence not yet produced by earlier steps. |
when_to_useread-only | 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. |
Schemas: list_tools.
{
"name": "org.agile-today/agile-today",
"title": "Agile Today",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://agile-today.org/api/mcp?src=mcp-registry",
"type": "streamable-http"
}
],
"version": "2.3.2",
"websiteUrl": "https://agile-today.org/en/mcp",
"description": "Project management methodology graph: route planning, stage-gate decisions and plan checks."
}