All servers · Crypto & blockchain

BlockReq

com.blockreq/rpc · v1.0.0

Measured by MCP Station

Description written by the publisher, not verified

Read-only BlockReq docs, network catalog, and JSON-RPC calls across EVM chains

Connect

claude mcp add --transport http rpc https://mcp.blockreq.com/mcp

{
  "mcpServers": {
    "rpc": {
      "url": "https://mcp.blockreq.com/mcp"
    }
  }
}

claude mcp add --transport http rpc https://mcp.blockreq.com/mcp/account

{
  "mcpServers": {
    "rpc": {
      "url": "https://mcp.blockreq.com/mcp/account"
    }
  }
}

Tools as reported by the server

• list_chains
  List every published BlockReq network with its host, public trial URL, private URL pattern ({API_KEY} placeholder), WSS support, and archive and proof/debug/trace flags.
• get_chain
  Get one network's URLs and capability flags, its API reference page, and (for EVM networks) the JSON-RPC methods documented for it.
• search_docs
  Search the BlockReq docs (setup, API keys, endpoints, Request Counting, plans, networks, support). Returns page titles, URLs, Markdown URLs for get_doc_page, and snippets. Chinese queries search the Chinese pages.
• get_doc_page
  Read one BlockReq docs page as Markdown. Accepts a https://blockreq.com/docs/... URL (HTML or index.md) or a path such as /docs/getting-started/.
• get_method_reference
  Get the documented parameters, result, example, and endpoints of one JSON-RPC method on one EVM network, from BlockReq's OpenRPC document.
• call_rpc
  Call one read-only JSON-RPC method on an EVM network. Without credentials it uses the public trial endpoint (rate-limited, recent state only); when this MCP connection sends a BlockReq API key or is signed in to a BlockReq account, it uses the caller's own endpoint, metered to their account with the

Website · JSON · Text for agents · Registry updated 2026-10-14