BlockVectra MCP

MCP ServerCommunity

BlockVectra MCP provides EVM chain discovery, documentation search, usage pricing, service status, read-only RPC calls and indexed blockchain data queries. Developers and data teams in advisory firms could use it to build digital-asset research and data integrations. The full connection also exposes account information and can broadcast already signed transactions.

evmblockchain datajson-rpcindexed datadeveloper toolstransaction broadcast

Status

Community

Auth

API key

Hosting

Remote

Community rating

Not rated yet

Role

System

Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers → All seven roles →

Open documentation →

Caveats

Capabilities are vendor-reported and not independently verified here. The cited connection checks do not establish successful blockchain RPC calls or live authenticated data access.
Despite the submission's exclusion of trade execution, the vendor's tool table includes send_raw_transaction, which broadcasts already signed transactions and is marked destructive. The full connection is not read-only.
Vendor-reported access rules vary by tool: documentation, discovery, pricing and status are keyless; public RPC depends on chain policy; indexed Data API and account tools require a BlockVectra API key.
The submission describes endpoint-specific data coverage, not a complete portfolio report. The vendor notes that a successful chain read does not verify historical coverage or indexing freshness.
The vendor states that the local stdio bridge forwards requests to its hosted service, including an API key header when configured. It is not a self-hosted backend; data retention and residency are not specified in the supplied material.
The repository and local bridge are vendor-described as MIT-licensed. Hosted usage remains subject to changing plans, CU pricing and limits; the submission excludes custody and investment advice.
Start with read-only scopes and keep client-side approval prompts on until the connection is proven.

Rate this server

How to connect BlockVectra MCP

Step 1

Remote server: paste a URL

BlockVectra MCP publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.

Endpoint

https://docs.blockvectra.com/mcp

Client config snippet

{
  "mcpServers": {
    "843b16d1-3e18-4485-8d2d-d21dfe17e72e": {
      "url": "https://docs.blockvectra.com/mcp"
    }
  }
}

Step 2

Authenticate with API key

Create a key in the vendor's dashboard and store it as an environment variable in your client config. Never paste it into a chat window.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Crypto & Digital Assets.

Digital asset holdings snapshot

One consolidated view across exchanges and wallets.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: consolidate my digital asset holdings across every connected source, exchange accounts, on-chain wallet or explorer tools, and any brokerage account holding crypto or crypto ETPs, into one table: asset, quantity, venue, source tool, USD value and share of total. Show a per-source subtotal so I can see which tool reported what, and flag any asset that appears in more than one source so it is not double-counted. Mask wallet addresses beyond the first and last four characters. Do not trade, transfer, approve or sign anything.

Guardrail · Read-only keys only. Never give a chat tool withdrawal or signing permissions.

Cost basis and realised gains review

A tax-ready view of what was sold and when.

Crypto & Digital AssetsCrypto & Digital AssetsAccounting & Tax

Read-only: list realised gains and losses on digital assets for <tax year> by combining exchange transaction history with on-chain transfer data, then compare the result to what is already recorded in my accounting or tax system. Show acquisition date, disposal date, proceeds, basis and the source tool for each line, and flag every transaction where basis is missing, inferred, or disagrees between the exchange and the books. Do not file, submit, amend or post any journal entry. This is a working draft for the tax preparer.

Guardrail · Draft only. Crypto basis data is often incomplete, verify before filing.

Venue and counterparty risk review

Where the assets actually sit and what that exposes you to.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: map where my digital asset exposure actually sits by combining exchange or custodial venue data, on-chain wallet and staking or DeFi data, and any crypto exposure held through brokerage accounts. For each venue describe the counterparty, smart-contract and liquidity risk, and note any concentration above <threshold>% of total digital assets across all sources combined. State which figures came from which tool and what you could not verify on-chain. No recommendations to move funds and no transactions.

Guardrail · Read-only. Never approve token allowances or transactions from a chat session.

Read the full connection guide →