MCP stdio bridge 0.1.1 — full and documentation-only

BlockVectra MCP stdio bridge 0.1.1

Use Node.js 22+ to connect a stdio MCP client to BlockVectra.

For documentation only (search_docs and read_doc):

npx --yes --package https://github.com/blockvectra/mcp/releases/download/v0.1.1/blockvectra-mcp-0.1.1.tgz blockvectra-docs-mcp

The documentation entry rejects other tool calls locally and does not forward an inherited API key. It needs no BlockVectra account or API key.

For the full bridge:

npx --yes --package https://github.com/blockvectra/mcp/releases/download/v0.1.1/blockvectra-mcp-0.1.1.tgz blockvectra-mcp

Documentation/discovery need no key; RPC follows each chain's public policy. Data API and account tools need your own API key in the client's private environment settings. Never put a key or private key in CLI arguments or chat.

This is a GitHub archive release. npm still publishes 0.1.0; use the archive URL above for 0.1.1.

Source: 1c73dc54dffad54b9570eb4732fb9bed09cdf104. The archive's eight files match that source; SHA256SUMS is attached. The same 13 mock protocol checks passed against source and the locally installed archive; the three installed executable entries also exited cleanly on EOF. This is package/protocol validation, not an on-chain or customer-use test.

Try a first documentation task

After connecting the docs-only server, ask:

Find the Robinhood Chain mainnet RPC setup and cite the guide. Keep testnet faucet instructions separate.

The two tools are search_docs and read_doc. Search first, then read the returned guide path with the same language. This reads documentation; it does not run RPC calls or send transactions.

Copy the MCP client configuration.