CoinMarketCal

com.coinmarketcalPublished by coinmarketcal.comOfficial publisherv1.0.1Updated Oct 24, 2026

Crypto events calendar: dated, sourced and impact-scored events for 14,000+ coins.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

CoinMarketCal's remote MCP server lets an assistant look up dated, sourced, impact-scored crypto events, coins and categories from its calendar.

What you can do
List and read calendar events, including upcoming and historical ones, filtered by coins, categories and date window, with tier-gated fields and cancellation status for removed events (410 Gone). Look up coins by rank or slug and browse the editorial category taxonomy with upcoming event counts. Check the authenticated key's monthly usage counters to back off before rate limits.
When to use it
Useful when an assistant needs to answer questions about upcoming or past crypto events for specific coins, or to build integrations that surface calendar data and event impact scores. It is read-only, so it suits research and monitoring rather than trading execution.
Requirements
A remote MCP endpoint at coinmarketcal.com over streamable HTTP. A CoinMarketCal API key is required, sent in the x-api-key header; a free tier is available. Results and available fields depend on the plan's tier and quota, which is shared with the REST API.
Before you install
The API key is a secret sent in the x-api-key header and shares quota with the REST API, so keep it private and watch usage. Some fields and tools (such as list_categories) are limited to higher tiers. Event dates marked as estimated are deadlines or window ends, not exact days. The server is read-only and does not modify data.

Installation

In SourceWeft

  1. Open CoinMarketCal in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.coinmarketcal%2Fevents/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "coinmarketcal": {
      "type": "http",
      "url": "https://coinmarketcal.com/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

CoinMarketCal API

Official examples for the CoinMarketCal API and MCP server.

CoinMarketCal is a crypto events calendar. Each event has a date, the coins it affects, an editorial category, an impact score and the source it comes from. The same data is available through a REST API and an MCP server for AI agents.

Quick start

Every request sends your key in the x-api-key header.

bash
curl -s "https://api.coinmarketcal.com/v2/events?coins=ethereum&limit=5" \  -H "x-api-key: $COINMARKETCAL_API_KEY"

Each event looks like this (fields depend on your plan):

json
{  "id": "48291",  "slug": "ethereum-pectra-upgrade",  "title": "Ethereum Pectra Upgrade",  "date": "2026-05-06T12:00:00Z",  "dateType": "date",  "isEstimated": false,  "displayedDate": "06 May 2026",  "categories": ["Release"],  "coins": [{ "slug": "ethereum", "symbol": "eth", "name": "Ethereum" }],  "impact": 8.5}

When isEstimated is true, date is a deadline or the end of a window, not an exact day. Show displayedDate to your users (for example Q2 2026 or By 30 May 2026).

Use it from an AI agent (MCP)

The MCP server exposes the read endpoints of the API as tools (list_events, get_event, list_coins, …). Event results include the url of the event page on coinmarketcal.com. It uses the same key and quota as the REST API.

ClientConfiguration
Claude Codemcp/claude-code.sh
Cursor, VS Code and clients using mcpServersmcp/mcp.json
Codex CLImcp/codex.toml
Claude Desktop and clients without remote HTTP supportmcp/mcp-remote.json

Replace YOUR_API_KEY with your key.

Examples

ExampleWhat it does
examples/curl.shList upcoming events, read one event, look up a coin
examples/python/upcoming_events.pyFetch every upcoming event for a coin, page by page
examples/javascript/upcoming-events.mjsSame with Node.js 18+ (fetch)
examples/webhooks/Verify the CMC-Signature header of a webhook delivery (Node.js, Python, PHP)

Data and license

The code in this repository is released under the MIT license. The CoinMarketCal data you access with it is governed by the API Terms of Service.

Support

Questions about the API: [email protected].

Source: README.md at commit 0074d74

Tools

7

list_events

List events

Returns a paginated list of upcoming and historical events within the date window available to the caller's plan. Default sort is `date asc` (soonest first). The `coins`, `categories`, and date filters compose with `AND`.

ParameterstofromcoinslimitcursorsortBykeywordimpactMincategories

list_event_cancellations

List permanently removed events

Returns removal records ordered by `cancelledAt`, then `id`. Available to every API V2 tier. Poll regularly and never leave more than 90 days between successful requests, even when webhooks are enabled.

Parameterslimitsincecursor

get_event

Fetch a single event

Returns the full event payload by id. Tier-gated fields follow the caller's plan. A recently removed event returns `410 Gone` with its `id` and `cancelledAt`. An unknown, temporarily unpublished, or out-of-window event returns `404`.

Parametersidrequired

list_categories

List categories

Returns every category in the editorial taxonomy with the count of upcoming events per category (tier-windowed). Standard+ only. Query parameters are ignored; the list is not paginated.

Takes no parameters.

list_coins

List coins

Returns a paginated list of coins ordered by `rank` ascending (top-ranked first). Pass the `tracked` filter only when you need to limit results by editorial coverage.

Parametersqlimitcursortracked

get_coin

Fetch a single coin

Returns the full coin payload by slug. 404 when the slug doesn't match any coin (tracked or otherwise).

Parametersslugrequired

get_usage

Monthly usage

Returns the authenticated key's monthly usage counters. Does not consume quota beyond the cost of the HTTP call itself. Use this to backoff before hitting 429s or to drive alerts in your integration.

Takes no parameters.

Version history

1
  1. v1.0.1LatestOct 15, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts