ChainRPC MCP
NPM · CHAINRPC-MCP · 2 COMPONENTS
Safety-first EVM and Bitcoin RPC tools for balances, contracts, blocks, and transactions
Available components
Last scanned (18 hours ago)
Scores higher than 65% 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 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
- 30 of 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 64 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 768 tokens (~42/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 6% 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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.
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 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.
- 13 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Oct 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.
- 11 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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/chainrpc-mcp@2.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 110 packages
| Packages resolved | 110 |
|---|---|
| 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 →
btc_broadcastTransaction ~75
Validate and broadcast an already-signed Bitcoin transaction. Disabled unless ALLOW_BITCOIN_BROADCAST=true; never signs or stores keys.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation | string | yes | – |
| expectedNetwork | string | yes | – |
| maxFeeRateBtcPerKvB | number | – | – |
| rawTransaction | string | yes | – |
No output schema declared.
No examples provided.
btc_decodeRawTransaction ~27
Decode a serialized Bitcoin transaction without broadcasting it.
| Name | Type | Req | Description |
|---|---|---|---|
| rawTransaction | string | yes | – |
No output schema declared.
No examples provided.
btc_estimateFee ~39
Estimate a Bitcoin fee rate for confirmation within a target number of blocks.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationTarget | integer | yes | – |
| mode | string | – | – |
No output schema declared.
No examples provided.
btc_getAddressBalance ~49
Scan the Bitcoin UTXO set for an address and return its confirmed spendable outputs. This is not address history and shared RPC nodes may reject concurrent scans.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
btc_getBlock ~33
Read a Bitcoin block by height or hash with selectable verbosity.
| Name | Type | Req | Description |
|---|---|---|---|
| block | – | yes | – |
| verbosity | integer | – | – |
No output schema declared.
No examples provided.
btc_getBlockchainInfo ~23
Return Bitcoin network, chain height, sync, and pruning information.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
btc_getTransaction ~45
Read a raw Bitcoin transaction by txid. A block hash can make confirmed transaction lookup more reliable.
| Name | Type | Req | Description |
|---|---|---|---|
| blockHash | string | – | – |
| txid | string | yes | – |
No output schema declared.
No examples provided.
btc_getTxOut ~54
Read an unspent Bitcoin transaction output. Returns null when the output is spent or unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| includeMempool | boolean | – | – |
| txid | string | yes | – |
| vout | integer | yes | – |
No output schema declared.
No examples provided.
evm_broadcastTransaction ~64
Preflight and broadcast an already-signed EVM transaction. Disabled unless ALLOW_EVM_BROADCAST=true; never signs or stores keys.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation | string | yes | – |
| expectedChainId | integer | yes | – |
| rawTransaction | string | yes | – |
No output schema declared.
No examples provided.
evm_call ~65
Run a read-only eth_call with pre-encoded calldata. This never submits a transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| block | string|number | – | – |
| data | string | – | – |
| from | – | – | – |
| to | string | yes | – |
| valueWei | string|number | – | – |
No output schema declared.
No examples provided.
evm_estimateTransaction ~29
Estimate gas for an unsigned EVM transaction. Values are accepted as decimal or hex quantities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evm_getBlock ~37
Read an EVM block by number, tag, or block hash.
| Name | Type | Req | Description |
|---|---|---|---|
| block | – | yes | – |
| includeTransactions | boolean | – | – |
No output schema declared.
No examples provided.
evm_getBlockNumber ~23
Return the latest EVM block number from the configured endpoint.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evm_getChainInfo ~22
Return the EVM chain ID and upstream client version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evm_getLogs ~25
Read EVM event logs using an address/topics filter and bounded block range.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evm_getNativeBalance ~56
Read an address native-token balance at an EVM block without requiring a wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| block | string|number | – | Block number or latest, earliest, pending, safe, or finalized |
No output schema declared.
No examples provided.
evm_getTransaction ~29
Read an EVM transaction and its receipt by transaction hash.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
No output schema declared.
No examples provided.
evm_readContract ~73
Encode, execute, and decode a read-only smart-contract function using a supplied JSON ABI.
| Name | Type | Req | Description |
|---|---|---|---|
| abi | array | yes | JSON ABI entries needed for this function |
| address | string | yes | – |
| args | array | – | – |
| block | string|number | – | – |
| functionName | string | yes | – |
No output schema declared.
No examples provided.
How do I install the ChainRPC MCP server?
ChainRPC MCP runs locally as an npm package, launched with npx -y chainrpc-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 · chainrpc-mcp
claude mcp add john0n1-chainrpc-mcp -- npx -y chainrpc-mcp
What is the ChainRPC MCP server?
ChainRPC MCP is listed in the public MCP registry as io.github.John0n1/chainrpc-mcp. Safety-first EVM and Bitcoin RPC tools for balances, contracts, blocks, and transactions. This page covers its npm package (chainrpc-mcp).
Is the ChainRPC MCP server safe to use?
ChainRPC MCP scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting 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 ChainRPC MCP server expose?
ChainRPC MCP exposes 18 tools: evm_getBlockNumber, evm_getChainInfo, evm_getNativeBalance, evm_getBlock, evm_getTransaction, and 13 more. Their descriptions and schemas cost roughly 768 tokens of context every time the server is loaded.
Is the ChainRPC MCP server still maintained?
ChainRPC 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 ChainRPC MCP server under?
ChainRPC 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.