CoinStatsHQ/coinstats-mcp

Hosted Model Context Protocol server for the CoinStats API. Lets AI agents (Claude, Cursor, Codex, ChatGPT — anything that speaks MCP) read and act on the same crypto data the CoinStats apps use, over a single OAuth-protected HTTPS URL.
There's no API key to copy and no env var to manage: each user authorises the agent against their own CoinStats account in the browser, and the agent gets a per-user token from then on.
Server URL
Installation
Claude.ai / Claude Desktop
Settings → **Connectors** → **Add custom connector**. Paste the server URL and click **Add**:
A browser window opens at coinstats.app/openapi/consent. Sign in (or recognise your existing session), review the requested access, click **Approve**.
Cursor
Or add to ~/.cursor/mcp.json manually:
Restart Cursor; on first call it opens a browser window for the OAuth flow.
Claude Code
Claude Code opens a browser to authorise. Verify with:
Codex
codex mcp add only registers the URL; it does **not** open a browser. Run codex mcp login separately:
After the login step codex mcp list should show Auth: OAuth for coinstats.
Other MCP clients
Any client that speaks the Streamable HTTP transport with OAuth 2.1 authorization will work. Point it at https://mcp.coinstats.app/mcp — Dynamic Client Registration (RFC 7591) is supported, so no pre-shared client_id is needed.
What you can do
After authorising, your agent can:
- Look up real-time prices, charts and market data for 100,000+ coins
- Read your CoinStats portfolio coins, P/L and performance over time
- Query wallet balances and transactions across 120+ blockchains
- Retrieve cash-flow-adjusted historical P/L for wallets, exchanges, and portfolios over preset or custom calendar ranges
- Compare ticker pricing across 200+ exchanges
- Pull crypto news (latest, trending, filtered by source or topic)
Full tool catalog: https://coinstats.app/api-docs/mcp/tools.
Authentication
Discovery + OAuth flow follows the standard MCP / RFC pattern:
| Endpoint | Spec | Purpose |
|---|---|---|
| GET /.well-known/oauth-protected-resource | RFC 9728 | Points at the authorization server (https://api.coin-stats.com) |
| GET /.well-known/oauth-authorization-server | RFC 8414 | AS metadata (also mirrored on the MCP host so older clients can find it without the indirection) |
| POST /v1/oauth/register (on AS) | RFC 7591 | Dynamic Client Registration |
| GET /v1/oauth/authorize → consent UI | OAuth 2.1 §4.1 | User approves access |
| POST /v1/oauth/token (on AS) | OAuth 2.1 §4.1 | PKCE code exchange |
| POST /v1/oauth/revoke (on AS) | RFC 7009 | Per-client disconnect |
Token transport: Authorization: Bearer . Single coinstats scope today; granular scopes are on the roadmap.
Self-host / stdio fallback (developer mode)
If you want to run the MCP server yourself (no per-user OAuth, just a developer API key), the legacy stdio entry point is published on npm:
with COINSTATS_API_KEY set in the env. Wire into a client like this: