BlockVectra: multi-chain RPC & Data API
REMOTE · DOCS.BLOCKVECTRA.COM · SCANNED OCT 7
Keyless multi-chain EVM JSON-RPC, indexed Data API, docs, CU pricing and status. API key optional.
Available components
Recent critical change
Authorization (2 Oct 2026). See the changelog before you install this server.
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_raw_transaction). See how to fix → View diagnostics → Fail
- 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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2306 tokens (~153/item across 15 items; 15 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (93% of tools); any adoption earns full credit.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "rpc_call" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the BlockVectra: multi-chain RPC & Data API MCP server?
BlockVectra: multi-chain RPC & Data API is a hosted endpoint at https://docs.blockvectra.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 · docs.blockvectra.com
claude mcp add --transport http com-blockvectra-docs 'https://docs.blockvectra.com/mcp'
{
"mcpServers": {
"com-blockvectra-docs": {
"url": "https://docs.blockvectra.com/mcp"
}
}
} {
"servers": {
"com-blockvectra-docs": {
"type": "http",
"url": "https://docs.blockvectra.com/mcp"
}
}
} [mcp_servers.com-blockvectra-docs] url = "https://docs.blockvectra.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-blockvectra-docs": {
"type": "remote",
"url": "https://docs.blockvectra.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-blockvectra-docs --url 'https://docs.blockvectra.com/mcp' --transport streamable-http
mcp_servers:
com-blockvectra-docs:
url: "https://docs.blockvectra.com/mcp" {
"McpServers": {
"com-blockvectra-docs": {
"Transport": "http",
"Url": "https://docs.blockvectra.com/mcp"
}
}
} assistant mcp add com-blockvectra-docs -t streamable-http -u 'https://docs.blockvectra.com/mcp'
{
"mcpServers": {
"com-blockvectra-docs": {
"type": "http",
"url": "https://docs.blockvectra.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Oct 26 +1
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- Tool “list_docs” rewrote its description, which is the text the model reads security
- 6 Oct 26 +1
- Tool “get_deposit_address” rewrote its description, which is the text the model reads security
- Tool “read_doc” rewrote its description, which is the text the model reads security
- 4 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- New tool “send_raw_transaction”, which the server declares destructive security
- Tool “data_api_get” rewrote its description, which is the text the model reads security
- Tool “get_method_info” rewrote its description, which is the text the model reads security
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- Tool “estimate_usage” rewrote its description, which is the text the model reads security
- Tool “read_doc” rewrote its description, which is the text the model reads security
- Tool “rpc_call” rewrote its description, which is the text the model reads security
- Tool “search_docs” rewrote its description, which is the text the model reads security
- Tool “rpc_call” no longer declares itself destructive security
- Schema quality: 1807 → 2274 ▼ functional
- Destructive annotations: 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "rpc_call" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. functional
- Server version: 1.0.0 → 1.2.0 functional
- New tool “get_deposit_address” functional
- “rpc_call” reworded the description of “method” cosmetic
- “estimate_usage” reworded the description of “calls_per_day” cosmetic
- “estimate_usage” reworded the description of “method” cosmetic
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +2
- Authorization: unverified → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_status” rewrote its description, which is the text the model reads security
- Tool “rpc_call” rewrote its description, which is the text the model reads security
- Tool “rpc_call” is now declared destructive security
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- New tool “get_account” functional
- 1 Oct 26 −9
- Authorization: partial → unverified ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1279 → 1648 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Destructive annotations: pass → 0 functional
- New tool “data_api_get” functional
- New tool “rpc_call” functional
- 30 Sept 26 73
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 9 Oct 2026 · Probed https://docs.blockvectra.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=docs.blockvectra.com | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 69c404920fa470ab0e777b91b1dea7f9 |
| SANs: docs.blockvectra.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 docs.blockvectra.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| blockvectra.com. | present | 2371 | 13 | Verified |
| docs.blockvectra.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://docs.blockvectra.com/mcp | Verified | 200 | |
| http (plaintext) | http://docs.blockvectra.com/mcp | HTTPS enforced | 301 | https://docs.blockvectra.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 →
data_api_get Query Data API ~189
Query the BlockVectra Data API for a specified chain and path using your BlockVectra API key. For endpoint schemas and parameter specifications, see the OpenAPI contract at https://docs.blockvectra.com/openapi/data.yaml. Requires the 'x-api-key' or 'Authorization: Bearer <key>' HTTP header in your MCP client configuration (keys must not be passed in tool parameters or chat). Returns the HTTP status and JSON response body.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Target blockchain network slug (e.g. 'robinhood_mainnet'). |
| path | string | yes | Path after '/v1/data/{chain}/' (e.g. 'status/freshness', 'address/0x.../balances'). Must not start with '/', and cannot contain '..', '//', '?', '#', or '%'. |
| query | object | – | Optional URL query parameters as key-value pairs. |
| Name | Type | Req | Description |
|---|---|---|---|
| _truncated | boolean | – | – |
| balance_units | integer | – | Remaining balance units after this request (only present when balance is known and x-bv-meter: 1 was sent). |
| bytes | integer | – | – |
| cu_charged | integer | – | Compute Units billed for this request (only present when charged and x-bv-meter: 1 was sent). |
| data | – | – | – |
| error | string | – | – |
| status | number | – | – |
No examples provided.
estimate_usage Estimate Usage and Cost ~202
Calculate projected daily and billing cycle Compute Units (CU) and USD costs for planned call volumes across one or more methods, factoring in method weights and free credit allowances from /v1/plans. Also evaluates whether traffic requires multiple API keys under key_defaults. Use this tool for volume budget calculations and capacity planning. For looking up raw system pricing tables, use get_pricing instead. For checking whether a single method is supported on a specific chain, use get_method_info instead. Accepts 'lines' array of {method, calls_per_day} or single 'method' and 'calls_per_day'.
| Name | Type | Req | Description |
|---|---|---|---|
| calls_per_day | integer | – | Expected daily call volume (non-negative integer). Single-method mode. |
| lines | array | – | List of methods and daily call volumes to estimate. |
| method | string | – | Exact method name (e.g. 'eth_call', 'eth_getLogs', 'eth_blockNumber', 'data.address_balances'). Single-method mode. |
| Name | Type | Req | Description |
|---|---|---|---|
| average_calls_per_sec | number | – | – |
| calls_per_day | number | yes | – |
| cu_weight | number|null | – | – |
| cycle_cost_usd | number|null | – | – |
| cycle_cu | number | – | – |
| cycle_days | number | – | – |
| daily_cost_usd | number|null | – | – |
| daily_cu | number | – | – |
| exceeds_free_quota | boolean | – | – |
| exceeds_rate_limit | boolean | – | – |
| free_quota_cu | number|null | – | – |
| max_calls_per_sec | number|null | – | – |
| method | string | yes | – |
| quota_percent | number|null | – | – |
No examples provided.
explain_error Explain Error Code or Reason ~178
Lookup error code, reason, or HTTP status in the official error reference catalog. Returns meaning, billing implications (whether the call was billed), retryability, retry delay, recommended agent action, and documentation URL.
| Name | Type | Req | Description |
|---|---|---|---|
| code | number|string | – | Error code (e.g. -32600, -32005, -32020, or console code string like 'siwe_invalid'). |
| http_status | number | – | HTTP status code (e.g. 200, 400, 402, 404, 429, 500, 503). |
| lang | string | – | Language for explanations: 'en' for English or 'zh' for Chinese. Defaults to 'en'. |
| reason | string | – | Error reason slug (e.g. 'invalid_request', 'key_rate_limit', 'insufficient_balance', 'not_found'). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| errors | array | yes | – |
| matched | boolean | yes | – |
No examples provided.
get_account Get Account Balance and Limits ~106
Get the API key's own balance, Compute Units (CU), rate limits, and key parameters from GET /v1/account using your BlockVectra API key. Free and unbilled. Requires the 'x-api-key' or 'Authorization: Bearer <key>' HTTP header in your MCP client configuration (never pass keys in tool parameters or chat). Returns the account's key_id, plan, balance_units, balance_cu, balance_as_of_age_ms, and key limits.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _truncated | boolean | – | – |
| balance_as_of_age_ms | integer | – | – |
| balance_cu | integer | – | – |
| balance_units | integer | – | – |
| bytes | integer | – | – |
| data | – | – | – |
| error | string | – | – |
| key | object | – | – |
| key_id | string | – | – |
| plan | string | – | – |
| status | number | – | – |
No examples provided.
get_deposit_address Get Deposit Address and Open Networks ~41
Requires an API key. Get your account's dedicated on-chain deposit address and open networks to top up balance; only transfer to the listed networks and tokens.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _truncated | boolean | – | – |
| address | string | – | – |
| bytes | integer | – | – |
| data | – | – | – |
| deposits_url | string | – | – |
| error | string | – | – |
| min_deposit_usd | string | – | – |
| networks | array | – | – |
| status | number | – | – |
No examples provided.
get_method_info Get Method Information ~195
Inspect a single method's chain-by-chain availability, Compute Unit (CU) weight, price per million calls, and documentation link. Check JSON-RPC method policy and Data API dataset coverage separately. JSON-RPC follows methods.allow and methods.deny from /v1/chains. Data API coverage follows data_features in GET /v1/status, with data enabled in /v1/chains. Pricing comes from /v1/plans. For the full system-wide pricing schedule and rate card, use get_pricing instead. For calculating projected bills for expected call volumes across methods, use estimate_usage instead.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Optional chain slug (e.g. 'robinhood_mainnet'). If specified, only availability for this chain is returned. |
| method | string | yes | Method name (e.g. 'eth_call', 'eth_getBalance', 'debug_traceBlockByNumber', 'data.address_balances'). |
| Name | Type | Req | Description |
|---|---|---|---|
| available_chains | array | yes | – |
| chain | string|null | – | – |
| cost_per_million_usd | number|null | – | – |
| cu_weight | number|null | – | – |
| docs_url | string|null | – | – |
| method | string | yes | – |
| notes | string|null | – | – |
| supported | boolean | yes | – |
No examples provided.
get_pricing Get Plans and Pricing ~230
Live prices and plan limits from `GET /v1/plans`. Use before estimating cost or when asked about free credits, rate limits or per-method prices. Units: 1 billing unit = `pricing.cu_per_unit` CU; 1 USD buys `pricing.units_per_usd` units. `method_weights` includes JSON-RPC and Data API CU per call, `push.log` / `push.native_transfer` / `push.token_transfer` per delivered data event, `push.history` per successful history request and `push.address_day` per billable address-day; resolve a method by exact match, then the longest prefix rule ending in `*`, then the `*` row (JSON-RPC only; Data API and push operations have no default). `free.*` values are in billing units; `key_defaults` are per-key CU/s and burst CU. `promo.ends_at` is a sign-up coverage cutoff, not the end of the offer. For a single method's chain support and documentation use get_method_info instead; for projecting cycle costs use estimate_usage instead.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| free | object | – | – |
| key_defaults | object | – | – |
| method_weights | array | yes | – |
| pricing | object | yes | – |
No examples provided.
get_status Get Service and Network Status ~88
Live operational status and network health from `GET /v1/status`. Confirm chain `status` is 'ok' before calling methods; see `list_chains` for static chain capabilities and method policies. For Data API, `data_status` can be 'ok', 'syncing' (queryable and billed normally, but indexing is lagging behind latest block time), or 'unavailable'.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| chains | array | yes | – |
| checked_at | string | yes | – |
| gateway | object | yes | – |
No examples provided.
how_to_get_api_key How to Get API Key ~76
Get instructions and endpoints for obtaining a BlockVectra API key via preferred programmatic SIWE sign-up or browser handoff, plus authentication header and URL formats for JSON-RPC and Data API.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Documentation language: 'en' for English or 'zh' for Chinese. Defaults to 'en'. |
| Name | Type | Req | Description |
|---|---|---|---|
| auth_methods | object | yes | – |
| env_var | string | yes | – |
| handoff_instructions | string | yes | – |
| paths | object | yes | – |
| preferred_path | string | yes | – |
No examples provided.
list_chains List Supported Chains ~81
Fetch supported blockchain networks and static parameters from `GET /v1/chains`. `methods.allow` and `methods.deny` support wildcard patterns where `deny` takes precedence over `allow`. `state_window_blocks` indicates the historical state window in blocks for state queries (null when full history is available); `max_logs_block_range` limits log queries.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| chains | array | yes | – |
No examples provided.
list_docs List Documentation Pages ~62
List all available documentation pages, relative paths, and titles from the static documentation index, including webhook push subscriptions, signatures, delivery and billing. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Published documentation language. Omit for English; unavailable languages return an error. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| docs | array | yes | – |
| lang | string | yes | – |
No examples provided.
read_doc Read Documentation Page ~127
Read the raw Markdown content of a documentation page from /md/{lang}/{path}.md. Path must be an internal relative path (e.g. 'quickstart', 'guides/ai-agents', 'api/json-rpc', 'chains').
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Published documentation language. Omit for English; unavailable languages return an error. |
| path | string | yes | Internal relative documentation path (e.g. 'quickstart', 'guides/ai-agents', 'api/json-rpc'). Do not include protocol, hostname, query string, fragment, or '..'. |
No output schema declared.
No examples provided.
rpc_call Call JSON-RPC Method ~255
Execute a read-only JSON-RPC 2.0 method on a specified blockchain network using your BlockVectra API key, or via the keyless public endpoint if available on the chain. Write methods (such as 'eth_sendRawTransaction') are not supported in rpc_call; use 'send_raw_transaction' instead. Consult the Ethereum JSON-RPC specification (https://ethereum.org/en/developers/docs/apis/json-rpc/) and the BlockVectra method reference (https://docs.blockvectra.com/en/api/json-rpc/methods/). Requires the 'x-api-key' or 'Authorization: Bearer <key>' HTTP header in your MCP client configuration for full access (keys must not be passed in tool parameters or chat). Returns the raw JSON-RPC response from the server.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Target blockchain network slug (e.g. 'robinhood_mainnet'). Must exist in GET /v1/chains. |
| method | string | yes | JSON-RPC 2.0 method name (e.g. 'eth_blockNumber', 'eth_call', 'eth_getLogs'). Write methods are not accepted. |
| params | array | – | Optional JSON-RPC parameter array. Defaults to []. |
| Name | Type | Req | Description |
|---|---|---|---|
| balance_units | integer | – | Remaining balance units after this request (only present when balance is known and x-bv-meter: 1 was sent). |
| cu_charged | integer | – | Compute Units billed for this request (only present when charged and x-bv-meter: 1 was sent). |
| error | object|string | – | – |
| help | object | – | – |
| id | number|string|null | – | – |
| jsonrpc | string | – | – |
| message | string | – | – |
| result | – | – | – |
| signup_url | string | – | Registration and sign-up URL (returned when rate-limited on the public endpoint). |
No examples provided.
search_docs Search Documentation ~98
Search documentation pages using keywords against page title, relative path, and first-paragraph summary. Returns matching page titles, paths, and summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Published documentation language. Omit for English; unavailable languages return an error. |
| limit | number | – | Maximum number of search results to return (1-20, default 5). |
| query | string | yes | Keywords to search for in documentation titles, paths, and summaries. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| results | array | yes | – |
No examples provided.
send_raw_transaction Send Raw Transaction ~146
Broadcast a signed raw transaction to a specified blockchain network via eth_sendRawTransaction. Requires the 'x-api-key' or 'Authorization: Bearer <key>' HTTP header in your MCP client configuration for full access, or uses the keyless public endpoint if permitted on the chain (keys must not be passed in tool parameters or chat). Returns the transaction hash or JSON-RPC error.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Target blockchain network slug (e.g. 'robinhood_mainnet'). Must exist in GET /v1/chains. |
| raw_tx | string | yes | Signed raw transaction data as a 0x-prefixed hex string (the RLP-encoded raw transaction). |
| Name | Type | Req | Description |
|---|---|---|---|
| balance_units | integer | – | Remaining balance units after this request (only present when balance is known and x-bv-meter: 1 was sent). |
| cu_charged | integer | – | Compute Units billed for this request (only present when charged and x-bv-meter: 1 was sent). |
| error | object|string | – | – |
| help | object | – | – |
| id | number|string|null | – | – |
| jsonrpc | string | – | – |
| message | string | – | – |
| result | – | – | – |
| signup_url | string | – | Registration and sign-up URL (returned when rate-limited on the public endpoint). |
No examples provided.
What is the BlockVectra: multi-chain RPC & Data API MCP server?
BlockVectra: multi-chain RPC & Data API is an MCP server listed in the public MCP registry as com.blockvectra/docs. Keyless multi-chain EVM JSON-RPC, indexed Data API, docs, CU pricing and status. API key optional. This page covers its hosted endpoint (https://docs.blockvectra.com/mcp).
Is the BlockVectra: multi-chain RPC & Data API MCP server safe to use?
BlockVectra: multi-chain RPC & Data API scores 68 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 BlockVectra: multi-chain RPC & Data API MCP server expose?
BlockVectra: multi-chain RPC & Data API exposes 15 tools: read_doc, search_docs, list_chains, get_status, get_pricing, and 10 more. Their descriptions and schemas cost roughly 2,074 tokens of context every time the server is loaded.
Does the BlockVectra: multi-chain RPC & Data API MCP server require authentication?
No. We connected to BlockVectra: multi-chain RPC & Data API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BlockVectra: multi-chain RPC & Data API MCP server still maintained?
BlockVectra: multi-chain RPC & Data API is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.