# Agile Today (remote · agile-today.org)

Project management methodology graph: route planning, stage-gate decisions and plan checks.

- Trust score: 87/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agile-today.org`: 87/100 (this document), [markdown](https://verifymcp.io/servers/org-agile-today-agile-today/api-mcp.md), [page](https://verifymcp.io/servers/org-agile-today-agile-today/api-mcp)

## Channel facts

- Endpoint: `https://agile-today.org/api/mcp?src=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1669 tokens (~208/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Agile Today MCP server?

Agile Today is a hosted endpoint at https://agile-today.org/api/mcp?src=mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-agile-today-agile-today 'https://agile-today.org/api/mcp?src=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "org-agile-today-agile-today": {
      "url": "https://agile-today.org/api/mcp?src=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-agile-today-agile-today": {
      "type": "http",
      "url": "https://agile-today.org/api/mcp?src=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-agile-today-agile-today]
url = "https://agile-today.org/api/mcp?src=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-agile-today-agile-today": {
      "type": "remote",
      "url": "https://agile-today.org/api/mcp?src=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-agile-today-agile-today --url 'https://agile-today.org/api/mcp?src=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-agile-today-agile-today:
    url: "https://agile-today.org/api/mcp?src=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "org-agile-today-agile-today": {
      "Transport": "http",
      "Url": "https://agile-today.org/api/mcp?src=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-agile-today-agile-today -t streamable-http -u 'https://agile-today.org/api/mcp?src=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "org-agile-today-agile-today": {
      "type": "http",
      "url": "https://agile-today.org/api/mcp?src=mcp-registry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 87, 0)

- [functional] Stability: pass → 0.97

### 2026-11-02 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `list_context` (~58 tokens)

List context options

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.

Input parameters:

- `lang` (string): Answer language, default en

### `plan_project` (~233 tokens)

Plan a project route

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).

Input parameters:

- `context` (object): Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.
- `format` (string): Default compact
- `include` (array): Default all four
- `lang` (string): Answer language, default en
- `min_strength` (string): Default: core for all stages, all when stages are given
- `stages` (array): Stage ids or codes, e.g. ['st.analysis','design']. Default: all

### `check_gate` (~585 tokens)

Check a 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 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.

Input parameters:

- `business_case_valid` (boolean): false → Stop
- `context` (object): Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.
- `days_in_stage` (number)
- `earlier_stage_invalid` (boolean): true → Recycle; the answer names the stage to return to
- `evidence` (object): Map artifact id → state or {state, reason, ref, by, date}. A waiver is {state:'waived', reason, by}: by is the role id of a decider of this gate (see gate.deciders, e.g. r.client_owner) or 'name, rol…
- `gate` (string, required): Gate id, e.g. g.g5
- `grace_days` (number): Overrides both limits. Default: 80% of planned_stage_days, else by approach (predictive/hybrid 10, agile/flow 5); required evidence then waits twice as long
- `invalid_artifact` (string): With earlier_stage_invalid: the artifact that is no longer true, to find where to return
- `invalid_stage` (string): With earlier_stage_invalid: the stage to return to, if known
- `lang` (string): Answer language, default en
- `planned_stage_days` (number): Planned length of the stage in days. With it, missing critical evidence is overdue after 80% of it and missing required evidence after all of it
- `work_started_beyond` (boolean): True if work of later stages already started (adds the 'work started without the gate' modifier; at G8 it is a Hold)

### `when_to_use` (~142 tokens)

When to use an item

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.

Input parameters:

- `context` (object): Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.
- `id` (string, required): e.g. t.planning_poker, p.stage_gating, x.velocity_kpi
- `lang` (string): Answer language, default en

### `check_mix` (~154 tokens)

Check a mix of practices

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.

Input parameters:

- `context` (object): Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.
- `ids` (array, required)
- `lang` (string): Answer language, default en

### `validate_plan` (~246 tokens)

Validate a 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 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.

Input parameters:

- `context` (object): Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.
- `evidence` (object): Artifacts that already exist
- `lang` (string): Answer language, default en
- `steps` (array, required)

### `search_graph` (~69 tokens)

Search the graph

Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated). Returns total and the best matches.

Input parameters:

- `lang` (string): Answer language, default en
- `limit` (integer)
- `query` (string, required)
- `type` (string)

### `explain_node` (~88 tokens)

Explain a 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.

Input parameters:

- `direction` (string)
- `id` (string, required)
- `lang` (string): Answer language, default en
- `limit` (integer)
- `link_types` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-agile-today-agile-today/api-mcp#diagnostics

## Score history

- 2026-11-05: 87
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 87
- 2026-10-31: 86
- 2026-10-30: 86
- 2026-10-29: 86
- 2026-10-28: 85
- 2026-10-27: 85
- 2026-10-26: 84
- 2026-10-25: 84
- 2026-10-24: 83
- 2026-10-23: 83
- 2026-10-22: 82
- 2026-10-21: 82
- 2026-10-20: 81
- 2026-10-19: 81
- 2026-10-18: 80
- 2026-10-17: 80
- 2026-10-16: 79
- 2026-10-15: 79
- 2026-10-14: 79
- 2026-10-13: 78
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-06: 75
- 2026-10-04: 74
- 2026-10-03: 73

## Common questions

### What is the Agile Today MCP server?

Agile Today is an MCP server listed in the public MCP registry as org.agile-today/agile-today. Project management methodology graph: route planning, stage-gate decisions and plan checks. This page covers its hosted endpoint (https://agile-today.org/api/mcp?src=mcp-registry).

### Is the Agile Today MCP server safe to use?

Agile Today scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Agile Today MCP server expose?

Agile Today exposes 8 tools: list_context, plan_project, check_gate, when_to_use, check_mix, and 3 more. Their descriptions and schemas cost roughly 1,575 tokens of context every time the server is loaded.

### Does the Agile Today MCP server require authentication?

No. We connected to Agile Today without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agile Today MCP server still maintained?

Agile Today is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agile-today.org/api/mcp?src=mcp-registry
- Website: https://agile-today.org/en/mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-agile-today-agile-today/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-agile-today-agile-today/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-agile-today-agile-today/api-mcp