Bitquery MCP
Hosted MCP endpoint for natural-language queries over Bitquery's trading, OHLC, and token-economics datasets.
- Sato Score25
- ChainsMultichain
Bitquery MCP is a closed-source MCP server by Bitquery, with no code activity tracked. Sato Score 25/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install Bitquery MCP →No code activity tracked
Listed from docs.bitquery.io on 2026-07-12. Install: not attempted. Evidence →
Next step
Watch Bitquery MCP
One email if what we observe changes — its endpoint stops answering, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on https://mcp.bitquery.io/ before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Bitquery hosts an MCP endpoint at mcp.bitquery.io that lets agents query per-trade blockchain data, prebuilt OHLC candles (1s to daily), and token economics (market cap, FDV, circulating supply) across eight chains — Solana, Ethereum, BSC, Base, Arbitrum, Optimism, Polygon, and Tron — without writing SQL or GraphQL. Results are outlier-filtered to deprioritize wash-traded pools. Access is OAuth 2.1 (browser sign-in) or a query-token method, read-only.
Sato Score
25/100· LowHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 8/35
- Code transparency
- 0/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 11/15
- Independent verification
- 0/10
Evidence — listed vs checked · what the words mean
Listed from docs.bitquery.io on 2026-07-12. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | docs.bitquery.io | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | docs.bitquery.io | as of 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_spec | self-reported | docs.bitquery.io | as of 2026-09-21 |
| MCP endpoint answers | answered, but declined an anonymous probe | observed | mcp.bitquery.io | 2026-10-15 |
| Daily check record | 0 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Deploys as | Hosted (remote MCP via mcp-remote/npx or direct URL, no self-hosting)confidence 0.80 | self-reported | docs.bitquery.io | as of 2026-07-14 |
| Works with | Cursor, Claude Code, VS Codeconfidence 0.75 | self-reported | docs.bitquery.io | as of 2026-07-14 |
| Sato Score | 25/100 (Low)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — not run by us — no falsifiable install+entry probe from deploy_spec
Runtime: Hosted MCP endpoint (no local install; optional mcp-remote bridge via npx)
claude mcp add bitquery -- npx -y mcp-remote https://mcp.bitquery.io/mcp
{"mcpServers": {"bitquery": {"command": "npx", "args": ["-y", "mcp-remote", "https://mcp.bitquery.io/mcp"]}}}You supply: Free Bitquery account; OAuth 2.1 browser sign-in (token cached ~30 days), or query-parameter token
claude mcp add --transport http satohub-bitquery-mcp https://mcp.bitquery.io/
A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-09-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 2
- Failed
- 89
- Their error
- 22
- Unattributed
- 67
State changed on 2026-07-19 (responding → unclear), 2026-09-01 (unclear → failing), 2026-09-23 (failing → unreachable from our probe).
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Multichain
- Agent types
- MCP Server, Data Provider
- Open source
- No
- Pricing
- Free tier with a Bitquery account; metered against existing plan beyond that
- Deploys as
- Hosted (remote MCP via mcp-remote/npx or direct URL, no self-hosting)
- Works with
- Cursor, Claude Code, VS Code
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Bitquery MCP fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are MCPs? The Standard Way to Give Agents Tools
Listing History
Recorded changes to Bitquery MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 20, 2026Edited: mcp endpoint url
- Jul 20, 2026Edited: deploy spec
- Jul 19, 2026Edited: mcp endpoint url
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Enriched: supported integrations
- Jul 14, 2026Auto-enriched: deployment options
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Phantom MCP
ActivePhantom's MCP server that lets AI agents view addresses, sign transactions, swap, and transfer tokens across Solana, Ethereum, Bitcoin, and Sui.
Bankless Onchain MCP
UnknownMCP server providing AI assistants read access to onchain data via the Bankless API.
Jupiter MCP Server
ActiveOpen-source MCP servers that let AI agents execute Solana token swaps via Jupiter's Ultra aggregation API.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Bitquery MCP
- Is Bitquery MCP open source?
- No. Bitquery MCP is closed source as of 2026-10-15.
- Which chains does Bitquery MCP support?
- Bitquery MCP lists support for Multichain as of 2026-10-15.
- Is Bitquery MCP still maintained?
- Sato Hub tracks no commit or release for Bitquery MCP; it cannot say whether it is maintained.
- How do I install or run Bitquery MCP?
- Hosted MCP endpoint (no local install; optional mcp-remote bridge via npx). Install: claude mcp add bitquery -- npx -y mcp-remote https://mcp.bitquery.io/mcp. Entry: {"mcpServers": {"bitquery": {"command": "npx", "args": ["-y", "mcp-remote", "https://mcp.bitquery.io/mcp"]}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.bitquery.io (remote MCP, OAuth)).
- Is Bitquery MCP verified on Sato Hub?
- No independent verification is on record for Bitquery MCP; its verification status is "Self-Reported" and its Sato Score is 25 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Bitquery MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/bitquery-mcpData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.