# MCP Crypto Data API Source Fit | PubFi Discovery

> Evaluate crypto data sources that expose or document MCP-style access while keeping PubFi's current non-claim boundary clear.

Source: Discovery demand-led page records consumed by the public Discovery routes.
Format: text/markdown; charset=utf-8
Inclusion rule: public demand-led records must be indexable; draft/noindex records are not emitted as markdown pages.
Canonical SEO rule: the HTML page is the canonical SEO URL; this Markdown route is an agent-readable mirror.
Capability boundary: page existence does not imply PubFi publishes an MCP server, x402 payment route, autonomous supplier call, or supplier-payment execution flow.


URL: https://pubfi.ai/discovery/topic/mcp-crypto-data-api
Markdown URL: https://pubfi.ai/discovery/topic/mcp-crypto-data-api.md
Title: MCP Crypto Data API Source Fit
Summary: Evaluate crypto data sources that expose or document MCP-style access while keeping PubFi's current non-claim boundary clear.
Primary query: MCP crypto data API
Supporting queries: crypto data MCP server
Demand area: MCP/agent-native crypto data APIs
Use case: Agent tooling research
Best starting page: https://pubfi.ai/discovery/topic/mcp-crypto-data-api
Availability status: roadmap signal (Roadmap signal)
Status-aware CTA: Signal MCP tooling demand
Actionability: not actionable
Status explanation: Discovery compares public MCP source evidence such as endpoint shape, authentication requirements, tool boundaries, source provenance, and freshness. PubFi does not publish a public MCP manifest, MCP server, or payable MCP tool today.
Machine interest signal: mcp tooling
Detail export status: public/featured-export
Related source pages:
- CoinGecko API: https://pubfi.ai/discovery/api/coingecko-api
- CoinMarketCap API: https://pubfi.ai/discovery/api/coinmarketcap-api
- Bitquery: https://pubfi.ai/discovery/api/bitquery
- The Graph: https://pubfi.ai/discovery/api/the-graph
Related category pages:
- Market data: https://pubfi.ai/discovery/category/market-data
- On-chain state: https://pubfi.ai/discovery/category/on-chain-state
Related chain pages: none
Source evidence:
- Model Context Protocol architecture: https://modelcontextprotocol.io/docs/learn/architecture
- CoinGecko MCP Server: https://mcp.api.coingecko.com/
- CoinMarketCap MCP API surface: https://coinmarketcap.com/api/mcp/
- Bitquery MCP server docs: https://docs.bitquery.io/docs/mcp/mcp-server/
Comparison criteria:
- Hosted endpoint or local server: Separate hosted MCP endpoints such as CoinGecko or CoinMarketCap from local or self-hosted server documentation such as Bitquery before treating a source as agent-ready.
- Authentication and key requirements: Record whether the public evidence requires an API key, bearer token, OAuth flow, local configuration, or no credential before an agent can list or call tools.
- Read-only versus write boundary: Prefer sources whose public tool descriptions make market data, on-chain reads, query execution, or any write-capable actions clear instead of assuming every MCP tool is read-only.
- Tool count and endpoint coverage: Compare the visible tool list, supported data families, and route coverage against the related Discovery provider pages for market data and on-chain state.
- Source provenance and freshness: Use official provider or protocol pages as evidence anchors and keep freshness claims tied to the source page record rather than to PubFi MCP availability.
- PubFi capability boundary: Treat this page as source-selection and demand-capture guidance; PubFi does not publish a public MCP discovery manifest, server, or payable MCP tool today.