Eclipse Revoke MCP runs on your own machine — the client starts it, so there is no endpoint to ping.
signed revocation lists for agent cards, keys, and mandates — one feed, every registry, revocation
Nothing serious here today
Today is the operative word: we check Eclipse Revoke MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to Eclipse Revoke MCP
same job, measured the same wayOne verification call for third-party agent cards and payment mandates — a receipted verdict a
Governed bench access for agents — signed mandates, pinned artifacts, evidence for every session.
Bazaar checkout for agents — quote, mandate, signed entitlement, delivery, receipt, refund.
KYA backed by a real company: e-CNPJ-signed agent mandates, revocation-checked, signed verdicts
One search across every agent registry: 100K+ MCP/A2A/x402 services, signed receipts.
Signed Agent Cards, policy-gated delegation, certification before hire.
Publish once, tracked everywhere: registry-native facets plus a mandate-bound listing ledger.
spawn trees, model/config lineage, and version ancestry for agents — who spawned whom, running
Eclipse Revoke MCP — questions
Answers built from our own checks of this server.