Agenda Intelligence MD
REMOTE · M2M-ESCROW-ARBITER-A2A.VASSILIY-LAKHONIN.WORKERS.DEV · 13 COMPONENTS · SCANNED SEP 20
Evidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 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 343 tokens (~49/item across 7 items; 1 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the Agenda Intelligence MD MCP server?
Agenda Intelligence MD is a hosted endpoint at https://m2m-escrow-arbiter-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 · m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev
claude mcp add --transport http vassiliylakhonin-agenda-intelligence-md 'https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp'
{
"mcpServers": {
"vassiliylakhonin-agenda-intelligence-md": {
"url": "https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp"
}
}
} {
"servers": {
"vassiliylakhonin-agenda-intelligence-md": {
"type": "http",
"url": "https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp"
}
}
} [mcp_servers.vassiliylakhonin-agenda-intelligence-md] url = "https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vassiliylakhonin-agenda-intelligence-md": {
"type": "remote",
"url": "https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add vassiliylakhonin-agenda-intelligence-md --url 'https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp' --transport streamable-http
mcp_servers:
vassiliylakhonin-agenda-intelligence-md:
url: "https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp" {
"McpServers": {
"vassiliylakhonin-agenda-intelligence-md": {
"Transport": "http",
"Url": "https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp"
}
}
} assistant mcp add vassiliylakhonin-agenda-intelligence-md -t streamable-http -u 'https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp'
{
"mcpServers": {
"vassiliylakhonin-agenda-intelligence-md": {
"type": "http",
"url": "https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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
- Tool “m2m_escrow_arbitration_ruling” rewrote its description, which is the text the model reads security
- Server version: 1.11.0 → 1.11.1 functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 67
First indexed and scored.
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 20 Sept 2026 · Probed https://m2m-escrow-arbiter-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 m2m-escrow-arbiter-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://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp | Inconclusive | 405 |
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 →
m2m_escrow_arbitration_ruling ~196
Deterministic dispute arbitration and delivery verification for Agent-to-Agent escrow transactions. Checks supplied hashes, supported offline JSON schemas and deadlines, proposing allocations for human review. No settlement or clearance is issued. Required fields in 'request': escrow_id, deal_terms, specification, delivery_submission. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | Structured request object. Full contract: https://github.com/vassiliylakhonin/agenda-intelligence-md/blob/main/schemas/v1/m2m-escrow-arbiter-request.schema.json |
No output schema declared.
No examples provided.
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://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp).
Is the Agenda Intelligence MD MCP server safe to use?
Agenda Intelligence MD scores 69 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 1 tool: m2m_escrow_arbitration_ruling. Their descriptions and schemas cost roughly 196 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.