Skip to main content
Glama
BlockRunAI

BlockRun MCP

Official
by BlockRunAI

blockrun_surf

Read-only

Access unified crypto data including market prices, on-chain SQL, wallet details, prediction markets, and social sentiment through a single API endpoint.

Instructions

Unified crypto data via Surf (asksurf.ai) — 83 endpoints, one API.

Coverage: CEX market data (16 exchanges), on-chain SQL across 13 chains, 100M+ labeled wallets, prediction markets (Polymarket + Kalshi), social mindshare / CT intelligence, news, and unified search.

Pricing (settled in USDC to Surf's Base treasury):

  • Flat $0.0095/call — every endpoint, including raw on-chain SQL. No tiers. ($0.0075 base + $0.002 tx fee.)

Common paths (full 83-endpoint catalog in the surf skill):

  • market/price?symbol=BTC

  • exchange/price?pair=BTC-USDT

  • prediction-market/polymarket/ranking

  • search/web?q=ethereum+pectra+upgrade

  • wallet/detail?address=0x...

  • social/mindshare?q=ethereum&interval=1d

  • onchain/sql + body:{ sql: "SELECT ..." }

Method is auto-routed: pass 'body' for POST endpoints; otherwise GET with 'params'. Each Surf endpoint pre-validates required params before settling — you get a 400 (not a charge) if a required field is missing. Browse the full catalog: https://blockrun.ai/marketplace/surf

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoJSON body for POST endpoints. Provide for: onchain/query, onchain/sql. When set, the call is sent as POST; otherwise GET with params.
pathYesEndpoint path under /v1/surf/, e.g. 'market/price', 'prediction-market/polymarket/ranking', 'wallet/detail', 'onchain/sql'
paramsNoQuery parameters for GET endpoints, e.g. { symbol: 'BTC' } or { address: '0x...', chain: 'ethereum' }
agent_idNoAgent identifier for budget tracking and enforcement.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses read-only nature (consistent with annotations), pricing, pre-validation, and no charge on 400 errors. Adds significant context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with front-loaded purpose, but includes pricing and catalog link that could be considered extraneous. Still efficient for the information density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all key aspects: scope, examples, behavior, parameter usage, and error handling. No output schema, but sufficient for a data-fetching tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description greatly expands meaning with examples, routing rules, pre-validation behavior. Makes parameters actionable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states this is a unified API for 83 Surf endpoints, listing specific coverage areas and common paths. It distinguishes from siblings by being the meta-tool for crypto data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides guidance on when to use (for various crypto data types) and method auto-routing. Does not explicitly compare to siblings but is clear enough for a broad tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BlockRunAI/blockrun-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server