OpenRPC MCP Server

MCP server by OpenRPC maintainer shanejonas that enables AI agents to interact with OpenRPC-described JSON-RPC APIs — including Ethereum and other blockchain node APIs. Parses OpenRPC specification documents and generates dynamic MCP tools from the spec, enabling agents to call any JSON-RPC method defined in an OpenRPC document.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools openrpc json-rpc api-spec mcp-server ethereum blockchain rpc
⚙ Agent Friendliness
72
/ 100
Can an agent use this?
🔒 Security
80
/ 100
Is it safe for agents?
⚡ Reliability
66
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
68
Documentation
70
Error Messages
68
Auth Simplicity
85
Rate Limits
78

🔒 Security

TLS Enforcement
90
Auth Strength
80
Scope Granularity
75
Dep. Hygiene
75
Secret Handling
80

Blockchain transactions are irreversible. Never pass private keys through MCP. Read-only RPC calls are safe; write operations need explicit authorization. HTTPS to JSON-RPC endpoints.

⚡ Reliability

Uptime/SLA
65
Version Stability
68
Breaking Changes
65
Error Recovery
68
AF Security Reliability

Best When

An agent needs to interact with Ethereum nodes, blockchain RPC endpoints, or other JSON-RPC services that have OpenRPC specifications — dynamically generating tools from the spec rather than hardcoding API calls.

Avoid When

Your target API is REST (not JSON-RPC), or doesn't have an OpenRPC specification document. The OpenRPC ecosystem is primarily used in blockchain/Ethereum contexts.

Use Cases

  • Calling Ethereum and EVM JSON-RPC methods from blockchain agent workflows
  • Dynamically generating MCP tools from OpenRPC specification documents
  • Interacting with any JSON-RPC API that has an OpenRPC spec from integration agents
  • Testing and exploring JSON-RPC APIs from development agents

Not For

  • REST API integration (OpenRPC is JSON-RPC specific, not REST)
  • APIs without OpenRPC specification documents
  • Simple HTTP API calls (use fetch/HTTP MCPs for REST APIs)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: api_key
OAuth: No Scopes: No

Authentication depends on the JSON-RPC endpoint being used. Ethereum nodes may require API keys (Infura, Alchemy). Configure endpoint URL and auth per JSON-RPC provider.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Free open source from OpenRPC project maintainer shanejonas. Underlying JSON-RPC endpoint costs vary (public Ethereum nodes are free, Infura/Alchemy have paid tiers).

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • OpenRPC is primarily used in blockchain/Ethereum ecosystems — limited use outside that context
  • Dynamic tool generation from OpenRPC spec may produce many tools — agents need to select correctly
  • Blockchain write transactions via JSON-RPC are irreversible — require explicit user confirmation
  • By the OpenRPC project maintainer — higher quality than average community MCP

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for OpenRPC MCP Server.

$99

Scores are editorial opinions as of 2026-03-06.

5220
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered