Ennodia MCP Server
ennodia
npm
v0.2.0
Published by cherninlab — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for multi-agent review with Compare and traceable receipts
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Dynamic module load from a non-literal (src/plan-advice.ts)MTC-SRC-005
In the server's implementation (`src/plan-advice.ts:262`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const record = this.require(id); if (isTerminal(record.status)) { return this.toView(record); } r
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/plan-advice.ts
Tools 26
Each tool and what it can reach — statically extracted from the published source.
ennodia_cancel_compareno sensitive capabilityennodia_cancel_plan_adviceno sensitive capabilityennodia_cancel_runno sensitive capabilityennodia_cancel_taskno sensitive capabilityennodia_estimate_budgetno sensitive capabilityennodia_estimate_compositional_budgetno sensitive capabilityennodia_get_compareno sensitive capabilityennodia_get_compositional_statusno sensitive capabilityennodia_get_plan_adviceno sensitive capabilityennodia_get_runno sensitive capability
Show 16 more tools ↓
ennodia_get_taskno sensitive capabilityennodia_historyno sensitive capabilityennodia_install_skillsno sensitive capabilityennodia_list_comparesno sensitive capabilityennodia_list_harnessesno sensitive capabilityennodia_list_plan_adviceno sensitive capabilityennodia_list_runsno sensitive capabilityennodia_list_skillsno sensitive capabilityennodia_list_tasksno sensitive capabilityennodia_planno sensitive capabilityennodia_runno sensitive capabilityennodia_startno sensitive capabilityennodia_start_advised_planno sensitive capabilityennodia_start_compareno sensitive capabilityennodia_start_compositionalno sensitive capabilityennodia_start_plan_adviceno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (26 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.0 latest |
A 99/100 | 1 | 1.13.0 | 2026-09-07 |
v0.1.1 |
A 99/100 | 0 | 1.12.1 | 2026-08-20 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan ennodia --onlineMore in AI & Agents
Authenticated MCP transport with HTTP Signatures for AAuth agents
Local-first MCP server for parallel AI coding agents to claim file ownership before edits, preventing stomping on each other in the same worktree.
Agent-agnostic intercommunication system — sessions, messaging, channels, shared state, and real-time events
MCP server for AI agent task communication and delegation with diagnostic lifecycle visibility
Programmatic add/link/unlink for MCP servers across 23 AI coding agents (Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Zed, Cline, OpenCode, Goose, Kiro, Windsurf, and more). Functional API with dry-run support.
MCP server layer exposing agent-mesh orchestrator as an MCP agent