Crypto Market MCP: live prices, coin discovery, trends, and market charts

Crypto Market MCP gives AI agents a structured interface to CoinGecko public market data. Look up current prices and market metrics, resolve a name or ticker to a CoinGecko ID, inspect trending assets, or retrieve timestamped market-chart series for analysis and visualization.

Use cases

• Enrich an assistant with current price, market-cap, 24-hour volume, and change data.
• Resolve ambiguous symbols before making another CoinGecko request.
• Monitor the assets currently surfaced by CoinGecko’s trending feed.
• Pull price, market-cap, and volume series for a chart or quantitative workflow.

Market data can be delayed or incomplete. This product supplies data, not investment, tax, legal, custody, execution, or trading advice, and it never places orders.

MCP tools

Tool	Arguments	Result
get-crypto-price	coinIds — array of 1–20 non-empty CoinGecko IDs, default ['bitcoin']; vsCurrency — non-empty quote-currency string, default usd	JSON text with results. Each item has normalized coinId, normalized vsCurrency, price, marketCap, volume24h, and change24h. Missing upstream values are null.
search-crypto	query — required non-empty string; maxResults — integer 1–50, default 10	JSON text with the original query and results containing id, name, symbol, nullable marketCapRank, thumb, and large image URLs.
get-trending-crypto	limit — integer 1–50, default 10	JSON text with results containing CoinGecko trend fields: id, nullable numeric coinId, name, symbol, marketCapRank, slug, priceBtc, score, image URLs, and the upstream data object.
get-coin-market-chart	coinId — required non-empty CoinGecko ID; vsCurrency — default usd; days — integer 1–365, default 7	JSON text with normalized identifiers, days, and prices, marketCaps, and volumes. Every series contains [Unix timestamp in milliseconds, value] pairs from CoinGecko.

Use CoinGecko IDs such as bitcoin, not merely ticker symbols such as BTC. Call search-crypto first when the ID is uncertain.

Connect from an MCP client

The exact Apify Streamable HTTP endpoint is:

https://reverberant-equality--mcp-crypto-market.apify.actor/mcp

Authenticate each request through Apify:

Authorization: Bearer <APIFY_API_TOKEN>
Content-Type: application/json
Accept: application/json, text/event-stream

Use POST through an MCP Streamable HTTP client and complete the standard MCP initialization sequence. This is JSON-RPC over MCP, not a custom REST interface. GET /mcp and DELETE /mcp return method-not-allowed responses.

Example price call after initialization:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get-crypto-price",
    "arguments": {
      "coinIds": ["bitcoin", "ethereum"],
      "vsCurrency": "usd"
    }
  }
}

Successful data is serialized in result.content[0].text; parse that JSON text for programmatic use.

Pricing and data source

The live price is $0.005 per tool call. Every tool emits one tool-call pay-per-event charge before making its CoinGecko request. A rate-limit response, invalid upstream ID, or other failure after charging can still consume the paid call. Apify platform usage is billed separately according to the user’s Apify plan.

The upstream source is the CoinGecko API, using public endpoints under https://api.coingecko.com/api/v3: /simple/price, /search, /search/trending, and /coins/{id}/market_chart. No CoinGecko API key is configured by this server.

Limitations and error behavior

• Public CoinGecko endpoints have rate limits and availability constraints. The server uses a 15-second request timeout and does not cache or retry.
• A requested ID absent from a successful simple-price response is retained in the result with null metrics; that is not proof the asset has no market value.
• Supported quote currencies and historical granularity are determined by CoinGecko. The server does not validate a quote currency against a local list.
• maxResults and limit only cap the upstream arrays returned; they cannot produce more search or trending records than CoinGecko supplies.
• Historical data is returned as raw arrays. The server does not calculate returns, candles, indicators, correlations, or forecasts.
• On an Axios/CoinGecko failure, the MCP result sets isError: true and returns JSON text with error, optional HTTP status, and retryAfter. HTTP 429 responses also include a hint to wait or reduce call frequency.
• Prices can move between calls. Verify consequential decisions against an appropriate real-time venue.

Privacy

No request or result is persisted to an Actor dataset, key-value store, or application database. Coin IDs, queries, quote currencies, limits, and day ranges are processed in memory and forwarded as needed to CoinGecko, which receives ordinary network metadata under its own policies. Operational error logs can include upstream status and message details. Do not place secrets or personal data in search queries. Keep the Apify Bearer token in secure MCP client configuration.

Local development

Requires Node.js 20 or newer:

npm install
npm run start:dev       # local endpoint: http://localhost:3000/mcp
npm test                # run Vitest
npm run build           # compile TypeScript to dist/
npm run start:prod      # run compiled output
apify validate-schema   # validate Actor configuration/schema

Set APIFY_CONTAINER_PORT to override port 3000. Local runs outside a monetized Apify environment may log that charging is ignored; the production handler still emits the PPE event.