
Eclipse Revoke MCP
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 26, 2026
signed revocation lists for agent cards, keys, and mandates — one feed, every registry, revocation
Overview
Local MCP server that provides signed revocation lists for agent cards, keys and mandates, aggregated into one feed across registries.
- What you can do
- The manifest lists no tools, so the exact operations are not documented.
- Based on the description, it is meant to supply signed revocation lists covering agent cards, keys and mandates.
- It presents those lists as a single feed intended to span multiple registries.
- No instructions or README are provided, so how an assistant queries the feed is unspecified.
- When to use it
- Consider it when an assistant or agent workflow needs to check whether an agent card, key or mandate has been revoked, and you want that check drawn from one consolidated feed rather than per-registry lookups.
- Requirements
- Runs as a local process on the user's machine over stdio; desktop only, with no web executable. No packages, environment variables, headers or authentication are declared, so setup details are undocumented.
Installation
In SourceWeft
- Open Eclipse Revoke MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
1- v0.1.0LatestOct 26, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.