A2A Governance Bridge MCP server. Tools: verify agent compliance, authorize a2a transaction, get trust registry. Built by MEOK AI Labs.
Free
Nothing to run from here
Ennodia is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for multi-agent review with Compare and traceable receipts
Quickstart
# 1 — run it from where its publisher ships it
npx -y ennodia
# 2 — ask your agent something
> MCP server for multi-agent review with Compare and traceable receipts
Ennodia is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
CHAll 1 server
cherninlab1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Ennodia as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add ennodia-mcp -- npx -y ennodiaReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
26 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Discover supported local AI harnesses and report availability, runnable state, command path, version, capabilities, and adapter notes. Use first when setup or routing fails.
Takes no parameters.
Example callreturns →
Discover prompt-only skills from project, user, and built-in skill directories without returning full instruction text.
Takes no parameters.
Example callreturns →
Install bundled Ennodia Agent Skills into native harness skill directories. Defaults to dryRun so clients can inspect planned writes before applying them.
Takes no parameters.
Example callreturns →
Classify a prompt and preview the route Ennodia would take without starting any child process. Use before ennodia_run when you want to inspect routing.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List recent Plan Advisor requests started by this Ennodia MCP server process.
Takes no parameters.
Example callreturns →
Inspect Plan Advisor status, validation issues, frozen inventory identity, proposal, validated plan, digest, budgets, events, and ETA. A plan can be launched only when status is ready. An authorized plan has status consumed and cannot run again.
Takes no parameters.
Example callreturns →
Cancel a running Plan Advisor request and its Advisor task.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Estimate the input-token budget for a planned Ennodia run and report whether optional limits would be exceeded before starting child tasks.
Takes no parameters.
Example callreturns →
Resolve focused compositional slices to harnesses and estimate child-task and later Judge + Result Advisor budget without starting child processes.
Takes no parameters.
Example callreturns →
Start raw child harness tasks without a run-level Judge + Result Advisor pass. Use for debugging, direct harness calls, or manual comparison workflows; prefer ennodia_run for normal end-to-end use.
Takes no parameters.
Example callreturns →
Start one focused child task per slice for compositional reviews. Poll the returned task IDs, then pass useful completed task IDs to ennodia_start_compare for a Judge + Result Advisor comparison.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List high-level Ennodia runs started by this MCP server process.
Takes no parameters.
Example callreturns →
Read terminal run receipts persisted under the local Ennodia history directory. Use after a restart to inspect previous final answers and Judge disagreement analysis.
Takes no parameters.
Example callreturns →
Inspect run status, selected harnesses, child task IDs, comparison ID, final Advisor answer, events, and ETA.
Takes no parameters.
Example callreturns →
Cancel a high-level run and any active child task, Judge, or Result Advisor.
Takes no parameters.
Example callreturns →
List tasks started by this Ennodia MCP server process.
Takes no parameters.
Example callreturns →
Inspect a batch of compositional shard tasks, group running and terminal states, and return successful task IDs ready for Judge + Result Advisor comparison.
Takes no parameters.
Example callreturns →
Compare completed Ennodia task outputs or caller-supplied responses. The Judge maps agreements, contradictions, and risks; the Result Advisor then combines that analysis into the final answer. Returns a Compare ID to inspect with ennodia_get_compare.
Takes no parameters.
Example callreturns →
List Judge + Result Advisor comparisons started by this Ennodia MCP server process.
Takes no parameters.
Example callreturns →
Inspect comparison status, candidate inputs, Judge analysis, Result Advisor answer, child task IDs, degradation state, and ETA.
Takes no parameters.
Example callreturns →
Cancel a running Judge + Result Advisor comparison and its active child task.
Takes no parameters.
Example callreturns →
Inspect task status, captured output, events, and ETA.
Takes no parameters.
Example callreturns →
Cancel a running task by task ID.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Ennodia costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 99 / 100
Release 0.2.0 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 1 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest151b1030058878f268df74ff5a2402029fcabce7de5afc025ef4a289b03143e8
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
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>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ennodia_list_harnesses | no tags | |
| ennodia_list_skills | no tags | |
| ennodia_install_skills | no tags | |
| ennodia_plan | no tags | |
| ennodia_start_plan_advice | no tags | |
| ennodia_list_plan_advice | no tags | |
| ennodia_get_plan_advice | no tags | |
| ennodia_cancel_plan_advice | no tags | |
| ennodia_start_advised_plan | no tags | |
| ennodia_estimate_budget | no tags | |
| ennodia_estimate_compositional_budget | no tags | |
| ennodia_start | no tags | |
| ennodia_start_compositional | no tags | |
| ennodia_run | no tags | |
| ennodia_list_runs | no tags | |
| ennodia_history | no tags | |
| ennodia_get_run | no tags | |
| ennodia_cancel_run | no tags | |
| ennodia_list_tasks | no tags | |
| ennodia_get_compositional_status | no tags | |
| ennodia_start_compare | no tags | |
| ennodia_list_compares | no tags | |
| ennodia_get_compare | no tags | |
| ennodia_cancel_compare | no tags | |
| ennodia_get_task | no tags | |
| ennodia_cancel_task | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest151b1030058878f2
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.2.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.2.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Ennodia in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.