Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 643 tokens (~71/item across 9 items; 3 tools + 6 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Agenda Intelligence MD MCP server?

Agenda Intelligence MD is a hosted endpoint at https://agenda-intelligence-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.

remote · agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev

# add to Claude Code
claude mcp add --transport http vassiliylakhonin-agenda-intelligence-md 'https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "url": "https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "type": "http",
      "url": "https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.vassiliylakhonin-agenda-intelligence-md]
url = "https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "type": "remote",
      "url": "https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vassiliylakhonin-agenda-intelligence-md --url 'https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  vassiliylakhonin-agenda-intelligence-md:
    url: "https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "Transport": "http",
      "Url": "https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add vassiliylakhonin-agenda-intelligence-md -t streamable-http -u 'https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "vassiliylakhonin-agenda-intelligence-md": {
      "type": "http",
      "url": "https://agenda-intelligence-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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1
    • Server version: 1.11.0 → 1.11.1 functional
  • 18 Sept 26 +1

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

  • 17 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “fleet_directory” rewrote its description, which is the text the model reads security
    • Schema quality: 38 → 71 functional
    • First check of Tool coverage: 33 functional
    • Server version: 1.10.0 → 1.11.0 functional
    • Server version: 1.9.0 → 1.10.0 functional
    • New tool “corridor_bankability_screen” functional
  • 14 Sept 26 +7
    • Judged manipulation: unverified → pass security
    • Schema quality: unverified → good functional
  • 13 Sept 26 −6
    • Judged manipulation: pass → unverified security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 32 → 38 functional
    • Schema quality: good → unverified functional
    • New tool “fleet_directory” functional
  • 12 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 9 Sept 26 −1
    • Server version: 1.8.0 → 1.9.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vassiliy-lakhonin.workers.dev CN=YE2,O=Let's Encrypt,C=US 17 Sept 2026 16 Dec 2026 ECDSA 256 ECDSA-SHA384 69cc8a16668af0d2b2aba6c3a6088fa18b6
SANs: *.vassiliy-lakhonin.workers.dev, vassiliy-lakhonin.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp Verified 200
http (plaintext) http://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp Inconclusive 405
MCP tools · 3 exposed · ~494 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
corridor_bankability_screen ~332

Evaluate project finance bankability and IFI covenants (EBRD, ADB, EU Global Gateway) for Trans-Caspian and Middle Corridor infrastructure projects. Evaluates minimum DSCR floor (1.20x), non-sovereign margin (1.30x), leverage ceiling (<=80%), Caspian hydrological water-level constraints (-1.20m Baltic datum), and FX currency mismatch. Returns a free Decision Teaser with covenant pass/fail matrix, bottleneck analysis, and an x402 micropayment invoice to unlock the full 15-year debt waterfall model and IFI memo. Evidence triage only: no factual-truth verification, no legal, compliance, sanctions, or financial advice. Human review is required before any commercial action.

NameTypeReqDescription
capex_usd_mnumberyesTotal project capital expenditure in millions USD.
corridor_legstringyesCorridor transit leg under review.
currency_mismatchbooleanWhether tariff revenues are collected in local currency (KZT/AZN/GEL) while debt is in USD/EUR.
dscr_minnumberyesProjected minimum Debt Service Coverage Ratio (DSCR).
evidence_sourcesarrayList of feasibility study references, decrees, or project files.
has_sovereign_guaranteebooleanWhether an official sovereign loan guarantee is provided.
ifi_debt_usd_mnumberyesTarget IFI senior debt financing in millions USD.
project_namestringyesName of the corridor infrastructure project (e.g. 'Aktau Port Container Hub Expansion').
NameTypeReqDescription
bankability_statusstringyes
corridor_legstring
project_namestringyes
unlocked_full_dossierbooleanyes

No examples provided.

fleet_directory ~78

List all 11 specialized risk triage and verification gates in the Agenda Intelligence fleet, including their MCP/A2A endpoints, supported profiles, primary tool names, input schemas, and required fields. Evidence triage only: no factual-truth verification, no legal, compliance, sanctions, or financial advice. Human review is required before any commercial action.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

strategic_risk_triage ~84

Triage a free-text strategic-risk question: route it to the relevant regional and sector modules and report which evidence categories a defensible answer would require. Evidence triage only: no factual-truth verification, no legal, compliance, sanctions, or financial advice. Human review is required before any commercial action.

NameTypeReqDescription
textstringyesThe question in plain language.

No output schema declared.

No examples provided.

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://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp).

Is the Agenda Intelligence MD MCP server safe to use?

Agenda Intelligence MD scores 79 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 3 tools: strategic_risk_triage, fleet_directory, corridor_bankability_screen. Their descriptions and schemas cost roughly 494 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.