INDIVIDUAL MCP TOOL
how_to_get_api_key
Get instructions and endpoints for obtaining a BlockVectra API key via preferred programmatic SIWE sign-up or browser handoff, plus authentication header and URL formats for JSON-RPC and Data API.
LIVE ENDPOINT
https://docs.blockvectra.com/mcp
Connect to this endpoint to inspect the live schema for how_to_get_api_key and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- A tool name, description or schema mentions credentials.
- A tool name or description suggests retrieving external content.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.blockvectra-docs]
url = "https://docs.blockvectra.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"blockvectra-docs": {
"type": "http",
"url": "https://docs.blockvectra.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: blockvectra-docs
Remote MCP URL: https://docs.blockvectra.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"blockvectra-docs": {
"url": "https://docs.blockvectra.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"blockvectra-docs": {
"type": "http",
"url": "https://docs.blockvectra.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "blockvectra-docs",
"transport": "streamable-http",
"url": "https://docs.blockvectra.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
read_doc— Read the raw Markdown content of a documentation page from /md/{lang}/{path}.md.search_docs— Find documentation by topic or task keywords when the page path is unknown.list_chains— Fetch supported blockchain networks and static parameters from `GET /v1/chains`.get_status— Live operational status and network health from `GET /v1/status`.get_pricing— Live prices and plan limits from `GET /v1/plans`.estimate_usage— Calculate projected daily and billing cycle Compute Units (CU) and USD costs for planned call volumes across one or more methods, factoring in method weights and free credit allowances from /v1/plans.get_method_info— Inspect a single method's chain-by-chain availability, Compute Unit (CU) weight, price per million calls, and documentation link.explain_error— Lookup error code, reason, or HTTP status in the official error reference catalog.