Is Emilia Protocol MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
How Emilia Protocol compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 74/100
- higher than 43% of 4,456 AI and agents servers
- Tools that change things
- 11%
- typical: 3%. Fewer write tools means less an agent can break
What its tools let an agent do: 32 read · 4 change
Release history: 2 versions in the registry since 2026-08-22, latest 2026-10-04, typically one every 43 days.
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
1 medium
- Code scan3 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (1)
- mediumeval / new Function used
exec.evalbundle.js: …cess(sourceCode,sch);const makeValidate=new Function(`${names_1.default.self}`,`${names_1.def…
Overall 74/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Emilia Protocol does
- DecionisAuthorize consequential AI agent actions before executionnot reviewedEstablishedA
- agent-custodyMCP gateway that checks each agent tool call against a signed grant and policy, and signs a receiptnot reviewedEstablishedA
three.ws ProvenanceAppend-only, signed, on-chain-verifiable agent action log — record and audit what agents did.not reviewedEstablishedB
