Bitquery MCP server is a hosted Model Context Protocol endpoint that connects your AI client to Bitquery's production trading dataset — the same data behind Bitquery's GraphQL APIs, IDE, Kafka streams, and TradingView feeds. You ask in plain English. The agent does the lookup. You get clean, structured rows back. No SQL, no schema, no rate-limit juggling. Concretely, your agent gets: - Billions of swap-level trade rows across Solana, Ethereum, BSC, Base, Arbitrum, Optimism, Polygon, and Tron. - Pre-built OHLC candles at 1-minute, 5-minute, hourly, and daily intervals. - Per-token economics — market cap, fully diluted valuation, circulating supply — on every row. - Bitquery's outlier filter baked in — wash-traded pools and noisy pairs are deprioritised automatically. - Zero infrastructure to maintain — no ETL, no schema sync, no API client to write.
bitquery-mcp is a remote MCP server published at mcp.bitquery.io. It has been probed 40 times since 9/10/2026. It answered in 40 of them (100.0%), a near-uninterrupted record. Median response time is 257 ms, placing it among the faster endpoints. Its tool list could not be read; the server is closed to direct calls. It answers direct calls with an authentication wall.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-14 04:24:59 | Auth-gated | 401 | 496 | 401 | 494 | — |
| 2026-09-14 02:22:47 | Auth-gated | 401 | 78 | 401 | 77 | — |
| 2026-09-14 00:19:26 | Auth-gated | 401 | 317 | 401 | 315 | — |
| 2026-09-13 22:17:36 | Auth-gated | 401 | 216 | 401 | 215 | — |
| 2026-09-13 21:01:02 | Auth-gated | 401 | 348 | 401 | 345 | — |
| 2026-09-13 18:57:30 | Auth-gated | 401 | 334 | 401 | 323 | — |
| 2026-09-13 16:52:42 | Auth-gated | 401 | 464 | 401 | 461 | — |
| 2026-09-13 14:49:35 | Auth-gated | 401 | 392 | 401 | 391 | — |
| 2026-09-13 12:47:19 | Auth-gated | 401 | 167 | 401 | 169 | — |
| 2026-09-13 10:45:14 | Auth-gated | 401 | 203 | 401 | 201 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/bitquery-bitquery-mcp)<a href="https://mcpmetrics.io/servers/bitquery-bitquery-mcp"><img src="https://mcpmetrics.io/badge/bitquery/bitquery-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
AI music production assistant — audio profiling, AI mixing sessions, and service inquiries.
A production-grade Model Context Protocol server for PostgreSQL. Lets AI agents safely inspect, query, operate, and tune a Postgres database — over 240 tools spanning catalog introspection, query intelligence, natural-language SQL, structural diffs, hybrid search, graph queries, data movement, live ops, and more.
Don't just collect requests—ship them. Loops integrates with AI Agents like Claude, Codex, and Cursor to write the code for top-voted features and notifies users the moment it’s live.
Structured Output MCP Agent (Instructor)
Structured Output MCP Agent (Langchain Core)
Structured Output MCP Agent (Cryptography)
Comments
Sign in to write a comment
No comments yet. Be the first.