ChainRPC MCP

REMOTE · CHAINRPC-MCP.MITANDER.IO · 2 COMPONENTS · SCANNED AUG 20

Safety-first EVM and Bitcoin RPC tools for balances, contracts, blocks, and transactions

Available components

remote · chainrpc-mcp.mitander.io 62 npm · chainrpc-mcp 65

62 62 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (evm_broadcastTransaction). See how to fix → View diagnostics → Fail
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → 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 Management3

Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · chainrpc-mcp.mitander.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http john0n1-chainrpc-mcp https://chainrpc-mcp.mitander.io/mcp

# ~/.codex/config.toml

[mcp_servers.john0n1-chainrpc-mcp]
url = "https://chainrpc-mcp.mitander.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "john0n1-chainrpc-mcp": {
      "type": "remote",
      "url": "https://chainrpc-mcp.mitander.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add john0n1-chainrpc-mcp --url https://chainrpc-mcp.mitander.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  john0n1-chainrpc-mcp:
    url: "https://chainrpc-mcp.mitander.io/mcp"

// mcp.json

{
  "mcpServers": {
    "john0n1-chainrpc-mcp": {
      "type": "http",
      "url": "https://chainrpc-mcp.mitander.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

20 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
19 Aug 26 61

First indexed and scored.

Show 1 earlier entry Hide earlier entries

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 Aug 2026 · Probed https://chainrpc-mcp.mitander.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=mitander.io	CN=WE1,O=Google Trust Services,C=US	19 Aug 2026	17 Nov 2026	ECDSA 256	ECDSA-SHA256	3bbb4ca55a152af40e4226a34f533aba
SANs: mitander.io, *.mitander.io
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of chainrpc-mcp.mitander.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
mitander.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=31536000
content-security-policy	default-src 'none'; frame-ancestors 'none'
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	no-referrer

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://chainrpc-mcp.mitander.io/mcp	Verified	200
http (plaintext)	http://chainrpc-mcp.mitander.io/mcp	HTTPS enforced	308	https://chainrpc-mcp.mitander.io/mcp

MCP tools · 18 exposed · ~768 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.

Tool Tokens

btc_broadcastTransaction ~75

Validate and broadcast an already-signed Bitcoin transaction. Disabled unless ALLOW_BITCOIN_BROADCAST=true; never signs or stores keys.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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.

Input Output Examples

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 Output Examples

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 Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

19 Aug 20 Aug