Is io.github.vassiliylakhonin/agenda-intelligence-md up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, valid. A2A 1.0 shape; 7 skills; JSONRPC; 1 JWS signature (ES256; not verified)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, does not validate: `$schema` is required (and 1 more). SEP-1649 shape; Agenda Intelligence MD MCP Server 1.14.1; MCP 2026-07-28; stdio./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 3 tools: corridor_bankability_screen, fleet_directory, strategic_risk_triage.
Its tools changed between 2026-09 and 2026-10:
- Added (1):
corridor_bankability_screen fleet_directory: description, output schema changedstrategic_risk_triage: description, output schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | io.github.vassiliylakhonin/agenda-intelligence-md |
|---|---|
| Endpoint | https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcp |
| Other endpoints | https://agent-output-verification-a2a.vassiliy-lakhonin.workers.dev/mcphttps://middle-corridor-deal-risk-gate-a2a.vassiliy-lakhonin.workers.dev/mcphttps://cis-secondary-sanctions-a2a.vassiliy-lakhonin.workers.dev/mcphttps://agentic-interaction-trust-a2a.vassiliy-lakhonin.workers.dev/mcphttps://gulf-maritime-exposure-a2a.vassiliy-lakhonin.workers.dev/mcphttps://kazakhstan-market-entry-readiness-a2a.vassiliy-lakhonin.workers.dev/mcphttps://corridor-sanctions-assistant-a2a.vassiliy-lakhonin.workers.dev/mcphttps://critical-minerals-due-diligence-a2a.vassiliy-lakhonin.workers.dev/mcphttps://dual-use-technology-export-a2a.vassiliy-lakhonin.workers.dev/mcphttps://agent-financial-guard-a2a.vassiliy-lakhonin.workers.dev/mcphttps://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt