EMILIA Protocol
About
Require a named human's offline-verifiable approval before an AI agent takes an irreversible action — payment release, record change, deploy. Two-person rule, Ed25519 Trust Receipts, IETF-drafted, Apache-2.0.
Details
- Author
- emiliaprotocol
- Categories
- Developer Tools, Security, Automation, AI
Jump to
Setup
Install EMILIA Protocol in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/emiliaprotocol/emilia-protocol
Follow the installation instructions in the repository README, then restart your MCP client.
What can you do with EMILIA Protocol MCP?
-
Scan tool surfaces— Runnpx @emilia-protocol/scan protect ./tools.jsonto map declared action surfaces and review the generated manifest before enforcement.
Issue offline receipts— Usenpx @emilia-protocol/issue demoto generate a Trust Receipt locally without an API key or backend.
Verify receipts— Runnpx @emilia-protocol/verify aeb-conformance --referenceto test evidence-to-effect boundary conformance, or paste any receipt into the browser verifier.
Protect MCP tools— Wrap payment, GitHub admin, or production deploy tools withrelease_payment,delete_repo, ordeploy_productionto refuse actions lacking valid authority receipts.
Run crash-test demo— Executenode examples/crash-test.mjsto see an autonomous agent blocked from wiring $82,000 without fresh human signoff, fully offline.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
