
blockvectra/mcp
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
BlockVectra MCP for AI agents: Robinhood Chain and multi-chain EVM RPC; keyless docs/discovery; RPC follows chain policy; Data API/account tools require an API key.
개요
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. 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 keyless TypeScript Quickstart. With Node.
README
원문 README의 일부입니다. 원문 보기.
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.
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 keyless TypeScript Quickstart. With Node.js >=24.12 and Git, it runs without installing dependencies: it reads the chain directory, verifies the chain ID, and reads the latest block number, with no wallet, account or API key.
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, then select your agent:
npx --yes [email protected] add blockvectra/agent-quickstart --skill blockvectra-docs
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
Server URL (Streamable HTTP, no key needed): https://docs.blockvectra.com/mcp
| Client | One-line install | Source |
|---|---|---|
| Claude Code | claude mcp add --transport http blockvectra-docs https://docs.blockvectra.com/mcp |
MCP in Claude Code |
| Codex | codex mcp add blockvectra --url https://docs.blockvectra.com/mcp |
Codex MCP setup |
설치
npx --yes --package @blockvectra/[email protected] blockvectra-mcp설정
{
"mcpServers": {
"blockvectra-docs": {
"command": "npx",
"args": ["--yes", "--package", "@blockvectra/[email protected]", "blockvectra-mcp"]
}
}
}