On this page

Model Context Protocol (MCP) Servers

Understanding MCP​

Model Context Protocol (MCP) is a thin specification that layers self-describing JSON-Schema "functions" over existing HTTP APIs. Every endpoint—its path, parameters, authentication rules, and error codes—is published as a machine-readable contract so that autonomous agents (LLMs, bots, test harnesses) can discover, validate, and invoke real requests without any custom glue code.

When and Where to Attach MCP​

You can think of the public MCP relays listed below as "drop-in adapters" that sit between your application and the native API:

• Client-side consolidation – Point your mobile app, backend service, or data-science notebook at a single MCP host instead of juggling many base URLs.
• Server-side gateway – Place MCP in front of private micro-services to expose them securely over JSON-RPC without rewriting any code.
• Automation & CI/CD – Use MCP with generic JSON-RPC tooling (e.g. curl, Postman, or WebSocket clients) to script repetitive operational tasks across different APIs.

What You Can Achieve with MCP​

Capability	How it Helps
Self-describing functions	Each endpoint is exposed as a JSON-Schema contract that an agent can introspect to build valid requests.
Dedicated service endpoints	Connect directly to the MCP server for the product you use without adding a custom adapter layer.
Schema-level validation	The relay checks your payload against the schema before forwarding it, catching mistakes early.
Consistent auth	Reuse your existing X-CoinAPI-Key header with no separate MCP credential flow.
Zero-day coverage	New upstream routes appear automatically in the MCP manifest—no SDK updates needed.
Unified observability	Logs, metrics, and rate limits can be enforced once at the MCP layer instead of per-service.

In short: MCP gives you a self-describing RPC surface for each supported API, reducing integration boilerplate and speeding up automation.

The table below lists all currently supported public CoinAPI MCP servers.

Only /mcp endpoints are supported. Aggregated MCP endpoints and SSE endpoints are no longer available.

Supported Server Endpoints​

Product	MCP Endpoint
CoinAPI Market Data API	https://mcp.md.coinapi.io/mcp
CoinAPI Exchange Rates Historical API	https://api-historical.exrates.coinapi.io/mcp
CoinAPI Exchange Rates Realtime API	https://api-realtime.exrates.coinapi.io/mcp
CoinAPI Indexes API	https://mcp.indexes.coinapi.io/mcp
CoinAPI Flat Files API	https://mcp.flatfiles.coinapi.io/mcp

---

Example client configuration​

Below is a minimal JSON example showing how an application might be configured to talk to these servers. Replace <YOUR_API_KEY> with the key issued for your account and keep only the services your application needs.

{
  "CoinAPI-Market-Data": {
    "url": "https://mcp.md.coinapi.io/mcp",
    "headers": {
      "X-CoinAPI-Key": "<YOUR_API_KEY>"
    }
  },
  "CoinAPI-Exrates-Historical": {
    "url": "https://api-historical.exrates.coinapi.io/mcp",
    "headers": {
      "X-CoinAPI-Key": "<YOUR_API_KEY>"
    }
  },
  "CoinAPI-Exrates-Realtime": {
    "url": "https://api-realtime.exrates.coinapi.io/mcp",
    "headers": {
      "X-CoinAPI-Key": "<YOUR_API_KEY>"
    }
  },
  "CoinAPI-Indexes": {
    "url": "https://mcp.indexes.coinapi.io/mcp",
    "headers": {
      "X-CoinAPI-Key": "<YOUR_API_KEY>"
    }
  },
  "CoinAPI-Flat-Files": {
    "url": "https://mcp.flatfiles.coinapi.io/mcp",
    "headers": {
      "X-CoinAPI-Key": "<YOUR_API_KEY>"
    }
  }
}

Feel free to adapt the format to your application's configuration system.

Was this section helpful?

• 1
• 2
• 3
• 4
• 5