Emilia Protocol
NPM · @EMILIA-PROTOCOL/MCP-SERVER
Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
Available components
Last scanned (18 hours ago)
Scores higher than 99% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to emiliaprotocol/emilia-protocol). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 30 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 492 tokens (~70/item across 7 items; 3 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 0
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −2
- Security disclosure: unverified → pass ▲ functional
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@emilia-protocol/mcp-server@2.1.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | emiliaprotocol/emilia-protocol |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/emiliaprotocol/emilia-protocol/.github/workflows/_publish-npm-package.yml@refs/heads/main |
| Rekor log index | 3078391556 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3b331405c77be4bdaf82fa07b0c66526e6659447bd1946647356f38c162543d16d7fe5fd658d3375944a7c5ddd5768cda9230638962e6418a101340e5 |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ep_check_signoff ~88
Poll a pending authorization after ep_guard_action returns BLOCKED. Pass the receipt_id. Returns PENDING, APPROVED_PENDING_CONSUME, CONSUMED, or DENIED. Approval alone is not permission to execute: the executor must match action_hash and atomically consume the receipt at its own choke point.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | The receipt_id returned by ep_guard_action. |
No output schema declared.
No examples provided.
ep_guard_action ~255
Request authorization before an irreversible action: payments, wire transfers, fund releases, deletions, record or account changes, or sending messages with real-world effect. Submits the exact action for policy evaluation and human authorization. This MCP tool does not itself sit at the executor choke point: even after approval, the executor MUST match the returned action_hash and atomically consume the receipt before effect. If BLOCKED, poll ep_check_signoff with the receipt_id.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | Kind of action, e.g. "large_payment_release", "vendor_bank_account_change", "ai_agent_payment_action". |
| amount | number | – | Amount, for payments/releases. |
| currency | string | – | ISO currency code, e.g. "USD". |
| destination | string | – | Where funds or data are going (account, address). |
| organization_id | string | yes | The organization this action belongs to. |
| risk_flags | array | – | Optional risk signals, e.g. ["new_destination","after_hours"]. |
| summary | string | – | One-line, human-readable description the approver will see. |
| target_resource_id | string | yes | What is being acted on — an invoice id, account id, or record id. |
No output schema declared.
No examples provided.
ep_verify_receipt ~67
Ask the configured EMILIA service to verify a stored trust receipt and report its hash and anchor status. Read-only, but not an offline verifier: the result is the service response for the supplied receipt_id.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | Receipt ID (ep_rcpt_...) |
No output schema declared.
No examples provided.
How do I install the Emilia Protocol MCP server?
Emilia Protocol runs locally as an npm package, launched with npx -y @emilia-protocol/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @emilia-protocol/mcp-server
claude mcp add emiliaprotocol-mcp-server -- npx -y @emilia-protocol/mcp-server
What is the Emilia Protocol MCP server?
Emilia Protocol is an MCP server listed in the public MCP registry as io.github.emiliaprotocol/mcp-server. Exact-action approval for consequential agent actions: request, track, and verify signed receipts. This page covers its npm package (@emilia-protocol/mcp-server).
Is the Emilia Protocol MCP server safe to use?
Emilia Protocol scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Emilia Protocol MCP server expose?
Emilia Protocol exposes 3 tools: ep_guard_action, ep_check_signoff, ep_verify_receipt. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.
Is the Emilia Protocol MCP server still maintained?
Emilia Protocol is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Emilia Protocol MCP server under?
Emilia Protocol declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.