BlockReq
REMOTE · MCP.BLOCKREQ.COM · 2 COMPONENTS
Read-only BlockReq docs, network catalog, and JSON-RPC calls across EVM chains
Available components
Last scanned (17 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 727 tokens (~121/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://mcp.blockreq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=blockreq.com | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b77f358f50cdf91d13857481efad689e |
| SANs: blockreq.com, mcp.blockreq.com, *.mcp.blockreq.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.blockreq.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| blockreq.com. | present | 2371 | 13 | Verified |
| mcp.blockreq.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.blockreq.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.blockreq.com/mcp | HTTPS enforced | 301 | https://mcp.blockreq.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_rpc Call a read-only JSON-RPC method ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Network slug (for example ethereum, base, arbitrum-sepolia), catalog id, hostname, name, or EVM chain ID (1 or 0x1) |
| method | string | yes | – |
| params | array | – | Positional JSON-RPC params; a missing block parameter means latest |
No output schema declared.
No examples provided.
get_chain Get one BlockReq network ~79
Get one network's URLs and capability flags, its API reference page, and (for EVM networks) the JSON-RPC methods documented for it.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Network slug (for example ethereum, base, arbitrum-sepolia), catalog id, hostname, name, or EVM chain ID (1 or 0x1) |
No output schema declared.
No examples provided.
get_doc_page Read a BlockReq docs page ~59
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Docs page URL or path |
No output schema declared.
No examples provided.
get_method_reference Get a JSON-RPC method reference ~98
Get the documented parameters, result, example, and endpoints of one JSON-RPC method on one EVM network, from BlockReq's OpenRPC document.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Network slug (for example ethereum, base, arbitrum-sepolia), catalog id, hostname, name, or EVM chain ID (1 or 0x1) |
| method | string | yes | JSON-RPC method, for example eth_getLogs |
No output schema declared.
No examples provided.
list_chains List BlockReq networks ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| network_type | string | – | Only this network type |
No output schema declared.
No examples provided.
search_docs Search BlockReq docs ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most results to return (default 5) |
| locale | string | – | Docs language; defaults to the query's language |
| query | string | yes | Words to search for |
No output schema declared.
No examples provided.
How do I install the BlockReq MCP server?
BlockReq is a hosted endpoint at https://mcp.blockreq.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.blockreq.com
claude mcp add --transport http com-blockreq-rpc 'https://mcp.blockreq.com/mcp'
What is the BlockReq MCP server?
BlockReq is an MCP server listed in the public MCP registry as com.blockreq/rpc. Read-only BlockReq docs, network catalog, and JSON-RPC calls across EVM chains. This page covers its hosted endpoint (https://mcp.blockreq.com/mcp).
Is the BlockReq MCP server safe to use?
BlockReq scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BlockReq MCP server expose?
BlockReq exposes 6 tools: list_chains, get_chain, search_docs, get_doc_page, get_method_reference, call_rpc. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.
Does the BlockReq MCP server require authentication?
No. We connected to BlockReq without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BlockReq MCP server still maintained?
BlockReq is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.