接入你的智能体
發布者自己的 URL。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
https://chainrpc-mcp.mitander.io/mcp上方的 Claude 按鈕會開啟 Claude,並填好名稱和 URL。你仍需在那裡確認。
claude mcp add --transport http io.github.john0n1-chainrpc-mcp https://chainrpc-mcp.mitander.io/mcpRun in a terminal.
{ "mcpServers": { "io.github.john0n1-chainrpc-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://chainrpc-mcp.mitander.io/mcp" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
A safety-first Model Context Protocol server for EVM chains and Bitcoin.
ChainRPC MCP gives agents a focused set of tools for balances, blocks, transactions, logs, smart-contract reads, gas and fee estimation, and transaction decoding. It can submit already-signed transactions, but only behind explicit, disabled-by-default safety gates. It never accepts private keys, manages wallets, or signs transactions.
The public endpoint is available now:
https://chainrpc-mcp.mitander.io/mcp
For clients that accept a remote Streamable HTTP server:
{
"mcpServers": {
"chainrpc-mcp": {
"url": "https://chainrpc-mcp.mitander.io/mcp"
}
}
}
Health and upstream status:
curl 'https://chainrpc-mcp.mitander.io/health?upstream=1'
The hosted service is shared, rate-limited, and intentionally has both broadcast features disabled. It is suitable for evaluation and public-chain reads, but has no availability SLA. Requests are visible to the service operator and upstream RPC providers; use your own deployment for sensitive queries or production workloads.
Requirements: Node.js 20 or newer.
npx -y chainrpc-mcp
Example client configuration:
{
"mcpServers": {
"chainrpc-mcp": {
"command": "npx",
"args": ["-y", "chainrpc-mcp"],
"env": {
"EVM_RPC_URL": "https://ethereum-rpc.publicnode.com",
"BITCOIN_RPC_URL": "https://bitcoin-rpc.publicnode.com"
}
}
}
}
The RPC variables are optional; they are shown to make the defaults explicit.
Any HTTP(S) EVM JSON-RPC endpoint can be used, so the same tools work with Ethereum mainnet, testnets, and compatible chains. Results always come from the configured endpoint; callers should inspect evm_getChainInfo before making chain-specific assumptions.
Bitcoin Core is not an address indexer. btc_getAddressBalance uses scantxoutset, which reports currently unspent, confirmed outputs—not history or unconfirmed balance. Only one scan can run on a node at a time, so a shared endpoint may return scan already in progress. Use a dedicated node for frequent address scans.
ChainRPC MCP treats transaction submission as an exceptional operation:
ALLOW_EVM_BROADCAST or ALLOW_BITCOIN_BROADCAST is explicitly enabled.I understand this broadcasts a real transaction.eth_estimateGas first.testmempoolaccept to approve the transaction.RPC responses are untrusted external data. A compromised endpoint can lie about chain state, censor requests, or observe queries. Independently verify high-value decisions, ideally against infrastructure you control.
See SECURITY.md for vulnerability reporting and the complete trust boundary.
Copy example.env to .env when running from a checkout.
GETH_URL remains a deprecated compatibility alias for EVM_RPC_URL. Credentials embedded in RPC URLs are rejected; use the matching username and password variables.
Start a loopback-only HTTP server:
npm start
curl 'http://127.0.0.1:3000/health?upstream=1'
To bind beyond loopback, explicitly set the host allowlist and authentication:
HOST=0.0.0.0 \
ALLOWED_HOSTS=mcp.example.com \
MCP_AUTH_TOKEN='replace-with-a-long-random-secret' \
npm start
Terminate TLS at a trusted reverse proxy, preserve the original Host header, and keep the origin private. A bearer token is useful for a single trusted client; use an OAuth-capable gateway and network access policy for multi-user deployments.
Docker defaults to stdio. Override the command for HTTP:
docker build -t chainrpc-mcp .
docker run --rm -p 127.0.0.1:3000:3000 \
-e HOST=0.0.0.0 \
-e ALLOWED_HOSTS=localhost,127.0.0.1 \
-e MCP_AUTH_TOKEN='replace-with-a-long-random-secret' \
chainrpc-mcp --http
Production service topology:
MCP client
|
v
Cloudflare edge -> outbound-only Cloudflare Tunnel -> nginx on loopback
|
v
ChainRPC MCP
/ \
v v
EVM RPC Bitcoin RPC
Deployment units, nginx configuration, hardening details, and operating commands are in docs/OPERATIONS.md.
git clone https://github.com/John0n1/chainrpc-mcp.git
cd chainrpc-mcp
npm ci
npm run check
npm run test:coverage
Useful commands:
The detailed design and remediation record is in docs/AUDIT.md. Contributions are welcome through issues and pull requests. Please use a private GitHub security advisory—not a public issue—for suspected vulnerabilities.
Safety-first EVM and Bitcoin RPC tools for balances, contracts, blocks, and transactions
{ "mcpServers": { "io.github.john0n1-chainrpc-mcp": { "url": "https://chainrpc-mcp.mitander.io/mcp", "headers": {} } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 http 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:EVM_RPC_URL, BITCOIN_RPC_URL, ALLOW_EVM_BROADCAST, ALLOW_BITCOIN_BROADCAST。
ChainRPC MCP 透過 HTTP 存取。
上次檢查時間:2026-11-09。 Safety-first EVM and Bitcoin RPC tools for balances, contracts, blocks, and transactions