MCP Crypto Data API Source Fit

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

Roadmap signal4 source signals2 categories

Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows

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
Query group: MCP/agent-native crypto data APIs
Best starting page: This page
Availability status: Roadmap signal
Demand signal: mcp tooling
Markdown mirror: /discovery/topic/mcp-crypto-data-api.md

Source Evidence

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.

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.

Related Discovery Records

Sources

CoinGecko API: /discovery/api/coingecko-api
CoinMarketCap API: /discovery/api/coinmarketcap-api
Bitquery: /discovery/api/bitquery
The Graph: /discovery/api/the-graph

Demand Signal

PubFi can record interest in this source-selection workflow without storing payment proofs, wallet data, raw search queries, or procurement notes.

Signal MCP tooling demand