Blockchain RPC and docs MCP for developers and AI agents

Quick answers

• No key needed: POST https://api.blockvectra.com/v1/<chain>/public works on 29 chains with no account or API key, at 3 requests per second per IP (burst 20, batches of up to 10).

  Source: GET /v1/chains

• Wallet sign-up takes four HTTP calls: request a challenge, sign it with an Ethereum wallet (EIP-191), log in (the first login creates the account), then POST /keys to create an API key.

  Source: programmatic sign-up guide

• One command adds the docs MCP server, no key needed: claude mcp add --transport http blockvectra-docs https://docs.blockvectra.com/mcp

  Source: AI agents guide

• Sign-up gives 30,000,000 CU free with no card. The free plan runs in 30-day cycles at 25 calls per second shared by all keys; eth_call costs 15 CU ($1.50 per 1,000,000 requests).

  Source: GET /v1/plans

• Same rules as people: creating and revoking keys, reading the balance and topping up on-chain are all HTTP calls, not console-only. The MCP server does not create or revoke keys.

  Source: programmatic sign-up guide

Which one should I use?

Keyless docs MCP

The documentation MCP server needs no API key and answers questions about the docs, chains, live status, pricing and usage estimates.

claude mcp add --transport http blockvectra-docs-only https://docs.blockvectra.com/mcp/docs

claude mcp add --transport http blockvectra-docs https://docs.blockvectra.com/mcp

Other clients:

In Cline, open MCP Servers → Configure → Configure MCP Servers and add this configuration without an API key:

{
  "mcpServers": {
    "blockvectra": {
      "type": "streamableHttp",
      "url": "https://docs.blockvectra.com/mcp"
    }
  }
}

List the supported chains and choose one whose public methods allow eth_chainId. Use get_method_info for that chain and method, then call eth_chainId with rpc_call without an API key. Compare the returned ID numerically with the selected chain's published chain_id and report the result and applicable public limits. If the ID is missing, invalid or different, stop and report it instead of claiming success.

For methods that require a key and the Data API, sign up over HTTP and create a key, then follow the Data API guide. To add credit, top up on-chain.

Integration guides

• MCP server Tool list, key requirements and client setup.
• LangChain Give a LangChain agent an RPC tool or the MCP server.
• ElizaOS Point the EVM plugin at BlockVectra endpoints.
• Coinbase AgentKit Use a BlockVectra RPC URL in AgentKit.
• Stock-token activity Read daily stock-token transfer activity from the Data API.

Same rights as people

Over HTTP an agent can create keys (POST /keys), revoke them (POST /keys/{key_id}/revoke), read its balance (GET /v1/account) and top up on-chain, under the same limits and prices as a person using the console.

The MCP server reads docs, chains, status and prices, calls read-only RPC (rpc_call), broadcasts a signed transaction (send_raw_transaction) and, with a key configured in the client, reads the account balance and deposit address. It has no tool that creates or revokes keys; use HTTP for that.

Prices an agent can read

GET /v1/plans returns every method's CU weight as JSON, so cost can be estimated before the first call.

Open GET /v1/plans →

Pay with USDC / USDT / USDG →

Free plan

Machine-readable entry points

Machine-readable files and catalogs, discoverable without an account:

• Main site llms.txt
• Documentation llms.txt
• Markdown copy of every docs page
• OpenAPI 3.1 — JSON-RPC
• OpenAPI 3.1 — Data API
• RFC 9727 API catalog
• Error reference

Copy-paste example

export BLOCKVECTRA_API_KEY=rgw_your_api_key

curl -X POST https://api.blockvectra.com/v1/robinhood_mainnet \
  -H "content-type: application/json" \
  -H "x-api-key: $BLOCKVECTRA_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

No API key yet?

If you have an Ethereum wallet: follow the programmatic sign-up guide to sign up and create an API key without a browser. If you do not have a wallet: ask the user to sign in at https://console.blockvectra.com, create a key, and set it as the environment variable BLOCKVECTRA_API_KEY. Do not ask the user to paste the key into the chat.