BlockVectra: multi-chain RPC & Data API
by blockvectra.com · remote · no sign-in to list tools · v1.2.0 · published by com.blockvectra
Keyless multi-chain EVM JSON-RPC, indexed Data API, docs, CU pricing and status. API key optional.
15 tools: 1 can delete or cancel things, 2 change things and 12 only read.
Scanned Oct 21, 2026
- Deletes or cancels1Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things2Claude Code: ask: see these tools
- Only reads12Claude Code: allow: see these tools
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http docs https://docs.blockvectra.com/mcpFindings
Matches of fixed checks, with the text they matched.
- Warnrpc_call
The server marks "rpc_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "rpc_call" says "call": a word for a change.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
15 tools
Deletes or cancels 1Claude Code: deny
send_raw_transactionBroadcast a signed raw transaction to a specified blockchain network via eth_sendRawTransaction.No findings
Why it is in this group
- The name "send_raw_transaction" says "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
Changes things 2Claude Code: ask
estimate_usageCalculate 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 allowa…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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. Available without an API key. Estimates the API key count for planned traffic under the free-account `key_defaults` (free new-key default CU/s); the result also echoes `paid_key_minimums` (the paid-account floor, not a cap: the first paid top-up raises each key to at least this value and higher custom limits are kept, and a key's actual limits come from the console Keys list). Cost and quota assumptions are for free-tier accounts. 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'.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
rpc_callExecute 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.1 finding
Why it is in this group
- The name "rpc_call" says "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "rpc_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "rpc_call" says "call": a word for a change.
Description, as the server wrote it 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. Chain slugs look like 'base_mainnet'; take them from list_chains. Without a key the call goes to the keyless endpoint `/v1/{chain}/public` (the chain's `public.url` in list_chains), which only serves the methods listed in that chain's `public.methods`. 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/). With a key, set 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
Only reads 12Claude Code: allow
data_api_getQuery the BlockVectra Data API for a specified chain and path using your BlockVectra API key.No findings
Why it is in this group
- The name "data_api_get" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
explain_errorLookup error code, reason, or HTTP status in the official error reference catalog.No findings
Why it is in this group
- The name "explain_error" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_accountGet the API key's own balance, Compute Units (CU), rate limits, and key parameters from GET /v1/account using your BlockVectra API key.No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
get_deposit_addressRequires an API key.No findings
Why it is in this group
- The name "get_deposit_address" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
get_method_infoInspect a single method's chain-by-chain availability, Compute Unit (CU) weight, price per million calls, and documentation link.No findings
Why it is in this group
- The name "get_method_info" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_pricingLive prices and plan limits from `GET /v1/plans`.No findings
Why it is in this group
- The name "get_pricing" says "get": a word for reading.
Description, as the server wrote it 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 the free-account new-key default CU/s and burst CU; `paid_key_minimums` (when present, otherwise null or absent) are the paid-account per-key lower bounds in CU/s and burst CU — a floor, not a cap, and not any key's actual value (the first paid top-up raises each key to at least this floor and higher custom limits are kept; actual limits are per key in the console). `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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_statusLive operational status and network health from `GET /v1/status`.No findings
Why it is in this group
- The name "get_status" says "get": a word for reading.
Description, as the server wrote it 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'.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
how_to_get_api_keyGet 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-R…No findings
Why it is in this group
- The name "how_to_get_api_key" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_chainsFetch supported blockchain networks and static parameters from `GET /v1/chains`.No findings
Why it is in this group
- The name "list_chains" says "list": a word for reading.
Description, as the server wrote it 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 `eth_getLogs`: the range is inclusive, so `toBlock - fromBlock + 1` must not exceed it, otherwise the call fails with `logs_range_too_large`. `public` describes the keyless endpoint: `public.url` serves only the methods in `public.methods`, and `public.history_blocks` is how far back a block reference may reach on that endpoint (it does not add methods). Pass `chain` (a slug such as `base_mainnet`) to return only that chain.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_docsList all available documentation pages, relative paths, and titles from the static documentation index, including webhook push subscriptions, signatures, delivery and billing.No findings
Why it is in this group
- The name "list_docs" says "list": a word for reading.
Description, as the server wrote it List all available documentation pages, relative paths, and titles from the static documentation index, including webhook push subscriptions, signatures, delivery and billing. Available without an API key.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
read_docRead the raw Markdown content of a documentation page from /md/{lang}/{path}.md.No findings
Why it is in this group
- The name "read_doc" says "read": a word for reading.
Description, as the server wrote it 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').
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
search_docsFind documentation by topic or task keywords when the page path is unknown.No findings
Why it is in this group
- The name "search_docs" says "search": a word for reading.
Description, as the server wrote it Find documentation by topic or task keywords when the page path is unknown. Searches page titles, navigation titles, relative paths, and page summaries, returning titles, relative paths, and summaries. Read a result with read_doc using its path and the same lang; use read_doc directly for a known path or list_docs to browse the documentation catalog. Omit lang for English; limit is 1-20 (default 5). If no results match, try broader keywords or browse list_docs. Available without an API key.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http docs https://docs.blockvectra.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__docs__read_doc",
"mcp__docs__search_docs",
"mcp__docs__list_chains",
"mcp__docs__get_status",
"mcp__docs__get_pricing",
"mcp__docs__how_to_get_api_key",
"mcp__docs__get_method_info",
"mcp__docs__explain_error",
"mcp__docs__list_docs",
"mcp__docs__data_api_get",
"mcp__docs__get_account",
"mcp__docs__get_deposit_address"
],
"ask": [
"mcp__docs__estimate_usage",
"mcp__docs__rpc_call"
],
"deny": [
"mcp__docs__send_raw_transaction"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as docs. Review it before you use it.