# BlockReq (remote · mcp.blockreq.com)

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

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `mcp.blockreq.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-blockreq-rpc/mcp.md), [page](https://verifymcp.io/servers/com-blockreq-rpc/mcp)
- remote · `mcp.blockreq.com`: 36/100, [markdown](https://verifymcp.io/servers/com-blockreq-rpc/mcp-account.md), [page](https://verifymcp.io/servers/com-blockreq-rpc/mcp-account)

## Channel facts

- Endpoint: `https://mcp.blockreq.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-blockreq-rpc 'https://mcp.blockreq.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-blockreq-rpc": {
      "url": "https://mcp.blockreq.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-blockreq-rpc": {
      "type": "http",
      "url": "https://mcp.blockreq.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-blockreq-rpc]
url = "https://mcp.blockreq.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-blockreq-rpc": {
      "type": "remote",
      "url": "https://mcp.blockreq.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-blockreq-rpc --url 'https://mcp.blockreq.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-blockreq-rpc:
    url: "https://mcp.blockreq.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-blockreq-rpc": {
      "Transport": "http",
      "Url": "https://mcp.blockreq.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-blockreq-rpc -t streamable-http -u 'https://mcp.blockreq.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-blockreq-rpc": {
      "type": "http",
      "url": "https://mcp.blockreq.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-20 (score 75, +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.

### 2026-10-18 (score 74, +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.

### 2026-10-16 (score 73, +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.

### 2026-10-15 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 72)

First indexed and scored.

## MCP tools (6)

### `list_chains` (~57 tokens)

List BlockReq networks

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.

Input parameters:

- `network_type` (string): Only this network type

### `get_chain` (~79 tokens)

Get one BlockReq network

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

Input parameters:

- `chain` (string, required): Network slug (for example ethereum, base, arbitrum-sepolia), catalog id, hostname, name, or EVM chain ID (1 or 0x1)

### `search_docs` (~95 tokens)

Search BlockReq 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.

Input parameters:

- `limit` (integer): Most results to return (default 5)
- `locale` (string): Docs language; defaults to the query's language
- `query` (string, required): Words to search for

### `get_doc_page` (~59 tokens)

Read a BlockReq docs 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/.

Input parameters:

- `url` (string, required): Docs page URL or path

### `get_method_reference` (~98 tokens)

Get a JSON-RPC method reference

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

Input parameters:

- `chain` (string, required): Network slug (for example ethereum, base, arbitrum-sepolia), catalog id, hostname, name, or EVM chain ID (1 or 0x1)
- `method` (string, required): JSON-RPC method, for example eth_getLogs

### `call_rpc` (~185 tokens)

Call a read-only JSON-RPC method

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.

Input parameters:

- `chain` (string, required): Network slug (for example ethereum, base, arbitrum-sepolia), catalog id, hostname, name, or EVM chain ID (1 or 0x1)
- `method` (string, required)
- `params` (array): Positional JSON-RPC params; a missing block parameter means latest

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-blockreq-rpc/mcp#diagnostics

## Score history

- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.blockreq.com/mcp
- Website: https://blockreq.com/docs/build/ai-assistants/
- Changelog RSS feed: https://verifymcp.io/servers/com-blockreq-rpc/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-blockreq-rpc/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-blockreq-rpc/mcp