Track MCP LogoTrack MCP
Track MCP LogoTrack MCP

The world's largest repository of Model Context Protocol servers. Discover, explore, and submit MCP tools.

Product

  • Categories
  • Top MCP
  • New & Updated
  • Submit MCP

Company

  • About

Legal

  • Privacy Policy
  • Terms of Service
  • Cookie Policy

© 2026 TrackMCP. All rights reserved.

Built with ❤️ by Krishna Goyal

    Coinstats Mcp

    9 stars
    TypeScript
    Updated Oct 1, 2025

    Table of Contents

    • Server URL
    • Installation
    • Claude.ai / Claude Desktop
    • Cursor
    • Claude Code
    • Codex
    • Other MCP clients
    • What you can do
    • Authentication
    • Self-host / stdio fallback (developer mode)
    • Architecture
    • Local development
    • Related
    • License

    Table of Contents

    • Server URL
    • Installation
    • Claude.ai / Claude Desktop
    • Cursor
    • Claude Code
    • Codex
    • Other MCP clients
    • What you can do
    • Authentication
    • Self-host / stdio fallback (developer mode)
    • Architecture
    • Local development
    • Related
    • License

    Documentation

    CoinStats MCP Server

    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

    code
    https://mcp.coinstats.app/mcp

    Installation

    Claude.ai / Claude Desktop

    Settings → Connectors → Add custom connector. Paste the server URL and click Add:

    code
    https://mcp.coinstats.app/mcp

    A browser window opens at coinstats.app/openapi/consent. Sign in (or recognise your existing session), review the requested access, click Approve.

    Cursor

    Install MCP Server

    Or add to ~/.cursor/mcp.json manually:

    json
    {
      "mcpServers": {
        "coinstats": {
          "url": "https://mcp.coinstats.app/mcp"
        }
      }
    }

    Restart Cursor; on first call it opens a browser window for the OAuth flow.

    Claude Code

    bash
    claude mcp add coinstats --transport http https://mcp.coinstats.app/mcp

    Claude Code opens a browser to authorise. Verify with:

    bash
    claude mcp list

    Codex

    codex mcp add only registers the URL; it does not open a browser. Run codex mcp login separately:

    bash
    codex mcp add coinstats --url https://mcp.coinstats.app/mcp
    codex mcp login coinstats

    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
    • 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:

    EndpointSpecPurpose
    GET /.well-known/oauth-protected-resourceRFC 9728Points at the authorization server (https://api.coin-stats.com)
    GET /.well-known/oauth-authorization-serverRFC 8414AS metadata (also mirrored on the MCP host so older clients can find it without the indirection)
    POST /v1/oauth/register (on AS)RFC 7591Dynamic Client Registration
    GET /v1/oauth/authorize → consent UIOAuth 2.1 §4.1User approves access
    POST /v1/oauth/token (on AS)OAuth 2.1 §4.1PKCE code exchange
    POST /v1/oauth/revoke (on AS)RFC 7009Per-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:

    bash
    npx @coinstats/coinstats-mcp

    with COINSTATS_API_KEY set in the env. Wire into a client like this:

    json
    {
      "mcpServers": {
        "coinstats": {
          "command": "npx",
          "args": ["-y", "@coinstats/coinstats-mcp"],
          "env": { "COINSTATS_API_KEY": "" }
        }
      }
    }

    Or via Docker:

    json
    {
      "mcpServers": {
        "coinstats": {
          "command": "docker",
          "args": ["run", "-i", "--rm", "-e", "COINSTATS_API_KEY", "coinstats/coinstats-mcp"],
          "env": { "COINSTATS_API_KEY": "" }
        }
      }
    }

    This path is the right choice for headless / unattended integrations where there's no human to click "Approve". Get a key from the CoinStats API Dashboard.

    Architecture

    The hosted server is a stateless Cloudflare Worker (~225 KiB / ~41 KiB gzipped) that:

    1. Exposes the RFC 9728 + RFC 8414 discovery endpoints.

    2. Gates POST /mcp on a Authorization: Bearer … token.

    3. Dispatches MCP JSON-RPC (initialize / tools/list / tools/call / ping) without session state.

    4. Forwards each tool call to https://openapiv1.coinstats.app carrying the same bearer.

    Source: [src/worker.ts](./src/worker.ts). Config: [wrangler.jsonc](./wrangler.jsonc).

    Local development

    The repo ships two entry points:

    • **src/worker.ts** — Cloudflare Worker. Run with wrangler dev (port 8787 by default).
    • **src/index.ts** — stdio server. Run with node dist/index.js after building, or via the published npm package.
    bash
    # Build the stdio CLI
    npm run build
    
    # Run the Worker locally (requires `wrangler login` first)
    npm run dev
    
    # Deploy the Worker — needs CLOUDFLARE_ACCOUNT_ID exported in the env
    # (the account ID isn't committed to wrangler.jsonc; pull it from the
    # Cloudflare dashboard sidebar or the CI deploy job's secrets).
    export CLOUDFLARE_ACCOUNT_ID=
    npm run deploy
    
    # Tail production logs
    npm run tail

    For local Worker development you can override env vars:

    bash
    wrangler dev --var OAUTH_ISSUER:http://localhost:1337 \
                 --var COINSTATS_API_BASE_URL:http://localhost:9999

    Related

    • CoinStats API docs — full REST surface, MCP setup guide, tool catalog
    • API dashboard — for stdio-mode users to manage their developer API key

    License

    MIT — see LICENSE.

    Similar MCP

    Based on tags & features

    • ME

      Metmuseum Mcp

      TypeScript·
      14
    • MC

      Mcp Server Aws Sso

      TypeScript·
      6
    • MC

      Mcp Ipfs

      TypeScript·
      11
    • LI

      Liveblocks Mcp Server

      TypeScript·
      11

    Trending MCP

    Most active this week

    • PL

      Playwright Mcp

      TypeScript·
      22.1k
    • SE

      Serena

      Python·
      14.5k
    • MC

      Mcp Playwright

      TypeScript·
      4.9k
    • MC

      Mcp Server Cloudflare

      TypeScript·
      3.0k
    View All MCP Servers

    Similar MCP

    Based on tags & features

    • ME

      Metmuseum Mcp

      TypeScript·
      14
    • MC

      Mcp Server Aws Sso

      TypeScript·
      6
    • MC

      Mcp Ipfs

      TypeScript·
      11
    • LI

      Liveblocks Mcp Server

      TypeScript·
      11

    Trending MCP

    Most active this week

    • PL

      Playwright Mcp

      TypeScript·
      22.1k
    • SE

      Serena

      Python·
      14.5k
    • MC

      Mcp Playwright

      TypeScript·
      4.9k
    • MC

      Mcp Server Cloudflare

      TypeScript·
      3.0k