// SCAN REPORT

Bitpoort

41 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 20 May 2026

0 can modify or destroy data

41 read-only

41 tools total

// TOOL MAP

Read (41) Write / Execute (0) Destructive / Financial (0)

// WHAT CAN GO WRONG

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

// RECOMMENDED RULES

Cap read operations

ask_blockchain:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 41 BITPOORT TOOLS

READ 41 tools

Read ask_blockchain Read get_alarm_categories Read get_alarm_feed Read get_alerts Read get_btc_flows Read get_chain_status Read get_conviction_signals Read get_cross_chain_signals Read get_emerging_tokens Read get_entity_activity Read get_exchange_flows Read get_health Read get_hl_market Read get_hl_traders Read get_intelligence_feed Read get_intent_detections Read get_logs Read get_mev_leaderboard Read get_network_summary Read get_pipeline_status Read get_predictions Read get_price_history Read get_risk_briefing Read get_smart_wallets Read get_stats Read get_token_flows Read get_trade_signals Read get_trending_tokens Read get_wallet_profile Read get_whale_activity Read inspect_block Read query_blocks Read query_transactions Read rpc_get_balance Read rpc_get_block Read rpc_get_contract_info Read rpc_get_logs Read rpc_get_transaction Read rpc_read_contract Read rpc_trace_transaction Read search_rag

// FAQ

Is the Bitpoort MCP server safe to use without restrictions? +

The Bitpoort server is primarily read-only with 41 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Bitpoort MCP server expose? +

41 tools across 1 categories: Read. 41 are read-only. 0 can modify, create, or delete data.

How do I add Intercept to my Bitpoort setup? +

One line change. Instead of running the Bitpoort server directly, prefix it with Intercept: intercept -c bitpoort-on-chain-data.yaml -- npx -y @bitpoort/on-chain-data. Download a pre-built policy from policylayer.com/policies/bitpoort-on-chain-data and adjust the limits to match your use case.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.