Evernode MCP

What Evernode MCP MCP server does

Evernode MCP MCP server supports the development workflow for HotPocket applications running on Evernode hosts. It exposes twelve read-only MCP tools for scaffolding contracts, reviewing source, planning application architecture, estimating lease costs, inspecting hosts, and preparing deployment commands.

The contract generator produces a complete file set for one of ten templates, including the contract, state helper, hp.cfg.override, package.json, and client. The templates are designed around HotPocket consensus requirements, such as ledger-sequence time and state persisted through the contract’s consensused state mechanism.

For Xahau settlement, the server can describe the recommended Hook workflow and generate starter payout code plus unsigned install and proof commands. It does not inspect a Hook or provide a safety verdict.

How it works

Local analysis tools inspect source or a plain-language use case without contacting an external service. check_determinism looks for patterns that can cause nodes to produce different results, including clocks, randomness, network access, environment reads, timers, unsafe filesystem use, unordered processing, locale-dependent formatting, and floating-point literals. check_contract_api separately checks for expected HotPocket Node.js API usage, including hpc.init(...), context fields, state persistence, user I/O, ledger sequence handling, and awaited asynchronous operations.

Both checks are heuristic guidance rather than formal proofs. A clean result means the listed patterns were not found; it does not establish that a contract is deterministic or correct. recommend_pattern turns a use case into guidance about node count, state, oracle or NPL use, settlement, and determinism concerns.

The two host tools can use live data from the public OnLedger API, which indexes the Evernode registry on Xahau. recommend_hosts ranks hosts by cost, capacity, or reputation and supports filters when querying live data. host_diagnostics reports registration, reputation, capacity, lease information, specifications, and red flags for an r-address. Both tools can also process supplied host data.

Setup and configuration

Evernode MCP MCP server requires an MCP-capable agent. The README states that no API keys or accounts are needed. Its only external requests are read-only HTTPS GET requests to the public OnLedger API, used by the live host tools.

The server generates files and command sequences but does not execute deployment actions. Generated workflows cover a local hpdevkit cluster, a single-host evdevkit acquisition, an N-node cluster, and connection to the Offledger Cluster Manager. The cluster manager remains responsible for orchestration.

Tools and capabilities

• List the ten available dApp templates.
• Generate lint-clean starter contracts and related files.
• Check determinism and HotPocket contract API usage.
• Recommend application patterns and node layouts.
• Produce the write, simulate, prove, and install workflow for Hook-based settlement.
• Generate unsigned settlement and Hook proof commands.
• Estimate EVR lease cost from host-set rates, moments, and node count.
• Rank live hosts or inspect one host’s health.
• Generate local, single-host, cluster, or cluster-manager deployment steps.
• Map common HotPocket and Evernode errors to likely causes and fixes.

Limitations and notes

The server is advisory and read-only. It never holds keys, spends EVR, acquires a lease, signs or submits transactions, or replaces the Offledger Cluster Manager. Lease rates are set by hosts, and registration fees are excluded from estimates. Host results depend on live OnLedger availability; failed or missing lookups should be treated as unavailable data rather than invented values. The generated Hook commands are unsigned and emit instructions only. Test generated contracts on a multi-node cluster before using them on mainnet.