Crypto APIs Market Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRYPTOAPIS_API_KEY | Yes | Crypto APIs API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| market_data_metadataB | Market Data metadata (list supported assets). Actions: • list-supported-assets: List supported crypto and fiat assets (optional pagination and type filter) Credits by action (source: OpenAPI): • list-supported-assets: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| market_data_exchange_ratesA | Market Data exchange rates. Actions: • get-exchange-rate-by-asset-symbols: Get exchange rate between two assets by symbol (e.g. BTC, USD) • get-exchange-rate-by-asset-ids: Get exchange rate between two assets by asset ID Credits by action (source: OpenAPI): • get-exchange-rate-by-asset-ids: 10 • get-exchange-rate-by-asset-symbols: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| market_data_assetsB | Market Data assets (asset details). Actions: • get-asset-details-by-asset-id: Get asset details by unique asset ID • get-asset-details-by-asset-symbol: Get asset details by symbol (e.g. BTC, ETH) Credits by action (source: OpenAPI): • get-asset-details-by-asset-id: 10 • get-asset-details-by-asset-symbol: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| system_infoA | CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| check-asset-price | Look up the current price and exchange rate for a crypto asset |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| supported-capabilities | Available market data tools, actions, and query parameters |
TDQS
Scored across 4 tools
The four tools have distinct purposes: metadata, exchange rates, asset details, and reference docs. Within exchange rates and assets, there are closely related actions (by symbol vs. by ID) that could cause selection confusion, but the tool-level separation is clear.
Tool names follow a consistent snake_case pattern with the 'market_data_' prefix for data tools, and 'system_info' is a minor deviation. Actions use a consistent kebab-case verb-noun structure (e.g., 'get-exchange-rate-by-asset-symbols'), so overall naming is predictable with only a slight inconsistency.
With 4 tools, the server is on the lean side but not unreasonable for a market data scope. Each tool covers a different aspect (metadata, rates, assets, reference), and the count is within the acceptable range, though it feels minimal rather than comprehensive.
The tool surface is missing common market data operations such as historical price data, market charts, OHLCV, or market cap. It only provides current exchange rates and asset details, which is a significant gap for a market data API and will likely cause agent failures when historical or broader market metrics are needed.