
Mcp Market Data
Feed live crypto prices, exchange rates, and asset metadata into apps and agent sessions through Crypto APIs market data MCP.
Overview
io.github.CryptoAPIs-io/mcp-market-data is a Build-phase MCP server that provides cryptocurrency prices, exchange rates, and market metadata through Crypto APIs.
What is this MCP server?
- Cryptocurrency asset prices, exchange rates, and market metadata via Crypto APIs
- @cryptoapis-io/mcp-market-data stdio MCP at version 0.3.0
- Requires CRYPTOAPIS_API_KEY for all tool calls
- Useful for quoting, portfolio display, and validation of pricing code in-agent
- Market data MCP—not a charting UI or exchange trading terminal
- Server version 0.3.0
- stdio npm package @cryptoapis-io/mcp-market-data
- 1 required environment variable: CRYPTOAPIS_API_KEY
What problem does it solve?
Adding accurate crypto quotes to a product usually means custom API clients and copy-paste rate checks instead of agent-native market data tools.
Who is it for?
Indie builders embedding rates and asset metadata into SaaS, agents, or internal tools who want the smallest Crypto APIs MCP setup.
Skip if: Teams needing deep order-book trading, proprietary alpha feeds, or market data with no Crypto APIs account.
What do I get? / Deliverables
Your agent can pull live prices and metadata from Crypto APIs while you build pricing, portfolio, or conversion features in one workflow.
- Live price and rate queries callable from the agent
- Metadata lookups to enrich asset labels and conversions in your app
- Registered stdio MCP alongside other Crypto APIs servers
Recommended MCP Servers
Journey fit
Market data hooks are integrated while you build dashboards, pricing logic, or trading UX; research use is secondary to shipping the feature. Canonical shelf is integrations because the server is an API bridge agents call from code you are actively writing.
How it compares
Quote and metadata MCP integration, not a backtesting or technical-analysis skill pack.
Common Questions / FAQ
Who is mcp-market-data for?
Solo builders and developers shipping crypto-aware UIs, APIs, or agent tools that need standardized price and metadata access from Crypto APIs.
When should I use mcp-market-data?
Use it while building features that display prices, convert assets, or validate business logic against current market metadata.
How do I add mcp-market-data to my agent?
Configure @cryptoapis-io/mcp-market-data as a stdio MCP server, provide CRYPTOAPIS_API_KEY, and add the server block from the CryptoAPIs-io repo to your agent.