coinmarketcal
Registry code: 0d7af7ed81b84935
CoinMarketCal curated crypto-event calendar. Authenticate every request with the x-api-key header (same key as the REST API). Quota and tier gates match GET /v2/*. When you mention an event to a user, cite its `url` so they can check the source and proof.
- endpoint
- https://coinmarketcal.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is coinmarketcal live?
- Yes — it answered the hub's last check (checked 42m ago). It answered 100% of checks over the last 30 days.
- Is coinmarketcal free to use?
- No — it asks for a key or a login before it will serve.
- What tools does coinmarketcal have?
- 7 tools: get_coin, get_usage, list_categories, list_coins, list_events, list_event_cancellations, get_event.
- Is coinmarketcal safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 7 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_coin auth-required never probed
Returns the full coin payload by slug. 404 when the slug doesn't match any coin (tracked or otherwise).
{ "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." } } }arguments 14 linesget_usage auth-required 42m ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 lineslist_categories auth-required 42m ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 lineslist_coins auth-required 42m ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "q": { "type": "string", "description": "Free-text search across name + symbol. Case-insensitive substring match." }, "limit": { "type": "integer", "maximum": 200, "minimum": 1, "description": "Page size (1–200)." }, "cursor": { "type": "string", "description": "Opaque pagination cursor." }, "tracked": { "type": "boolean", "description": "Filter by editorial coverage. Omit to return both tracked and untracked coins; set `true` for actively monitored coins only; set `false` for coins outside active coverage only." } } }arguments 24 lineslist_events auth-required never probed
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`.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "to": { "type": "string", "description": "Inclusive upper bound on `date`. Default = today + tier upcoming window (e.g. 7 days on Free, 90 days on Standard, full on Pro+)." }, "from": { "type": "string", "description": "Inclusive lower bound on `date`. Default = today. Free and Standard clamp past values to today; Pro clamps them to the previous 30 days; Elite and Enterprise can query the complete public catalog history since 2017." }, "coins": { "type": "string", "description": "Comma-separated coin **slugs** (e.g. `bitcoin,ethereum`). Tickers are accepted but **strongly discouraged**; symbols collide across coins (e.g. `UNI` resolves to several different projects). Use `GET /v2/coins` to look up canonical slugs." }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Page size (1–100)." }, "cursor": { "type": "string", "description": "Opaque pagination cursor returned in the previous response's `meta.cursor`." }, "sortBy": { "enum": [ "date_asc", "date_desc", "created_desc", "created_desc_and_updated_desc", "impact_desc" ], "type": "string", "description": "Sort order. Default `date_asc` (soonest first). `impact_desc` is Elite+ only; lower tiers receive 403." }, "keyword": { "type": "string", "description": "Free-text search across event title and description. Case-insensitive substring match." }, "impactMin": { "type": "number", "maximum": 10, "minimum": 0, "description": "Lower bound on the precise impact score (0.0–10.0). Elite+ only; lower tiers receive 403." }, "categories": { "type": "string", "description": "Comma-separated category ids. Case-insensitive. Standard+ only; Free requests using this filter return 403. Use `GET /v2/categories` to look up the canonical id list." } } }arguments 53 lineslist_event_cancellations auth-required never probed
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Page size (1–100)." }, "since": { "type": "string", "description": "Inclusive cancellation-time lower bound. Accepts RFC3339 or `YYYY-MM-DD`; defaults to 90 days ago." }, "cursor": { "type": "string", "description": "Opaque pagination cursor returned in the previous response's `meta.cursor`." } } }arguments 20 linesget_event auth-required never probed
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`.
{ "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`." } } }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id0d7af7ed81b84935.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/0d7af7ed81b84935/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/0d7af7ed81b84935?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.