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.

Choose your installed client below. Each entry adds the documentation endpoint as blockvectra-docs-only; no headers are needed.

For Gemini CLI, run the command from a trusted project directory. It adds the connection to the project's .gemini/settings.json; configure your model provider separately.

For a first read, ask your agent to call search_docs with your task, then call read_doc with the path from a result and the same lang. To read the quickstart directly, call read_doc with {"path":"quickstart","lang":"en"}. For a runnable example, see the documentation guide.

Then 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."

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.

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.

OpenCode (docs-only)

Check opencode --version, then merge this server into your project's existing opencode.json rather than replacing the file. No BlockVectra account or key is needed for the docs-only connection; your model client or provider is configured separately.

OpenCode 2 puts the server under mcp.servers:

{

"$schema": "https://opencode.ai/config.json", "mcp": { "servers": { "blockvectra-docs-only": { "type": "remote", "url": "https://docs.blockvectra.com/mcp/docs", "oauth": false } } } }

OpenCode 1 places the same object directly under mcp (mcp.blockvectra-docs-only).

Run opencode mcp list from the project and confirm blockvectra-docs-only is connected. See the official v2 and v1 MCP guides for your version.

First documentation read with Python

With Python 3.11+ and uv, run the example directly from its fixed commit; no Git checkout is needed:

uv run --script https://raw.githubusercontent.com/blockvectra/agent-quickstart/07b2d89f0ab9129c011d8b135dec441c6bde1f04/examples/mcp_docs.py

To inspect or edit the example locally, use the fixed-version Git checkout:

git clone --branch python-mcp-docs-2026.11.06 --depth 1 https://github.com/blockvectra/agent-quickstart.git

cd agent-quickstart uv run examples/mcp_docs.py

uv installs the pinned mcp==2.3.0 client dependency. The example connects to /mcp/docs, lists search_docs and read_doc, then reads the English quickstart page. It prints JSON with the tool names and full Markdown text. No BlockVectra account, API key, wallet or model API is needed; this task only reads documentation.

Pydantic AI

For a Pydantic AI project, run the fixed-version example with Python 3.11+ and uv, without cloning:

uv run --no-project --script --python 3.11 https://raw.githubusercontent.com/blockvectra/agent-quickstart/1f14f9ec159ed5f3d417876167cdb37e13579c8d/examples/pydantic_docs.py

It uses MCPToolset with pinned pydantic-ai-slim[mcp]==2.66.0, fastmcp==4.1.6 and mcp==2.3.0 to search for quickstart and read that English page. It prints the Markdown in JSON and needs no model, BlockVectra account, wallet or API key. The toolset closes on success or failure. See the example's setup and timeout details. This is a direct documentation-tool read, not a model-driven agent run.

OpenAI Agents SDK and mcp-use

• Python / OpenAI Agents SDK: follow the search-and-read example for setup and the run command.
• Node.js / mcp-use: follow the standalone npm example for its Node.js requirements, installation and run commands.

Both examples connect to /mcp/docs, search the documentation and read a returned page without a model or BlockVectra credentials.

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.

Related case study: An RPC failure is not an empty event range — an upstream-merged fix with offline regressions and explicit coverage limits.

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

| Claude Code plugin (MCP server + blockvectra-rpc skill) | /plugin marketplace add blockvectra/mcp, then /plugin install blockvectra-docs@blockvectra | [Create a marketplace](https://code.claude.c