Is the Coinmarketcal Events MCP server down?

mcp-registry/com.coinmarketcal/events · v1.0.0

healthy
Last checked 2026-10-25 23:49 UTC · handshake 772ms

As of 2026-10-25 23:49 UTC, the Coinmarketcal Events MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 1 minutes.

uptime (30d checks)
100%
checks observed
2,350
outages (90d)
1
tools
7

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

Install Coinmarketcal Events MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http coinmarketcal-events-mcp-server https://coinmarketcal.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "coinmarketcal-events-mcp-server": {
      "type": "http",
      "url": "https://coinmarketcal.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 7 tool(s); ~1,408 tokens of tool definitions.
Scores higher than 45% of 15,716 MCP servers Glimind has audited.
Its tool list costs an agent ~1,408 tokens per session — lighter than 65% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_coin, get_event, get_usage, list_categories, list_coins and 2 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.coinmarketcal%2Fevents/fixes

get_coin 1 change
{
  "name": "get_coin",
  "description": "Returns the full coin payload by slug. 404 when the slug doesn't match any coin (tracked or otherwise).",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "minLength": 1,
        "description": "Coin slug (e.g. `bitcoin`). Lowercase, URL-safe."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Fetch a single coin"
}
get_event 1 change
{
  "name": "get_event",
  "description": "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`.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "minLength": 1,
        "description": "The event id, as returned by `GET /v2/events`."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Fetch a single event"
}
get_usage 1 change
{
  "name": "get_usage",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Monthly usage"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.coinmarketcal/events"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.coinmarketcal/events"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.coinmarketcal%2Fevents.svg)](https://glimind.com/server/mcp-registry%2Fcom.coinmarketcal%2Fevents?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.coinmarketcal%2Fevents?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.coinmarketcal%2Fevents.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.coinmarketcal%2Fevents.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.coinmarketcal%2Fevents?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3c2225cb2154d342…, first seen 2026-10-17, included at leaf 1661 of 69,458. Version history · verify what your client received.

Tools (7)

Compare: most reliable data servers · most reliable other servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Coinmarketcal Events MCP server down right now?

As of 2026-10-25 23:49 UTC, the Coinmarketcal Events MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 1 minutes.

How many tools does Coinmarketcal Events MCP server provide?

Coinmarketcal Events MCP server advertises 7 tools, including get_coin, get_event, get_usage, list_categories, list_coins.

How do I install Coinmarketcal Events MCP server?

Point your MCP client at this streamable-http endpoint: https://coinmarketcal.com/mcp

Is the Coinmarketcal Events MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Coinmarketcal Events MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve