_ registry / mcp http-sse · checked 2h ago

Crypto.com Exchange MCP

https://mcp.crypto.com

Registry code: 04e7e7e5fb72d939

api record

Crypto.com Exchange MCP Server - Real-time cryptocurrency market data and interactive widgets.

Available Tools:

endpoint
https://mcp.crypto.com/market-data/mcp
protocol
http-sse ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Crypto.com Exchange MCP live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is Crypto.com Exchange MCP free to use?
Yes — the hub reached it with no key and no payment.
What tools does Crypto.com Exchange MCP have?
9 tools: get_trades, get_index_price, get_mark_price, get_book, get_ticker, get_instrument, get_candlestick, get_tickers, ….
Is Crypto.com Exchange MCP 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.
reachable
live
uptime, 30 days
99.2%

90 days 99.2%· all time 99.2%

latency
359ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 395 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
crypto & onchain prices & market data
used for
  • get cryptocurrency order book
  • get cryptocurrency trade history
  • get cryptocurrency candlestick data
  • get cryptocurrency index price
  • list available trading instruments
takes → gives
text → data
tools
9 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
2 open 7 never probed 2 of 9 classified

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_tickers reads open 14h ago

    Tickers for an instrument or all

    mcp-tool

    {
  "type": "object",
  "title": "PublicGetTickersParams",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "instrument_name": {
      "type": [
        "string",
        "null"
      ],
      "description": "Optional instrument name filter"
    }
  }
}
    arguments 14 lines
  • get_instruments reads open 14h ago

    List all available trading instruments

    mcp-tool

    {
  "type": "object",
  "title": "PublicGetInstrumentsParams",
  "$schema": "http://json-schema.org/draft-07/schema#"
}
    arguments 5 lines
  • get_trades reads unknown 24h ago

    Recent trades (default 10, max 150)

    mcp-tool

    {
  "type": "object",
  "title": "PublicGetTradesParams",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "instrument_name"
  ],
  "properties": {
    "count": {
      "type": [
        "integer",
        "null"
      ]
    },
    "instrument_name": {
      "type": "string"
    }
  }
}
    arguments 19 lines
  • get_index_price reads unknown 14h ago

    Index price for an instrument

    mcp-tool

    {
  "type": "object",
  "title": "PublicGetIndexPriceParams",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "instrument_name"
  ],
  "properties": {
    "instrument_name": {
      "type": "string"
    }
  }
}
    arguments 13 lines
  • get_mark_price reads unknown 6h ago

    Mark price for an instrument

    mcp-tool

    {
  "type": "object",
  "title": "PublicGetMarkPriceParams",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "instrument_name"
  ],
  "properties": {
    "instrument_name": {
      "type": "string"
    }
  }
}
    arguments 13 lines
  • get_book reads unknown never probed

    Order book snapshot (bids/asks)

    mcp-tool

    {
  "type": "object",
  "title": "PublicGetBookParams",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "instrument_name"
  ],
  "properties": {
    "depth": {
      "type": [
        "integer",
        "null"
      ]
    },
    "instrument_name": {
      "type": "string"
    }
  }
}
    arguments 19 lines
  • get_ticker reads unknown 6h ago

    Single ticker for an instrument

    mcp-tool

    {
  "type": "object",
  "title": "PublicGetTickerParams",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "instrument_name"
  ],
  "properties": {
    "instrument_name": {
      "type": "string"
    }
  }
}
    arguments 13 lines
  • get_instrument reads unknown 6h ago

    Instrument detail for an instrument by id

    mcp-tool

    {
  "type": "object",
  "title": "PublicGetInstrumentParams",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "instrument_name"
  ],
  "properties": {
    "instrument_name": {
      "type": "string"
    }
  }
}
    arguments 13 lines
  • get_candlestick reads unknown 24h ago

    Recent candlesticks for an instrument and timeframe (returns up to 50)

    mcp-tool

    {
  "type": "object",
  "title": "PublicGetCandlestickParams",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "instrument_name",
    "timeframe"
  ],
  "properties": {
    "timeframe": {
      "type": "string"
    },
    "instrument_name": {
      "type": "string"
    }
  }
}
    arguments 17 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 04e7e7e5fb72d939.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/04e7e7e5fb72d939/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/04e7e7e5fb72d939/badge.svg)](https://brick.blue/agent/04e7e7e5fb72d939?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.