MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
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.
99/100
trust score
29
downloads a day
local
runs on your machine
1k
downloads in 30d
What it does
Connects the AI agents you use: your agent hands a task to another and gets the answer back
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user ennodia-mcp '--' npx -y ennodia
# 2 — ask your agent for something these tools do
# ennodia_list_harnesses, ennodia_list_skills, ennodia_install_skills and 23 more
Ennodia costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
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. Its scan result is on the Security tab — 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. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user ennodia-mcp '--' npx -y ennodiaReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
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.
No parameter schema on file.
Discover prompt-only skills from project, user, and built-in skill directories without returning full instruction text.
No parameter schema on file.
Install bundled Ennodia Agent Skills into native harness skill directories. Defaults to dryRun so clients can inspect planned writes before applying them.
No parameter schema on file.
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.
No parameter schema on file.
No parameter schema on file.
List recent Plan Advisor requests started by this Ennodia MCP server process.
No parameter schema on file.
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.
No parameter schema on file.
Cancel a running Plan Advisor request and its Advisor task.
No parameter schema on file.
No parameter schema on file.
Estimate the input-token budget for a planned Ennodia run and report whether optional limits would be exceeded before starting child tasks.
No parameter schema on file.
Resolve focused compositional slices to harnesses and estimate child-task and later Judge + Result Advisor budget without starting child processes.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
No parameter schema on file.
List high-level Ennodia runs started by this MCP server process.
No parameter schema on file.
Read terminal run receipts persisted under the local Ennodia history directory. Use after a restart to inspect previous final answers and Judge disagreement analysis.
No parameter schema on file.
Inspect run status, selected harnesses, child task IDs, comparison ID, final Advisor answer, events, and ETA.
No parameter schema on file.
Cancel a high-level run and any active child task, Judge, or Result Advisor.
No parameter schema on file.
List tasks started by this Ennodia MCP server process.
No parameter schema on file.
Inspect a batch of compositional shard tasks, group running and terminal states, and return successful task IDs ready for Judge + Result Advisor comparison.
No parameter schema on file.
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.
No parameter schema on file.
List Judge + Result Advisor comparisons started by this Ennodia MCP server process.
No parameter schema on file.
Inspect comparison status, candidate inputs, Judge analysis, Result Advisor answer, child task IDs, degradation state, and ETA.
No parameter schema on file.
Cancel a running Judge + Result Advisor comparison and its active child task.
No parameter schema on file.
Inspect task status, captured output, events, and ETA.
No parameter schema on file.
Cancel a running task by task ID.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ennodia or to call it, 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: —
ATrust score 99 / 100
Release 0.4.1 · scanned 14 Oct 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
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest3fc33796416306a3a1719519120b4e56d5f01cfec5f251fa1fb7271ac0552ec3
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 digest3fc33796416306a3
Scanned2026-10-14
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.4.1. Pin a release below and the command asks for exactly that one.
0.4.1
28 Sep 2026
latestNo release note was published with this version.
0.4.0
26 Sep 2026
No release note was published with this version.
0.3.0
18 Sep 2026
No release note was published with this version.
0.2.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Ennodia can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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 a signed-in account that does not publish it, and nothing else.