npm @cryptoapis-io/mcp-market-datastdioupdated 1mo ago
MCP server for Crypto APIs Market Data product. List supported assets, get exchange rates, and get asset details.
What can you do with mcp market data?
@cryptoapis-io/mcp-market-data
MCP server for Crypto APIs Market Data product. List supported assets, get exchange rates, and get asset details.
API Version: Compatible with Crypto APIs version 2024-12-12
Features
- List supported crypto and fiat assets with filtering and pagination
- Get exchange rates between any two assets (by symbol or asset ID)
- Get asset details by asset ID or symbol
Prerequisites
- Node.js 18+
- Crypto APIs account and API key (sign up | get API key)
Installation
npm install @cryptoapis-io/mcp-market-data
Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
Usage
# Run with API key
npx @cryptoapis-io/mcp-market-data --api-key YOUR_API_KEY
# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-market-data
# HTTP transport
npx @cryptoapis-io/mcp-market-data --transport http --port 3000 --api-key YOUR_API_KEY
Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"cryptoapis-market-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-market-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-market-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-market-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
MCP Inspector
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-market-data --api-key YOUR_API_KEY
n8n
- Start the server in HTTP mode:
npx @cryptoapis-io/mcp-market-data --transport http --port 3000 --api-key YOUR_API_KEY - In your n8n workflow, add an AI Agent node
- Under Tools, add an MCP Client Tool and set the URL to
http://localhost:3000/mcp
All servers default to port 3000. Use
--portto assign different ports when running multiple servers.
Available Tools
market_data_metadata
| Action | Description |
|---|---|
list-supported-assets |
List supported crypto and fiat assets. Optional: limit, offset, type (crypto/fiat) |
market_data_exchange_rates
| Action | Description |
|---|---|
get-exchange-rate-by-asset-symbols |
Get exchange rate between two assets by symbol (e.g. BTC to USD) |
get-exchange-rate-by-asset-ids |
Get exchange rate between two assets by asset ID |
market_data_assets
| Action | Description |
|---|---|
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) |
CLI Arguments
| Argument | Description | Default |
|---|---|---|
--api-key |
Crypto APIs API key | CRYPTOAPIS_API_KEY env var |
--transport |
Transport type: stdio or http |
stdio |
--host |
HTTP host | 0.0.0.0 |
--port |
HTTP port | 3000 |
--path |
HTTP path | /mcp |
--stateless |
Enable stateless HTTP mode | false |
HTTP API Key Modes
When using HTTP transport, the server supports two API key modes:
- With
--api-key: The key is used for all requests.x-api-keyrequest headers are ignored. - Without
--api-key: Each request must include anx-api-keyheader with a valid Crypto APIs key. This enables hosting a public server where each user provides their own key.
# Per-request key mode (multi-tenant)
npx @cryptoapis-io/mcp-market-data --transport http --port 3000
# Clients send x-api-key header with each request
Stdio transport always requires an API key at startup.
Important: API Key Required
Warning: Making requests without a valid API key — or with an incorrect one — may result in your IP being banned from the Crypto APIs ecosystem. Always ensure a valid API key is configured before starting any server.
Remote MCP Server
Crypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at https://ai.cryptoapis.io/mcp. Pass your API key via the x-api-key header — no installation required.
License
MIT
Install
Add mcp market data to your client. Pick the one you use.
claude mcp add mcp-market-data -- npx -y @cryptoapis-io/mcp-market-datacodex mcp add mcp-market-data -- npx -y @cryptoapis-io/mcp-market-dataamp mcp add mcp-market-data -- npx -y @cryptoapis-io/mcp-market-data{
"mcpServers": {
"mcp-market-data": {
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-market-data"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"mcp-market-data": {
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-market-data"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"mcp-market-data","command":"npx","args":["-y","@cryptoapis-io/mcp-market-data"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"mcp-market-data": {
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-market-data"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"mcp-market-data": {
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-market-data"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"mcp-market-data": {
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-market-data"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"mcp-market-data": {
"type": "local",
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-market-data"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"mcp-market-data": {
"command": {
"path": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-market-data"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y @cryptoapis-io/mcp-market-dataRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance22/25
- Trust9/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 33 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.3.0Latest | Mar 13, 2026 |
| 0.2.5 | Mar 6, 2026 |
| 0.2.3 | Mar 5, 2026 |