Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.reagost/nerve-rpc

NPM · NERVE-RPC-MCP · SCANNED SEP 20

MCP server for Nerve blockchain JSON-RPC & REST API for AI Agents

Available components

npm · nerve-rpc-mcp 83
0 this week 83 Trust /100
Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 825 tokens (~58/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
Install

How do I install the io.github.reagost/nerve-rpc MCP server?

io.github.reagost/nerve-rpc runs locally as an npm package, launched with npx -y nerve-rpc-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 · nerve-rpc-mcp

# add to Claude Code
claude mcp add reagost-nerve-rpc -- npx -y nerve-rpc-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "reagost-nerve-rpc": {
      "command": "npx",
      "args": [
        "-y",
        "nerve-rpc-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "reagost-nerve-rpc": {
      "command": "npx",
      "args": [
        "-y",
        "nerve-rpc-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add reagost-nerve-rpc -- npx -y nerve-rpc-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reagost-nerve-rpc": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "nerve-rpc-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add reagost-nerve-rpc --command npx --arg -y --arg nerve-rpc-mcp
# ~/.hermes/config.yaml
mcp_servers:
  reagost-nerve-rpc:
    command: "npx"
    args: ["-y", "nerve-rpc-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "reagost-nerve-rpc": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "nerve-rpc-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add reagost-nerve-rpc -t stdio -c npx -a -y nerve-rpc-mcp
// mcp.json
{
  "mcpServers": {
    "reagost-nerve-rpc": {
      "command": "npx",
      "args": [
        "-y",
        "nerve-rpc-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Analysed npm/nerve-rpc-mcp@1.0.2

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 →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~825 tokens

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 →

Tool Tokens
nerve_get_account_balance ~83

Query account balance for a specific asset (chainId, assetChainId, assetId, address)

NameTypeReqDescription
addressstringyesNerve address
assetChainIdintegeryesAsset chain ID
assetIdintegeryesAsset ID
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)

No output schema declared.

No examples provided.

nerve_get_agent_list ~43

Get list of consensus nodes (agents) for the chain

NameTypeReqDescription
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)

No output schema declared.

No examples provided.

nerve_get_balance_list ~70

Query balance list for an address and optional asset IDs

NameTypeReqDescription
addressstringyesNerve address
assetIdListarray–Optional list of asset IDs; omit for all
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)

No output schema declared.

No examples provided.

nerve_get_best_block_header ~50

Get the latest block header (hash, height, txCount, packingAddress, etc.)

NameTypeReqDescription
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)

No output schema declared.

No examples provided.

nerve_get_block_by_hash ~54

Get block (header + transactions) by block hash

NameTypeReqDescription
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)
hashstringyesTransaction or block hash

No output schema declared.

No examples provided.

nerve_get_block_by_height ~52

Get block (header + transactions) by block height

NameTypeReqDescription
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)
heightintegeryesBlock height

No output schema declared.

No examples provided.

nerve_get_deposit_list ~59

Get delegation list for a consensus node (by agent creation tx hash)

NameTypeReqDescription
agentHashstringyesCreate consensus node transaction hash
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)

No output schema declared.

No examples provided.

nerve_get_header_by_height ~48

Get block header only by height

NameTypeReqDescription
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)
heightintegeryesBlock height

No output schema declared.

No examples provided.

nerve_get_latest_height ~42

Get the latest main chain block height for a chain

NameTypeReqDescription
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)

No output schema declared.

No examples provided.

nerve_get_tx ~47

Get transaction by transaction hash

NameTypeReqDescription
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)
hashstringyesTransaction or block hash

No output schema declared.

No examples provided.

nerve_info ~30

Get Nerve chain info (chainId, assetId, symbol, addressPrefix, consensus assets, etc.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

nerve_jsonrpc ~86

Call any Nerve JSON-RPC method by name with params array. Use for methods not covered by dedicated tools (e.g. getRandomSeedByCount, getProposalInfo, swap/farm APIs).

NameTypeReqDescription
methodstringyesJSON-RPC method name (e.g. info, getTx, getSwapPairInfo)
paramsarray–Array of positional parameters

No output schema declared.

No examples provided.

nerve_rest ~108

Call Nerve REST API by path. Method GET by default; pass body for POST. Base URL is from NERVE_API_BASE_URL (default https://api.nerve.network). Example paths: api/info, api/block/header/height/1000, api/tx/{hash}

NameTypeReqDescription
bodyobject–JSON body for POST/PUT
methodstring––
pathstringyesREST path (e.g. api/info or api/block/height/123)

No output schema declared.

No examples provided.

nerve_validate_address ~53

Validate if a Nerve address is correct for the given chain

NameTypeReqDescription
addressstringyesNerve address
chainIdintegeryesNerve chain ID (e.g. 9 for mainnet)

No output schema declared.

No examples provided.

Common questions

What is the io.github.reagost/nerve-rpc MCP server?

io.github.reagost/nerve-rpc is an MCP server listed in the public MCP registry as io.github.reagost/nerve-rpc. MCP server for Nerve blockchain JSON-RPC & REST API for AI Agents. This page covers its npm package (nerve-rpc-mcp).

Is the io.github.reagost/nerve-rpc MCP server safe to use?

io.github.reagost/nerve-rpc scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.reagost/nerve-rpc MCP server expose?

io.github.reagost/nerve-rpc exposes 14 tools: nerve_info, nerve_get_latest_height, nerve_get_best_block_header, nerve_validate_address, nerve_get_account_balance, and 9 more. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.

Is the io.github.reagost/nerve-rpc MCP server still maintained?

io.github.reagost/nerve-rpc is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.reagost/nerve-rpc MCP server under?

io.github.reagost/nerve-rpc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.