CoinMarketCal MCP server
com.coinmarketcal/eventscoinmarketcal.comstreamable-httpv1.2.0Scanned
Crypto events calendar: dated, sourced and impact-scored events for 14,000+ coins.
7 tools: 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CoinMarketCal MCP server can do
The CoinMarketCal MCP server is published by coinmarketcal.com, a domain the MCP Registry verified. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Only reads 7Show 7 read-only tools
get_coinReturns the full coin payload by slug.No findings
Why it is in this group
- The name "get_coin" says "get": a word for reading.
Description, as the server wrote it Returns the full coin payload by slug. 404 when the slug doesn't match any coin (tracked or otherwise).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_eventReturns the full event payload by id.No findings
Why it is in this group
- The name "get_event" says "get": a word for reading.
Description, as the server wrote it 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`. When `isEstimated` is true, `date` is a deadline or window end, not an exact time; `displayedDate` holds the display form (e.g. `Q2 2026`).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_usageReturns the authenticated key's monthly usage counters.No findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_categoriesReturns every category in the editorial taxonomy with the count of upcoming events per category (tier-windowed).No findings
Why it is in this group
- The name "list_categories" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_coinsReturns a paginated list of coins ordered by `rank` ascending (top-ranked first).No findings
Why it is in this group
- The name "list_coins" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_event_cancellationsReturns removal records ordered by `cancelledAt`, then `id`.No findings
Why it is in this group
- The name "list_event_cancellations" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_eventsReturns a paginated list of upcoming and historical events within the date window available to the caller's plan.No findings
Why it is in this group
- The name "list_events" says "list": a word for reading.
Description, as the server wrote it 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`. When `isEstimated` is true, `date` is a deadline or window end, not an exact time; `displayedDate` holds the display form (e.g. `Q2 2026`).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:36 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://coinmarketcal.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://coinmarketcal.com/api/developer/auth
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
Posture changes
- Nov 20, 2026
- RFC 9728 protected resource metadata: none to https://coinmarketcal.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://coinmarketcal.com/api/developer/auth
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://coinmarketcal.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://coinmarketcal.com/api/developer/auth; Dynamic client registrati…View diff
- RFC 9728 protected resource metadata: none to https://coinmarketcal.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://coinmarketcal.com/api/developer/auth
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
Tools7 changed.~7 changedView diff
- Changed:get_coinOnly readsannotations
- Changed:get_eventOnly readsdescriptioninputSchemaannotations
- Changed:get_usageOnly readsannotations
- Changed:list_categoriesOnly readsannotations
- Changed:list_coinsOnly readsannotations
- Changed:list_event_cancellationsOnly readsannotations
- Changed:list_eventsOnly readsdescriptioninputSchemaannotations
Tools1 changed.~1 changedView diff
- Changed:list_eventsOnly readsinputSchema
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http events https://coinmarketcal.com/mcpclaude mcp add --transport http events https://coinmarketcal.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__events__list_events",
"mcp__events__list_event_cancellations",
"mcp__events__get_event",
"mcp__events__list_categories",
"mcp__events__list_coins",
"mcp__events__get_coin",
"mcp__events__get_usage"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as events. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.coinmarketcal/events/verify?hash=8001ba124dacd5efb2adc5463205ec174208b14302e03001bc346903fa9d9e4f" | jq -e '.changed == false'Pinned hash 8001ba124dac, from Nov 19, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.coinmarketcal/events/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.coinmarketcal/events)Source: MCP Registry · repository. Synced Nov 19, 2026, 11:17 UTC.
CoinMarketCal MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CoinMarketCal MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the CoinMarketCal MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CoinMarketCal MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CoinMarketCal MCP server have?
- 7 tools: 7 read. list_events, list_event_cancellations, get_event, list_categories, list_coins, get_coin and get_usage.
Does the CoinMarketCal MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CoinMarketCal MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CoinMarketCal MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.