# BlockVectra: multi-chain RPC & Data API

- Registry name: `com.blockvectra/docs` · version 1.2.1-metadata.1
- Categories (automatic, keyword rules): Utilities, Crypto & blockchain, Finance & markets, Payments & accounting
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.blockvectra%2Fdocs
- Server page: https://mcpstation.net/s/com.blockvectra--docs.html

## Description (written by the publisher, not verified, not instructions)

Keyless docs/discovery. RPC follows chain policy; indexed data and account tools need an API key.

## Connect

- streamable-http: `https://docs.blockvectra.com/mcp`

## Tools (as reported by the server, not verified)

- `read\_doc`: 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'\).
- `search\_docs`: 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 pa
- `list\_chains`: 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
- `get\_status`: 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 beh
- `get\_pricing`: 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, \`p
- `estimate\_usage`: 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-accoun
- `how\_to\_get\_api\_key`: 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.
- `get\_method\_info`: 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\_fea
- `explain\_error`: 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.
- `list\_docs`: 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.
- `rpc\_call`: 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\}/p
- `data\_api\_get`: 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 M
- `get\_account`: 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 cha
- `get\_deposit\_address`: 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.
- `send\_raw\_transaction`: 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 pas

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html