Birdeye MCP
Official hosted MCP for real-time and historical crypto market data across 8M+ tokens.
- Sato Score25
- ChainsMultichain
Birdeye MCP is a MCP server by Birdeye, 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 Birdeye MCP →No code activity tracked
Listed from birdeye.so on 2026-07-13. Install: not attempted. Evidence →
Next step
Watch Birdeye 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.birdeye.so/mcp 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
Birdeye MCP is the official Model Context Protocol server run by Birdeye, exposing real-time pricing, OHLCV history, token security metadata, holder distribution, and wallet PnL for 15k+ coins and 8M+ tokens. A builder plugs it into an agent for onchain market-data lookups and token discovery without building custom API integrations. Currently in beta; production use requires a paid API key, with a limited keyless tier for testing.
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 birdeye.so on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | docs.birdeye.so | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | birdeye.so | as of 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted by Sato Hub | self-reported | docs.birdeye.so | as of 2026-07-20 |
| MCP endpoint answers | answered, but declined an anonymous probe | observed | mcp.birdeye.so | 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 | npm/npx, Hosted API (keyless option)confidence 0.70 | self-reported | docs.birdeye.so | as of 2026-07-14 |
| Works with | Claude Desktop, Gemini CLI, Cursorconfidence 0.85 | self-reported | docs.birdeye.so | 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 — as documented by the project, not run by us
Runtime: Hosted MCP endpoint (mcp-remote bridge via npx; Node.js v18+)
npx -y mcp-remote@0.1.38 https://mcp.birdeye.so/mcp --header "x-api-key:<YOUR_API_KEY>"
{"mcpServers": {"birdeye-mcp": {"command": "npx", "args": ["-y", "mcp-remote@0.1.38", "https://mcp.birdeye.so/mcp", "--header", "x-api-key:${API_KEY}"], "env": {"API_KEY": "<YOUR_API_KEY>"}}}}You supply: Birdeye API key (x-api-key header; generated at bds.birdeye.so under Usages -> Security)
claude mcp add --transport http satohub-birdeye-mcp https://mcp.birdeye.so/mcp
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-07-20. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 0
- Failed
- 91
- Their error
- 22
- Unattributed
- 69
State changed on 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.
Skills that target this — 1, with disclosures
Disclosures describe what a skill declares and does; they are not safety verdicts. All skills →
Details
- Chains
- Multichain
- Agent types
- MCP Server, Data Provider
- Open source
- Unknown
- Pricing
- Demo/Pro API key tiers; limited keyless tier for testing
- Deploys as
- npm/npx, Hosted API (keyless option)
- Works with
- Claude Desktop, Gemini CLI, Cursor
- 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 Birdeye MCP fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?, What Are MCPs? The Standard Way to Give Agents Tools
Listing History
Recorded changes to Birdeye 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: deployment options
- Jul 14, 2026Auto-enriched: supported integrations
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Birdeye MCP
- Is Birdeye MCP open source?
- Unknown. Sato Hub has not found a public repository or a license statement for Birdeye MCP as of 2026-10-15.
- Which chains does Birdeye MCP support?
- Birdeye MCP lists support for Multichain as of 2026-10-15.
- Is Birdeye MCP still maintained?
- Sato Hub tracks no commit or release for Birdeye MCP; it cannot say whether it is maintained.
- How do I install or run Birdeye MCP?
- Hosted MCP endpoint (mcp-remote bridge via npx; Node.js v18+). Install: npx -y mcp-remote@0.1.38 https://mcp.birdeye.so/mcp --header "x-api-key:<YOUR_API_KEY>". Entry: {"mcpServers": {"birdeye-mcp": {"command": "npx", "args": ["-y", "mcp-remote@0.1.38", "https://mcp.birdeye.so/mcp", "--header", "x-api-key:${API_KEY}"], "env": {"API_KEY": "<YOUR_API_KEY>"}}}}. 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.birdeye.so/mcp (remote, via mcp-remote)).
- Is Birdeye MCP verified on Sato Hub?
- No independent verification is on record for Birdeye 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. "Birdeye MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/birdeye-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.