← All servers

Agenda Intelligence MD

warnings

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

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

https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/mcpWebsiteOAuthMCP 2026-07-28v1.17.0last checked 18 Oct 2026spoke MCP on 100% of 88 checks (30 days)initialize in 221 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✕Claude CodeNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Claude Code docs · read on 2026-08-30

✕Claude (claude.ai & Desktop)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✕ChatGPTNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

ChatGPT docs · read on 2026-08-30

✕CursorNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Cursor docs · read on 2026-08-30

✕VS Code (Copilot)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 18 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
OAuth
Issuer
https://vizier.vassiliy-lakhonin.workers.dev
Dynamic client registration
✕Not advertised

A client that cannot register itself needs credentials issued out of band before it can begin the flow.

Client ID Metadata Document
✕Not advertised
PKCE
✕None advertised

MCP requires S256; a client that implements only that has no method in common with this server.

Grant types
authorization_code, client_credentials, urn:ietf:params:oauth:grant-type:token-exchange
Scopes
mcp:tools, read, audit
Protected-resource metadata
✓Published (RFC 9728)
Anonymous access
Handshake succeeds; 5 tools listable
Credentials demanded in prose
✕fleet_directory

These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

Documentation
https://agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev/docs

What the probe found

warningTools needing credentials are listed without a challenge

1 of the 5 tools listed anonymously say in their own descriptions that they need an account or a key (fleet_directory), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

5 tools usable without signing in

The server exposes a public surface before authorization: strategic_risk_triage, fleet_directory, corridor_bankability_screen, free_trial_status, free_trial.

Tools

corridor_bankability_screenfleet_directoryfree_trialfree_trial_statusstrategic_risk_triage

Contract history

18 Oct 2026v1.17.0no contract changes
17 Oct 2026v1.16.21 compatible3 cosmeticinstructions rewritten

Instructions rewritten: corridor_bankability_screen, strategic_risk_triage. The description an agent follows changed; the callable contract may not have.

16 Oct 2026v1.16.2no contract changes
15 Oct 2026v1.16.12 compatible3 cosmeticinstructions rewritten

Instructions rewritten: corridor_bankability_screen, strategic_risk_triage. The description an agent follows changed; the callable contract may not have.

15 Oct 2026v1.16.1no contract changes
13 Oct 2026v1.16.03 cosmeticinstructions rewritten

Instructions rewritten: corridor_bankability_screen, strategic_risk_triage. The description an agent follows changed; the callable contract may not have.

11 Oct 2026v1.16.03 cosmetic
10 Oct 2026v1.16.0no contract changes
9 Oct 2026v1.14.11 cosmeticinstructions rewritten

Instructions rewritten: fleet_directory. The description an agent follows changed; the callable contract may not have.

8 Oct 2026v1.14.03 cosmeticinstructions rewritten

Instructions rewritten: corridor_bankability_screen, fleet_directory, strategic_risk_triage. The description an agent follows changed; the callable contract may not have.

1 Oct 2026v1.14.03 cosmeticinstructions rewritten

Instructions rewritten: corridor_bankability_screen, fleet_directory, strategic_risk_triage. The description an agent follows changed; the callable contract may not have.

30 Sep 2026v1.13.03 compatibleinstructions rewritten

Instructions rewritten: corridor_bankability_screen. The description an agent follows changed; the callable contract may not have.

30 Sep 2026v1.13.03 cosmeticinstructions rewritten

Instructions rewritten: corridor_bankability_screen, fleet_directory, strategic_risk_triage. The description an agent follows changed; the callable contract may not have.

26 Sep 2026v1.13.0no contract changes
23 Sep 2026v1.12.1no contract changes
21 Sep 2026v1.12.0no contract changes
20 Sep 2026v1.11.1no contract changes
17 Sep 2026v1.11.01 compatible
17 Sep 2026v1.10.0no contract changes
17 Sep 2026v1.9.01 cosmeticinstructions rewritten

Instructions rewritten: fleet_directory. The description an agent follows changed; the callable contract may not have.

12 Sep 2026v1.9.01 compatible
9 Sep 2026v1.9.0no contract changes
2 Sep 2026v1.8.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for Agenda Intelligence MD
[![MCP status](https://mcpi.app/servers/agenda-intelligence-md/badge.svg)](https://mcpi.app/servers/agenda-intelligence-md)