Eclipse Consent MCP
Per-agent, per-purpose consent receipts for personal data, checked at action time
- Platforms
- API, CLI
- Version
- 0.1.0
- Listing updated
- today
Similar MCP servers
About Eclipse Consent MCP
Eclipse Consent MCP is an MCP server for security. It is available on API and CLI.
The MCP registry entry describes a grant an agent must present before touching personal data, along with a revocation that takes effect on the next check. Processors send a receipt id at action time and receive an ALLOW or DENY answer against the current state, so a revoked grant stops working immediately rather than at a batch cycle.
The Bazaar page lists the server's tools as consent_grant, consent_check, consent_revoke, consent_history and consent_dependents. It states that a grant without full lineage is void and that a grantee cannot write its own consent, which it names as a distinct refusal.
According to the Bazaar listing, the build is local v0.1 and only accepts fixture subjects, which the product enforces itself. Real-subject processing and jurisdiction packs are described as held, so the server is aimed at developers testing consent logic rather than live personal-data workflows.
Tools this server provides (5)
Taken from the project documentation; the running server may differ.
- consent_grant
- Creates a consent grant for an agent and purpose.
- consent_check
- Returns ALLOW or DENY for a presented receipt id against current state.
- consent_revoke
- Revokes an existing consent grant.
- consent_history
- Returns the history of a consent record.
- consent_dependents
- Lists records that depend on a consent grant.
What it does
- Grant-based consent receipts
- Each agent and purpose pair is covered by a receipt id that a processor must present before acting.
- Synchronous allow or deny
- Checks return ALLOW or DENY against current state, so revocations apply at the next call.
- Revocation propagation
- Revoking a grant removes its effect for every later check made against that receipt.
- Consent history and dependents
- Tools expose the history of a consent record and the records that depend on it.
- Self-assertion refusal
- A grantee cannot write its own consent, and the server reports this as CONSENT_SELF_ASSERTED.
Good for
- Gate agent access to personal data on a recorded, purpose-specific grant
- Test consent revocation behaviour before deploying a processor that handles personal data
- Keep an auditable history of which agent was granted which purpose
Eclipse Consent MCP FAQ
Can it be used with real personal data?
The Bazaar listing says the local v0.1 build accepts fixture subjects only, enforced by the product, and that real-subject processing is held.
How does a revocation take effect?
According to the listing, a processor presents a receipt id at action time and gets an ALLOW or DENY answer against current state, so a revocation applies at the very next check.
What are the best alternatives to Eclipse Consent MCP?
The closest alternatives to Eclipse Consent MCP are Eclipse Countermark MCP, Eclipse Steward MCP, Eclipse Census MCP, Protect MCP and Eclipse Cluster MCP.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.