emilia-protocol (emiliaprotocol/emilia-protocol) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
2 months ago

emilia-protocol

Authority control plane for autonomous work. EMILIA Gate enforces finite customer-owned mandates at protected executor boundaries; the open protocol keeps evidence verifiable.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

emiliaprotocol

Source: Glama · also listed on github_topic

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: RESEND_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: EP_PUBLIC_KEY, RESEND_API_KEY, STRIPE_SECRET_KEY, EP_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configEP_KEYS_URL
🔐 secretEP_PUBLIC_KEY
configEP_RECEIPT
configPILOT_FROM_EMAIL
🔐 secretRESEND_API_KEY
🔐 secretSTRIPE_SECRET_KEY
configEP_BASE_URL
🔐 secretEP_API_KEY
configEP_ORG_ID
configEP_SIGNOFF_TIMEOUT_S
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_APP_URL
deployNEXT_PUBLIC_BASE_URL
deployNEXT_PUBLIC_SITE_URL
// quality suggestions

Dependencies

34 dependencies, 1 flagged: @playwright/test

All four hints declared on every tool

4/4 tools missing one or more hints — ep_verify_receipt (missing: idempotentHint); ep_verify_signoff (missing: idempotentHint); ep_trust_profile (missing: idempotentHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

openWorldHint matches behaviour

2 tools claim openWorldHint=false but make outbound HTTP — ep_trust_profile → dynamic (line 87); ep_trust_evaluate → dynamic (line 104)

Either flip openWorldHint to true (acknowledging external reach) or refactor the handler to avoid outbound HTTP. If the only network calls are to a known fixed endpoint that you consider part of the tool itself, document that and keep openWorldHint=false; otherwise true is honest.

Tool handlers catch errors

Only 0/4 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

3/4 tools referenced in tests (75%)

Write tests that reference each tool by name so every tool has at least one test.

Domain consistency

npm scope @emilia-protocol doesn't match GitHub owner emiliaprotocol

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/emiliaprotocol-emilia-protocol-157gfe)](https://m8ven.ai/mcp/emiliaprotocol-emilia-protocol-157gfe)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ccb739bb5ba01146dc2c430f099ed50d0516e1a8
code hash: 67f1a9ba2037b99a41755a9fe664acc0ec9c511f3ebe0cd7909d58426944e956
verified: 6/16/2026, 11:39:35 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client