Refusal-dialect probe: signed cards naming what a server's 429 means and whether its meter lies.
Scored across 3 tools
cached_card_query, list_servers, and verify_card each target a distinct action (query a card, enumerate servers, check a signature). The only mild overlap is that cached_card_query and verify_card both operate on 'cards', but retrieve-vs-verify is clear from the descriptions.
All three follow a verb_noun shape (list_servers, verify_card) with cached_card_query deviating only by the 'cached_' modifier prefix. Conventions are snake_case throughout and readable, just not perfectly uniform.
At 3 tools the surface is thin for a protocol that appears to involve servers, signed cards, and verification. Each tool does earn its place, but the count sits at the borderline for the apparent scope.
Read-side operations (query a card, list servers, verify a signature) are covered, but there is no way to register/admit a server, publish or revoke a dialect card, or inspect server/card metadata. These are notable lifecycle gaps for the stated domain.
Cached signed dialect card query ($0.05; first free once per account and per wallet). Requires api_token and server_id.
Inputs: api_token (required), server_id (required).
List admitted dialect servers
Inputs: no named parameters.
Verify a dialect card Ed25519 signature
Inputs: card (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Live-payload conformance probes with signed receipts: ABSENT/EMPTY/PARTIAL/COMPLETE/BROKEN.
Three-leg MCP OAuth remediation verdicts, proven behaviourally against a canary server.
Measured rates at which web services lack machine-readable capabilities. Research demonstrator.
Add one secure layer between your agents and this server.