BlockReq

com.blockreq/rpc · v1.0.0 · docs-and-knowledge

BlockReq is healthy: it completed an MCP handshake in 1783 ms and exposes 6 tools. It scores 61/100.

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

Endpoint: https://mcp.blockreq.com/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Score 61/100

health18.9 / 25
authEase15 / 15
toolQuality15 / 15
maintenance7 / 15
adoption0 / 10
usage0 / 10
security5 / 10

Scoring v0.3, computed 2026-10-14T20:26:03.264Z.

Health history

Checked (UTC)StatusLatencyError
2026-10-14T18:20:40.533ZHealthy1783

Tools (6)

list_chainsList 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_chainGet one network's URLs and capability flags, its API reference page, and (for EVM networks) the JSON-RPC methods documented for it.
search_docsSearch 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 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_referenceGet the documented parameters, result, example, and endpoints of one JSON-RPC method on one EVM network, from BlockReq's OpenRPC document.
call_rpcCall 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