BlockReq

com.blockreq/rpc

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

Yes, your AI can use this right now.Answered a live MCP handshake in 170 ms with no sign-in needed and exposes 6 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://mcp.blockreq.com/mcp

6 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
list_chainsread-only

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_chainread-only

Get one network's URLs and capability flags, its API reference page, and (for EVM networks) the JSON-RPC methods documented for it.

search_docsread-only

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_pageread-only

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_referenceread-only

Get the documented parameters, result, example, and endpoints of one JSON-RPC method on one EVM network, from BlockReq's OpenRPC document.

call_rpcread-only

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 their plan's limits and history. eth_getLogs needs numeric fromBlock/toBlock at most 1000 blocks apart,

Alternatives in Productivity

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”