BlockVectra Docs: Robinhood Chain & EVM

BlockVectra MCP server

Remote Model Context Protocol server for BlockVectra: multi-chain EVM JSON-RPC, indexed Data API, docs, CU pricing and status. Documentation, discovery, pricing and status need no API key. Keyless RPC depends on each chain's public method policy; indexed Data API and account tools require your own BlockVectra API key.

中文

Documentation-only remote connection

For setup answers with source links, connect directly to https://docs.blockvectra.com/mcp/docs using Streamable HTTP. It exposes only search_docs and read_doc, needs no BlockVectra account or API key, and requires no local bridge or package installation.

For remote URL settings below, use this URL and a distinct server name such as blockvectra-docs-only. Packaged plugins and stdio commands keep their existing scopes. With ToolHive, keep --target-uri set to the origin and put /mcp/docs on the loopback client URL. Ask: "Find the Robinhood Chain setup guide, read it, and cite the source. Separate mainnet from testnet; do not run RPC or send a transaction."

The server enforces the two-tool scope, including when a key is supplied. For chain discovery, RPC, indexed data or account tools, use the full https://docs.blockvectra.com/mcp connection described below. Keep the two connections under separate names if you need both.

Registry version 2.0.0 of com.blockvectra/docs points to this two-tool documentation endpoint. Existing 1.x registry versions describe the full /mcp endpoint; use /mcp directly when you need discovery, RPC or authenticated data tools.

Robinhood Chain mainnet and testnet tasks

Use the chain RPC guide for mainnet public read-only RPC tasks. Use the testnet starter and faucet guide for testnet tasks. Mainnet public reads do not require claiming testnet tokens first.

Connect to https://docs.blockvectra.com/mcp without headers for documentation and discovery. Robinhood Chain public endpoints allow supported RPC reads without a key; methods outside the public policy require an API key. Faucet claims require x-api-key. HTTP 202 means accepted; check the transaction receipt for on-chain inclusion (status: "0x1"), which is not finality.

For a first mainnet RPC check before configuring an MCP client, use the fixed-version keyless TypeScript Quickstart. With Node.js 22 (>=22.18) or Node.js >=24.12, and Git, run:

git clone --branch keyless-chain-id-2026.11.02 --depth 1 https://github.com/blockvectra/agent-quickstart.git

cd agent-quickstart node src/public-read-cli.ts

To read another chain, pass its decimal chain ID: node src/public-read-cli.ts 56 for BNB Smart Chain, 1 for Ethereum mainnet, or 57073 for Ink. With no argument, the default is Robinhood mainnet (4663).

No dependency installation, wallet, account or API key is needed. The reader checks the chain directory, verifies the chain ID, then reads the latest block number: at most three HTTP requests, including two RPC calls. It stops before RPC if the directory does not advertise the required public endpoint and methods.

Read HoodFi name records on Robinhood Chain

For an address stored under a HoodFi name, follow the HoodFi name-record guide. It selects Robinhood coin type 2147488311 and compares coin type 60 at the same canonical block hash. A missing or invalid Robinhood record stops the read; coin type 60 is not a fallback. If the records differ, confirm the Robinhood destination before using it.

With the documentation connection above, ask: "Find and read the HoodFi name-record guide. Explain how to select the Robinhood record, compare the two coin types at one block hash, and stop on errors. Cite the source; do not run RPC or send a transaction."

Reading the guide needs no key. Running its four-request diagnostic requires your own API key in the x-api-key header on the keyed RPC endpoint. Keep credentials out of prompts and tool arguments. The diagnostic reads records only; it does not send funds.

Documentation Skill for coding agents

For source-linked setup answers, install the blockvectra-docs Skill from your project directory with Node.js 22.20 or newer. Choose the command for your agent; these project-scoped commands skip installer prompts:

# Codex

npx --yes skills@1.7.4 add blockvectra/agent-quickstart --skill blockvectra-docs --agent codex --yes

Claude Code

npx --yes skills@1.7.4 add blockvectra/agent-quickstart --skill blockvectra-docs --agent claude-code --yes

Try: "How do I get started on Robinhood Chain? Separate mainnet from testnet and cite the docs."

The Skill uses a configured BlockVectra MCP connection (search_docs, then read_doc) or your agent's HTTP reader to find and read Markdown pages. Documentation lookup needs no BlockVectra account or API key. Follow the MCP setup below to configure a server connection for RPC, indexed data and account tools.

Install in one step

Before connecting, you can check AI Anytime's independent report for the latest MCP initialization and tool-discovery results. These checks cover the MCP connection, not individual blockchain RPC calls.

Server URL (Streamable HTTP, no key needed): https://docs.blockvectra.com/mcp

The Cursor config value is the base64 of {"url":"https://docs.blockvectra.com/mcp"}. The VS Code link is the URL-encoded JSON server configuration.

The plugin is described by .claude-plugin/marketplace.json and .claude-plugin/plugin.json. It installs the blockvectra MCP server from .mcp.json and, as a dependency, the blockvectra-rpc skill from blockvectra/skills.

• Endpoint: https://docs.blockvectra.com/mcp (Streamable HTTP, stateless)
• Auth: optional x-api-key header (a BlockVectra API key). Authorization: Bearer is also accepted. Without a key you can use the documentation, chain, pricing and status tools, and the JSON-RPC methods that a chain's public endpoint allows.
• Never put API keys or private keys in tool arguments or chat; the server reads the key only from HTTP headers.

Chains, prices and limits change, so this README does not list them. Read them live:

• Supported chains: GET https://api.blockvectra.com/v1/chains
• Plans, prices and limits: GET https://console-api.blockvectra.com/v1/plans
• Service status: GET https://api.blockvectra.com/v1/status

More: BlockVectra for agents and AI agents guide.

Try a first chain read

With the keyless MCP connection above, give your agent this task:

Call list_chains once and find Ink (chain ID 57073). Use its returned chain slug. Continue only if its public.url exists and public.methods includes both eth_chainId and eth_blockNumber. Call rpc_call with that chain, method="eth_chainId" and params=[]; decode the hexadecimal result and stop unless it equals 57073. Then call rpc_call with the same chain, method="eth_blockNumber" and params=[]. Show the chain ID, returned block number and UTC observation time. Stop on an error; do not retry, register, create a key or send a transaction.

This task uses at most three MCP tool calls, sequentially. It needs no wallet, account, API key, repository checkout or local Node.js. A successful read checks chain identity and obtains a block number; it does not verify historical coverage, indexing freshness or performance. If you connected the documentation-only stdio entry below, it exposes only search_docs and read_doc; use the full remote connection above for this task.

Local stdio bridge

Use Node.js 22 or newer to run the MIT-licensed stdio bridge:

npx --yes --package @blockvectra/mcp@0.1.0 blockvectra-mcp

This uses the published npm release 0.1.0. For documentation only, use the versioned GitHub package below.

Configure a stdio client:

{

"mcpServers": { "blockvectra-docs": { "command": "npx", "args": ["--yes", "--package", "@blockvectra/mcp@0.1.0", "blockvectra-mcp"] } } }

For a source checkout, run npm ci, then use node with the absolute path to src/cli.js instead.

The CLI always bridges to https://docs.blockvectra.com/mcp; it accepts no command-line arguments. Optionally supply BLOCKVECTRA_API_KEY through the child process environment or your client's private environment settings. It is forwarded only as x-api-key. Never put a key in CLI arguments, tool arguments, or chat; never supply private keys.

The default entry connects the official StreamableHTTPClientTransport and StdioServerTransport directly, without rebuilding capabilities or tools. It preserves initialize parameters/results, capabilities, instructions, protocolVersion, tool results, JSON-RPC errors, notifications and bidirectional requests at the JSON message level (not byte formatting). After a successful initialize response, it sets the HTTP transport's negotiated protocol version b