Bitpoort MCP — integration guide for AI agents

1. Get a key (no signup, no email)

curl -X POST https://api.bitpoort.com/v1/keys

Response includes api_key (a bp_ string), tier: free, 60 req/min limit, 10,000/day cap, 90-day expiry, usage.docs, usage.agents_landing, usage.discovery_manifest, and the MCP config snippet under usage.mcp.config.

2. Plug into your MCP client

Claude Code (1.0+, native HTTP MCP)

claude mcp add bitpoort \
  --transport http \
  --url https://mcp.bitpoort.com/ \
  --header "X-API-Key: bp_YOUR_KEY"

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json)

{
  "mcpServers": {
    "bitpoort": {
      "type": "http",
      "url": "https://mcp.bitpoort.com/",
      "headers": {"X-API-Key": "bp_YOUR_KEY"}
    }
  }
}

Cursor (~/.cursor/mcp.json or .cursor/mcp.json)

{
  "mcpServers": {
    "bitpoort": {
      "url": "https://mcp.bitpoort.com/",
      "headers": {"X-API-Key": "bp_YOUR_KEY"}
    }
  }
}

VS Code (.vscode/mcp.json, 1.99+ with Copilot Chat)

{
  "servers": {
    "bitpoort": {
      "type": "http",
      "url": "https://mcp.bitpoort.com/",
      "headers": {"X-API-Key": "bp_YOUR_KEY"}
    }
  }
}

Codex / OpenClaw (~/.codex/config.toml, via mcp-remote stdio shim)

[mcp_servers.bitpoort]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.bitpoort.com/", "--header", "X-API-Key:bp_YOUR_KEY"]

Anthropic SDK (Python, MCP Connector beta)

import anthropic
client = anthropic.Anthropic()
response = client.beta.messages.create(
    model="claude-opus-4-7",
    max_tokens=1024,
    mcp_servers=[{
        "type": "url",
        "url": "https://mcp.bitpoort.com/",
        "name": "bitpoort",
        "authorization_token": "bp_YOUR_KEY",
    }],
    messages=[{"role": "user", "content": "What large ETH transfers happened in the last hour?"}],
    extra_headers={"anthropic-beta": "mcp-client-2025-04-04"},
)

OpenAI Agents SDK (Python)

from agents import Agent, Runner
from agents.mcp import MCPServerStreamableHttp

bitpoort = MCPServerStreamableHttp(
    name="bitpoort",
    params={"url": "https://mcp.bitpoort.com/", "headers": {"X-API-Key": "bp_YOUR_KEY"}},
)
async with bitpoort as server:
    agent = Agent(name="onchain-analyst", mcp_servers=[server], model="gpt-4o")
    print((await Runner.run(agent, "Latest whale activity on ETH?")).final_output)

Plain JSON-RPC (curl)

# 1. Initialize -- capture the Mcp-Session-Id header
SESSION_ID=$(curl -sD - -X POST https://mcp.bitpoort.com/ \
  -H "X-API-Key: bp_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}' \
  | awk -F': ' 'tolower($1)=="mcp-session-id"{gsub(/\r/,"",$2);print $2}')

# 2. List tools
curl -X POST https://mcp.bitpoort.com/ \
  -H "X-API-Key: bp_YOUR_KEY" -H "Mcp-Session-Id: $SESSION_ID" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

# 3. Call ask_blockchain
curl -X POST https://mcp.bitpoort.com/ \
  -H "X-API-Key: bp_YOUR_KEY" -H "Mcp-Session-Id: $SESSION_ID" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"ask_blockchain","arguments":{"question":"Recent whale activity on ETH","chain":"ETH"}}}'

3. All 68 MCP tools (canonical)

Matches the live tools/list response. Schema for each tool (params, defaults, min/max bounds) is returned by tools/list.

• RAG / NL (2) — ask_blockchain, search_rag
• Block / tx data (3) — query_blocks, query_transactions, inspect_block
• RPC (live archive node) (7) — rpc_get_balance, rpc_get_block, rpc_get_transaction, rpc_get_logs, rpc_trace_transaction, rpc_read_contract, rpc_get_contract_info
• Whales / entity (5) — get_whale_activity, get_btc_flows, get_smart_wallets, get_entity_activity, get_wallet_profile
• Market (5) — get_emerging_tokens, get_trending_tokens, get_token_flows, get_exchange_flows, get_price_history
• Signals (9) — get_trade_signals, get_intelligence_feed, get_alarm_feed, get_alerts, get_alarm_categories, get_conviction_signals, get_predictions, get_signal_accuracy, get_signal_history
• Behavioral / cross-chain (3) — get_cross_chain_signals, get_intent_detections, get_mev_leaderboard
• Hyperliquid perps (5) — get_hl_market, get_hl_traders, get_hl_funding_arbs, get_hl_liquidation_heatmap, get_hl_copy_trade_alerts
• Forensic (8) — screen_address, assess_risk, detect_mixer_interactions, check_abuse_status, trace_flows, generate_compliance_report, export_compliance_pdf, get_risk_briefing
• Compliance monitoring (3) — monitor_address, list_retroactive_alerts, dismiss_retroactive_alert
• KYA agent identity (4) — register_agent_identity, validate_agent_action, revoke_agent_identity, list_my_agent_identities
• Pipeline / system (7) — get_network_summary, get_system_status, get_chain_status, get_pipeline_status, get_health, get_logs, get_stats

Total: 2+3+7+5+5+9+3+5+8+3+4+7 = 61. Standard query contract on most list endpoints: chain, limit, min_usd, since, until (ISO 8601), cursor (opaque keyset paginator where supported). Responses include next_cursor + has_more for keyset-paginated endpoints.

3a. Chain coverage

3b. One-shot smoke test

If all five steps return successful JSON matching the expected shapes, your MCP integration is healthy end-to-end.

KEY=$(curl -s -X POST https://api.bitpoort.com/v1/keys | python3 -c "import sys,json;print(json.load(sys.stdin)['api_key'])")
# Expected: KEY starts with "bp_". POST /v1/keys returns api_key, tier="agent",
# rate_limit=20, daily_cap=1500, scopes[], expires_at, usage{...}.

# 1. Auth identity (REST)
curl -H "X-API-Key: $KEY" https://api.bitpoort.com/v1/auth/me
# Expected: {api_key_id:<int>, name:"instant-agent", role:"agent",
#   rate_limit:20, scopes:[...], sso:null}

# 2. Sample REST query
curl -H "X-API-Key: $KEY" "https://api.bitpoort.com/v1/whales/recent?chain=ETH&limit=3"
# Expected: {count:<=3, chain:"ETH", min_usd:100000.0, next_cursor, has_more,
#   whales:[{tx_hash,block_number,from/to_address,value_usd,timestamp,...}]}

# 3. MCP initialize -- capture session id
SESSION=$(curl -sD - -X POST https://mcp.bitpoort.com/ \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"smoke","version":"1"}}}' \
  | awk -F': ' 'tolower($1)=="mcp-session-id"{gsub(/\r/,"",$2);print $2}')
# Expected: SESSION is a UUID. result.serverInfo = {name:"bitpoort", version:"3.5.0"}.
# result.instructions opens with "Bitpoort provides real-time blockchain
# intelligence live across Ethereum, Bitcoin, and Hyperliquid..."

# 4. MCP tools/list (68 tools)
curl -X POST https://mcp.bitpoort.com/ -H "X-API-Key: $KEY" -H "Mcp-Session-Id: $SESSION" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'
# Expected: result.tools length == 68.

# 5. MCP tool call
curl -X POST https://mcp.bitpoort.com/ -H "X-API-Key: $KEY" -H "Mcp-Session-Id: $SESSION" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_network_summary","arguments":{"chain":"ETH"}}}'
# Expected: result.content[0].text is a JSON string. Parsed:
# {chain:"ETH", health_score, latest_block, hourly{...}, whales_1h{...}}.

4. Discover programmatically

• /.well-known/mcp.json — MCP discovery manifest
• api.bitpoort.com/v1/trust — Live trust + accuracy baseline (public)
• api.bitpoort.com/openapi.json — OpenAPI 3.1 spec
• api.bitpoort.com/redoc — ReDoc UI
• api.bitpoort.com/health — JSON health (public)