# Agenda Intelligence MD (remote · agent-output-verification-a2a.vassiliy-lakhonin.workers.dev)

Evidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev`: 79/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agenda-intelligence-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agenda-intelligence-a2a)
- remote · `agent-financial-guard-a2a.vassiliy-lakhonin.workers.dev`: 69/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agent-financial-guard-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agent-financial-guard-a2a)
- remote · `agent-output-verification-a2a.vassiliy-lakhonin.workers.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agent-output-verification-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agent-output-verification-a2a)
- remote · `agentic-interaction-trust-a2a.vassiliy-lakhonin.workers.dev`: 77/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agentic-interaction-trust-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agentic-interaction-trust-a2a)
- remote · `cis-secondary-sanctions-a2a.vassiliy-lakhonin.workers.dev`: 76/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/cis-secondary-sanctions-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/cis-secondary-sanctions-a2a)
- remote · `corridor-sanctions-assistant-a2a.vassiliy-lakhonin.workers.dev`: 79/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/corridor-sanctions-assistant-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/corridor-sanctions-assistant-a2a)
- remote · `critical-minerals-due-diligence-a2a.vassiliy-lakhonin.workers.dev`: 75/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/critical-minerals-due-diligence-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/critical-minerals-due-diligence-a2a)
- remote · `dual-use-technology-export-a2a.vassiliy-lakhonin.workers.dev`: 75/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/dual-use-technology-export-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/dual-use-technology-export-a2a)
- remote · `gulf-maritime-exposure-a2a.vassiliy-lakhonin.workers.dev`: 78/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/gulf-maritime-exposure-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/gulf-maritime-exposure-a2a)
- remote · `kazakhstan-market-entry-readiness-a2a.vassiliy-lakhonin.workers.dev`: 75/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/kazakhstan-market-entry-readiness-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/kazakhstan-market-entry-readiness-a2a)
- remote · `m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev`: 69/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/m2m-escrow-arbiter-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/m2m-escrow-arbiter-a2a)
- remote · `middle-corridor-deal-risk-gate-a2a.vassiliy-lakhonin.workers.dev`: 78/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/middle-corridor-deal-risk-gate-a2a.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/middle-corridor-deal-risk-gate-a2a)
- pypi · `agenda-intelligence-md`: 85/100, [markdown](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agenda-intelligence-md.md), [page](https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agenda-intelligence-md)

## Channel facts

- Endpoint: `https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.11.1`

## 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-09-20.

- **Endpoint Security**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1060 tokens (~96/item across 11 items; 5 tools + 6 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 77/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 19% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Agenda Intelligence MD MCP server?

Agenda Intelligence MD is a hosted endpoint at https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp, 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 vassiliylakhonin-agenda-intelligence-md 'https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "url": "https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "type": "http",
      "url": "https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vassiliylakhonin-agenda-intelligence-md]
url = "https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "type": "remote",
      "url": "https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vassiliylakhonin-agenda-intelligence-md --url 'https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vassiliylakhonin-agenda-intelligence-md:
    url: "https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "Transport": "http",
      "Url": "https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vassiliylakhonin-agenda-intelligence-md -t streamable-http -u 'https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "type": "http",
      "url": "https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp"
    }
  }
}
```

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-09-20 (score 76, +1)

- [functional] Server version: 1.11.0 → 1.11.1

### 2026-09-17 (score 75, +1)

- [functional] Server version: 1.10.0 → 1.11.0
- [functional] Server version: 1.9.0 → 1.10.0

### 2026-09-15 (score 74, +1)

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

### 2026-09-13 (score 73, +1)

- [security] Tool “decision_verify” rewrote its description, which is the text the model reads
- [security] Tool “agent_output_verification” rewrote its description, which is the text the model reads
- [security] Tool “pre_action_check” rewrote its description, which is the text the model reads

### 2026-09-11 (score 72, +1)

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

### 2026-09-09 (score 71, 0)

- [functional] Server version: 1.8.0 → 1.9.0

### 2026-09-08 (score 71, +1)

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

### 2026-09-06 (score 70, +1)

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

## MCP tools (5)

### `agent_output_verification` (~180 tokens)

Decide whether another agent's claim-backed output is safe to relay onward. Returns a relay verdict with per-claim findings, orphaned evidence references, and owner actions. It does not fetch or validate the cited sources. Required fields in 'request': output_under_review, claims. Grades the evidence you supply and names what is still missing; it does not retrieve sources, so a call that brings none is refused. With only a question and no evidence yet, start at corridor_sanctions_assistant. Evidence triage only: no factual-truth verification, no legal, compliance, sanctions, or financial advice. Human review is required before any commercial action.

Input parameters:

- `claims` (array, required)
- `evidence` (array, required)
- `topic` (string)
- `unsupported_claims` (array): Important claims the analyst could not back with evidence.

Output parameters:

- `claim_count` (integer)
- `evidence_gaps` (array)
- `grounded_claim_count` (integer): Number of claims that carry at least one supporting quote span.
- `human_review_required` (boolean): True for any verdict other than allow_relay: a human should review before the consuming agent acts.
- `limitations` (array)
- `not_advice_notice` (string)
- `owner_actions` (array): Concrete fixes the producing agent should make before the output is relayed.
- `readiness_label` (string)
- `readiness_score` (integer): Heuristic 0-100 score for how ready the supplied claim set is for relay. Only claims that cite an evidence_id present in the supplied evidence contribute to it; a claim whose declared support_level n…
- `trust_signal` (string)
- `unsafe_claims` (array): Claims that must not be relayed as fact: marked unsupported, or citing evidence_ids absent from the supplied evidence.
- `unsupported_statements` (array): Statements the producing agent itself flagged as unsupported (from evidence-audit unsupported_claims).
- `verdict` (string): Machine-actionable relay verdict. allow_relay: every claim is grounded and none is unsupported. verify_before_relay: claims are declared-supported but carry weak support or span-grounding gaps. block…
- `watch_next` (array)
- `weak_claims` (array): Claims declared with weak support that should be strengthened before relay.

### `pre_action_check` (~249 tokens)

Route a caller-controlled action to continue, request_evidence, require_approval, or stop using supplied claim evidence, risk tier, policy checks, and an optional external approval reference. Resubmit the same run_id after adding evidence or approval. The caller remains responsible for enforcement. Required fields in 'request': run_id, proposed_action, risk_tier, claims, dated_sources, policy_context. Grades the evidence you supply and names what is still missing; it does not retrieve sources, so a call that brings none is refused. With only a question and no evidence yet, start at corridor_sanctions_assistant. Evidence triage only: no factual-truth verification, no legal, compliance, sanctions, or financial advice. Human review is required before any commercial action.

Input parameters:

- `actor` (required)
- `approval`
- `claims` (array, required)
- `evidence` (array, required)
- `policy_context`
- `requested_action` (string, required)
- `risk_tier` (string, required)
- `run_id` (string, required): Caller-generated correlation identifier. Resubmit the same run_id after adding evidence or approval.
- `target` (required)
- `unsupported_claims` (array)

Output parameters:

- `approval_required` (boolean)
- `blocking_gaps` (array)
- `decision` (string)
- `decision_id` (string)
- `evidence_requests` (array)
- `human_review_required` (boolean)
- `limitations` (array)
- `not_authorization_notice` (string)
- `policy_checks` (array)
- `policy_version` (string)
- `reason_code` (string)
- `receipt`: Short-lived readiness receipt attached by decision_check. The legacy pre_action_check response omits it.
- `receipt_status` (string): Present on decision_check. unavailable fails the signed Gate path closed.
- `run_id` (string)
- `verification` (object)

### `decision_policies_list` (~81 tokens)

List the bounded readiness policies exposed by the hosted decision Gate, including the decision and verification tools, possible outcomes, positive outcome, input schema, receipt lifetime, and exact machine-readable request/action hash binding. Evidence triage only: no factual-truth verification, no legal, compliance, sanctions, or financial advice. Human review is required before any commercial action.

Output parameters:

- `binding` (object)
- `not_authorization_notice` (string)
- `policies` (array)
- `receipt_format` (string)

### `decision_check` (~219 tokens)

Run pre_action_check and attach a short-lived ES256 readiness receipt bound to the exact request and action hashes. The receipt is evidence of this Gate result, not authorization. Require decision_verify to return gate_passed before using it in an enforcement path. Grades the evidence you supply and names what is still missing; it does not retrieve sources, so a call that brings none is refused. With only a question and no evidence yet, start at corridor_sanctions_assistant. Evidence triage only: no factual-truth verification, no legal, compliance, sanctions, or financial advice. Human review is required before any commercial action.

Input parameters:

- `actor` (required)
- `approval`
- `claims` (array, required)
- `evidence` (array, required)
- `policy_context`
- `requested_action` (string, required)
- `risk_tier` (string, required)
- `run_id` (string, required): Caller-generated correlation identifier. Resubmit the same run_id after adding evidence or approval.
- `target` (required)
- `unsupported_claims` (array)

Output parameters:

- `approval_required` (boolean)
- `blocking_gaps` (array)
- `decision` (string)
- `decision_id` (string)
- `evidence_requests` (array)
- `human_review_required` (boolean)
- `limitations` (array)
- `not_authorization_notice` (string)
- `policy_checks` (array)
- `policy_version` (string)
- `reason_code` (string)
- `receipt`: Short-lived readiness receipt attached by decision_check. The legacy pre_action_check response omits it.
- `receipt_status` (string): Present on decision_check. unavailable fails the signed Gate path closed.
- `run_id` (string)
- `verification` (object)

### `decision_verify` (~176 tokens)

Verify a signed readiness receipt against the caller's expected request and action hashes. Returns gate_passed only for a valid, unexpired, exactly bound continue decision. This does not authorize or perform the action. Required fields in 'request': receipt, expected_request_sha256, expected_action_sha256. Evidence triage only: no factual-truth verification, no legal, compliance, sanctions, or financial advice. Human review is required before any commercial action.

Input parameters:

- `expected_action_hash` (string, required): SHA-256 JCS hash computed from the enforcing caller's own actor, requested_action, target, and risk_tier object.
- `expected_request_hash` (string, required): SHA-256 JCS hash computed from the enforcing caller's own copy of the complete request; do not copy it blindly from the receipt response.
- `receipt` (string, required)

Output parameters:

- `binding_matches` (boolean)
- `expired` (boolean)
- `gate_passed` (boolean)
- `not_authorization_notice` (string)
- `reason_code` (string)
- `receipt`
- `signature_valid` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agent-output-verification-a2a#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 75
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 71
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 69
- 2026-09-04: 69
- 2026-09-03: 68
- 2026-09-02: 67
- 2026-09-01: 67
- 2026-08-31: 66
- 2026-08-30: 66
- 2026-08-29: 65
- 2026-08-28: 65

## Common questions

### What is the Agenda Intelligence MD MCP server?

Agenda Intelligence MD is an MCP server listed in the public MCP registry as io.github.vassiliylakhonin/agenda-intelligence-md. Evidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs. This page covers its hosted endpoint (https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp).

### Is the Agenda Intelligence MD MCP server safe to use?

Agenda Intelligence MD scores 76 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 Agenda Intelligence MD MCP server expose?

Agenda Intelligence MD exposes 5 tools: agent_output_verification, pre_action_check, decision_policies_list, decision_check, decision_verify. Their descriptions and schemas cost roughly 905 tokens of context every time the server is loaded.

### Does the Agenda Intelligence MD MCP server require authentication?

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

### Is the Agenda Intelligence MD MCP server still maintained?

Agenda Intelligence MD is still listed as active in the MCP registry. We last reached this channel on 20 September 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://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcp
- Repository: https://github.com/vassiliylakhonin/agenda-intelligence-md
- Website: https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agent-output-verification-a2a.xml
- Changelog JSON feed: https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agent-output-verification-a2a.json
- HTML version of this page: https://verifymcp.io/servers/vassiliylakhonin-agenda-intelligence-md/agent-output-verification-a2a