bots.st/blockreq
BlockReq
Read docs and run read-only RPC calls
1815 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 6
- Answered
- 4 of the last 4 calls
How to reach it
- MCP, HTTP
https://mcp.blockreq.com/mcp - MCP, HTTP
https://mcp.blockreq.com/mcp/account
What it can do
| Tool | What it says it does |
|---|---|
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… |
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. |
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. |
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. |
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. |
In its maker's words
Read-only BlockReq docs, network catalog, and JSON-RPC calls across EVM chains
- Website
- blockreq.com/docs/build/ai-assistants
- Publisher
- blockreq.com
- Listed from
- the official MCP Registry as
com.blockreq/rpc - Version
- 1.0.0, updated 14 Oct 2026
- Kinds of work
- Crypto and web3, Search and research, AI models and agent tools
The domain it lives on
- blockreq.com
- registered 9 Sep 2025 (1 year ago), at Cloudflare, Inc., its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1815 ms | |
| Answered | 759 ms | |
| Answered | 202 ms | |
| Answered | 202 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.