Evernode MCP
NPM · EVERNODE-MCP
Evernode/HotPocket dApp helper: templates, non-determinism lint, lease math, live host lookup.
Available components
Last scanned (6 hours ago)
Scores higher than 42% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1398 tokens (~116/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 66% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "generate_deploy_commands" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +6
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.40 ▲ functional
- 11 Oct 26 −5
- CVE-2026-104850 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Security disclosure: fail → unverified ▼ functional
- 1 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/evernode-mcp@0.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_contract_api Check HotPocket contract API usage ~126
Heuristic static check that a HotPocket Node.js contract uses the contract API correctly: an hpc.init(...) entry point, reading ctx (users / lclSeqNo), persisting ONLY through the consensused state mechanism (no arbitrary fs writes to non-state paths), handling ctx.users I/O, using ctx.lclSeqNo for time (not Date.now), and awaiting async consensus ops. Severity-rated with fix + why. Sibling to check_determinism — guidance, NOT a proof.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | the HotPocket contract JS/TS source to check |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | – | – |
| summary | string | – | – |
No examples provided.
check_determinism Check contract determinism ~113
Heuristic linter for HotPocket contract source: flags known non-deterministic patterns that can break cluster consensus (wall-clock, randomness, network I/O, env/host reads, timers/races, filesystem outside the state file, unordered iteration/serialization, locale/ICU, floating-point literals). HIGH findings are likely consensus breakers. A clean result means none of these patterns were found — it does not prove the contract is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | the contract JS/TS source to scan |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | – | – |
| summary | string | – | – |
No examples provided.
check_hook_compat Xahau Hook settlement workflow ~119
Returns the recommended workflow (no analysis is performed) for a dApp that settles value on Xahau through a Hook-guarded account: build/lint the Hook with xahc, simulate it with xahau-mcp, prove the spend invariant with xahc-prover, then install via an unsigned SetHook.
| Name | Type | Req | Description |
|---|---|---|---|
| involves_hook | boolean | yes | does the dApp's Xahau account run a Hook? |
| what | string | – | what the hook should enforce, e.g. 'per-tx spend limit' |
| Name | Type | Req | Description |
|---|---|---|---|
| involvesHook | boolean | – | – |
| repos | object | – | – |
| workflow | array | – | – |
No examples provided.
estimate_lease_cost Estimate EVR lease cost ~106
Estimate tenant EVR lease cost = evrPerMoment × moments × nodes. Rates are host-set (no network standard); registration fees are host-side, not included.
| Name | Type | Req | Description |
|---|---|---|---|
| evr_per_moment | number | yes | host's per-Moment lease rate in EVR (from its offer) |
| moment_minutes | number | – | Moment window in minutes (default 60) |
| moments | number | yes | number of Moments to lease |
| nodes | number | yes | cluster size |
| Name | Type | Req | Description |
|---|---|---|---|
| approxDurationHours | number | – | – |
| inputs | object | – | – |
| notes | array | – | – |
| perNodeEVR | number | – | – |
| totalEVR | number | – | – |
No examples provided.
explain_error Explain an Evernode/HotPocket error ~52
Map a HotPocket/Evernode error message to its likely cause and fix (connection, consensus stall, no hosts, insufficient EVR, lease expiry, docker, Hook rejection).
| Name | Type | Req | Description |
|---|---|---|---|
| error_text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| explanations | array | – | – |
| matched | boolean | – | – |
| message | string | – | – |
No examples provided.
generate_contract Generate a HotPocket dApp ~107
Generate a HotPocket dApp file set (contract + state helper + hp.cfg.override + package.json + client) for a template. Templates avoid the known non-determinism sources (no wall-clock, randomness, or network in the contract path; time = ctx.lclSeqNo) and pass check_determinism with no HIGH findings — lint-clean, not proven deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | project/contract name (default: mycontract) |
| template | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| files | object | – | – |
| notes | array | – | – |
| template | string | – | – |
No examples provided.
generate_deploy_commands Generate deploy commands ~82
Generate the command sequence for: local (hpdevkit dev cluster), single (evdevkit acquire one host), cluster (evdevkit N-node cluster), or cluster-manager (connect to Offledger Cluster Manager).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | – |
| instance_name | string | – | – |
| mode | string | yes | – |
| nodes | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | array | – | – |
| steps | array | – | – |
No examples provided.
generate_settlement Generate Xahau settlement bundle ~214
For a value-moving dApp, generate the cluster-side Xahau payout code (a starting point; multisig aggregation is left to you) + an unsigned `xahc install-tx` command for the agent_guardrail Hook (per-tx LIM spend cap + optional DST lock) on the cluster account + the `xahc prove` command to check it. Emits commands only — no safety verdict. While that Hook is installed it makes the ledger reject outgoing Payments over LIM or to a non-allowed DST; it fires on Payment only, so it does not stop the account's signers from removing it with SetHook or moving value with other transaction types.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster_account | string | – | the cluster's Xahau (multisig) account r-address |
| dest | string | – | optional r-address to LOCK payouts to (the DST hook param) |
| limit_drops | integer | yes | per-tx spend cap in drops (the LIM hook param) |
| template | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| files | object | – | – |
| install | string | – | – |
| limitDrops | number | – | – |
| notes | array | – | – |
| prove | string | – | – |
| template | string | – | – |
No examples provided.
host_diagnostics Diagnose an Evernode host (live) ~172
Health view of a single Evernode host by r-address: registration status, reputation, active/total/available instance slots, lease rate (EVR per Moment and/or drops, if the source has them), RAM/disk, and red-flags (flagged in the registry, marked inactive, reputation < 50, zero reputation, full capacity). Fetches live from the public OnLedger API (api.onledger.net) — or pass a `host` object to diagnose it. REAL data only: unknown fields are OMITTED (never invented); honest found:false + note on not-found / fetch failure.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | the host's Xahau r-address to look up live on OnLedger |
| host | object | – | optional: diagnose this supplied host object instead of fetching live |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| found | boolean | – | – |
| lease | object | – | – |
| note | string | – | – |
| redFlags | array | – | – |
| registration | object | – | – |
| reputation | number | – | – |
| slots | object | – | – |
| source | string | – | – |
| specs | object | – | – |
No examples provided.
list_templates List dApp templates ~50
List the available HotPocket dApp templates (escrow, subscription, game_backend, voting, token_gated, payment_splitter, oracle_consumer, streaming_payment, multisig_treasury, blank).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| templates | array | – | – |
No examples provided.
recommend_hosts Recommend Evernode hosts (live) ~203
Fetch + rank live Evernode hosts from the public OnLedger API (api.onledger.net, which indexes the Evernode registry on Xahau) by cheap | capacity | reputation; the filters (min_reputation, min_slots, country, min_ram_mb, limit) are passed to that live query. Or pass your own `hosts` list to rank it (filters are not applied to a supplied list; top 10 returned). Real data only — never invents hosts.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | 2-letter ISO code, e.g. DE, US, JP |
| hosts | array | – | optional: rank this supplied list instead of fetching live |
| limit | number | – | max hosts (default 10) |
| min_ram_mb | number | – | – |
| min_reputation | number | – | 0–255 host reputation floor |
| min_slots | number | – | minimum free instances (default 1) |
| prefer | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| note | string | – | – |
| prefer | string | – | – |
| query | string | – | – |
| ranked | array | – | – |
| source | string | – | – |
No examples provided.
recommend_pattern Recommend a HotPocket pattern ~54
Given a plain-English use-case, recommend the HotPocket pattern (node count, state model, oracle/NPL usage, Xahau settlement) with the determinism caveats that matter.
| Name | Type | Req | Description |
|---|---|---|---|
| use_case | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| nodes | string | – | – |
| notes | array | – | – |
| pattern | string | – | – |
No examples provided.
How do I install the Evernode MCP server?
Evernode MCP runs locally as an npm package, launched with npx -y evernode-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · evernode-mcp
claude mcp add hugegreencandle-evernode-mcp -- npx -y evernode-mcp
What is the Evernode MCP server?
Evernode MCP is listed in the public MCP registry as io.github.Hugegreencandle/evernode-mcp. Evernode/HotPocket dApp helper: templates, non-determinism lint, lease math, live host lookup. This page covers its npm package (evernode-mcp).
Is the Evernode MCP server safe to use?
Evernode MCP scores 73 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Evernode MCP server expose?
Evernode MCP exposes 12 tools: list_templates, generate_contract, check_determinism, check_contract_api, recommend_pattern, and 7 more. Their descriptions and schemas cost roughly 1,398 tokens of context every time the server is loaded.
Is the Evernode MCP server still maintained?
Evernode MCP is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Evernode MCP server under?
Evernode MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.