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. |
| Multi-service router | Reach FinFeedAPI, CoinAPI, and future services through a single /mcp endpoint by changing the server parameter. |
| Schema-level validation | The relay checks your payload against the schema before forwarding it, catching mistakes early. |
| Consistent auth | Reuse your existing X-APIKey or bearer Authorization header—no new tokens required. |
| 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 lets you treat a heterogeneous fleet of APIs as a single, extensible RPC surface—simplifying integration, reducing boilerplate, and speeding up development cycles.
The table below lists publicly accessible MCP servers that relay FinFeedAPI and CoinAPI services. Each service can be called directly, or you may use the Composite MCP endpoint that aggregates them behind a single host.
Two endpoint variants are available for every service:
/mcp– implements HTTP streaming (bidirectional over a single request)./sse– implements Server-Sent Events (SSE) for one-way, event-driven updates.
Individual Server Endpoints
Composite Server Endpoint
| Endpoint | Aggregated Servers |
|---|---|
| https://mcp.api.apibricks.io/mcp (HTTP Streaming) | |
| https://mcp.api.apibricks.io/sse (SSE) | All of the individual servers listed above |
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.
{
"FinFeedAPI-SEC": {
"url": "https://mcp.sec.finfeedapi.com/mcp",
"headers": {
"X-APIKey": "<YOUR_API_KEY>"
}
},
"FinFeedAPI-Stock": {
"url": "https://mcp-historical.stock.finfeedapi.com/mcp",
"headers": {
"X-APIKey": "<YOUR_API_KEY>"
}
},
"FinFeedAPI-FX-Realtime": {
"url": "https://mcp-realtime.fx.finfeedapi.com/mcp",
"headers": {
"X-APIKey": "<YOUR_API_KEY>"
}
},
"FinFeedAPI-FX-Historical": {
"url": "https://mcp-historical.fx.finfeedapi.com/mcp",
"headers": {
"X-APIKey": "<YOUR_API_KEY>"
}
},
"CoinAPI-Market-Data": {
"url": "https://mcp.md.coinapi.io/mcp",
"headers": {
"X-CoinAPI-Key": "<YOUR_API_KEY>"
}
}
}
Or for the composite MCP:
{
"APIBRICKS_COMPOSITE": {
"url": "https://mcp.apibricks.io/mcp",
"headers": {
"X-APIKey": "<YOUR_API_KEY>"
}
}
}
Feel free to adapt the format to your application's configuration system.