mcpbeat Sign in

BlockReq MCP Server

answering

BlockReq is answering right now. Last checked 8 min ago. It exposes 6 tools.

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

Uptime history 12 days of history
12 days agonow
100.0%
Uptime 24h
182 of 182 checks
6
Tools
read from the server
204 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check BlockReq every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add rpc --transport http https://mcp.blockreq.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.blockreq.com/mcp
~/.codex/config.toml
[mcp_servers.rpc]
url = "https://mcp.blockreq.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "rpc": {
      "url": "https://mcp.blockreq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "rpc": {
      "type": "http",
      "url": "https://mcp.blockreq.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

call
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 their plan's limits and history. eth_getLogs needs numeric fromBlock/toBlock at most 1000 blocks apart, or a blockHash. Responses above 256 KB are refused. It cannot sign or send transactions.
chain
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.
chains
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.
doc
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/.
docs
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.
method
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.blockreq.com/mcp streamable-http answering 158 ms 8 min ago
https://mcp.blockreq.com/mcp/account streamable-http sign-in 200 ms 9 min ago

Alternatives to BlockReq

same job, measured the same way
Parallax Protocol
by parallaxprotocol

Read-only Parallax PoW chain data: blocks, transactions, mining, supply, explorer and network health

36 tools answering
Nodeflare MCP
by nodeflare-app

Blockchain JSON-RPC on 23 EVM chains for AI agents - free tier, API key, or x402 pay-per-call.

18 installs/wk local only
LCX Liberty DEX
by lcx-ag

Best-route swap quotes, token search and USD prices across EVM chains. Read-only, never trades.

5 tools answering
Alchemy Nft
by mcparmory

Retrieve NFT metadata, ownership, and contract details across blockchains

220 installs/wk local only
Chainstack
by chainstack

Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.

23 tools answering
Ankr Agent RPC
by w3tech

Read chain data on 200+ networks and Sui: transactions, logs, balances, objects, ABI-decoded.

329 installs/wk 25 tools answering
Harbor Crew Cross-Chain Report
by rocket-harbor-420

Paid read-only reports for 1–5 EVM addresses across four networks; 0.02 supported stablecoin direct.

answering
Slimsnap
by bickov

Your recent screen captures as structured JSON your AI agent can read. Local only, no network.

21 installs/wk local only

BlockReq — questions

Answers built from our own checks of this server.

What can BlockReq do?
It exposes 6 tools, read directly from the server on our last check. Among them: call_rpc, get_chain, get_doc_page, get_method_reference, list_chains, search_docs. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is BlockReq working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 204 ms. The bar chart above shows every period we have measured.
How do I connect BlockReq?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to BlockReq?
No API key is involved. BlockReq answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is BlockReq?
It answers our handshake in 204 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.