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

cryptocoinstat

https://cryptocoinstat.io

Registry code: ef243023def9e230

api record

CryptoCoinStat shows what can be checked about a crypto token: whether its code is moving, whether it is used (fees, TVL), whether CoinGecko and CoinMarketCap agree on its numbers, and, for the top 1000, what the chain and the futures markets say: real vs paper market cap, owner powers, holders, unlocks, copies under its ticker, open interest, funding, liquidations and where Hyperliquid positions would be liquidated. Report read dates. “Not found” and “not read” don’t mean absent. For a contract address use check_contract; for what changed lately use recent_signals; for the market as a whole…

endpoint
https://cryptocoinstat.io/api/mcp
protocol
streamable-http ·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 it live, free and safe measured by this hub
Is cryptocoinstat live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is cryptocoinstat free to use?
Yes — the hub reached it with no key and no payment.
What tools does cryptocoinstat have?
6 tools: token_check, recent_signals, check_contract, find_tokens, sources_disagree, market_gauges.
Is cryptocoinstat 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
100%

90 days 100%· all time 100%

latency
278ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ 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 6 tools
3 open 3 never probed 3 of 6 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.

  • find_tokens open 2h ago

    Find tokens by category, live code, real fees, or an on-chain signal, e.g. “DePIN tokens with live code” or “tokens whose market cap is mostly paper”. Signals cover the top 1000: thin = real cap under half the market cap (order books too shallow for its size), unbacked = under half the volume venues report is carried by their order books (on $1M+ a day), unlocks = next 30 days of vesting worth more than a day of trading, heated = open interest at 30%+ of market cap or funding beyond ±0.05% per 8h, mint = the owner can mint, whales = ten wallets hold half the supply, fakes = copies under its ticker whose owner can take or freeze tokens.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "lang": {
          "enum": [
            "en",
            "ru"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the text answer: en or ru"
        },
        "sort": {
          "enum": [
            "fees",
            "code",
            "rank"
          ],
          "type": "string",
          "default": "rank",
          "description": "Order: fees: most fees first; code: most commits first; rank: market cap rank"
        },
        "limit": {
          "type": "integer",
          "default": 6,
          "maximum": 25,
          "minimum": 1,
          "description": "How many to return, 1 to 25"
        },
        "signal": {
          "enum": [
            "thin",
            "unbacked",
            "unlocks",
            "heated",
            "mint",
            "whales",
            "fakes"
          ],
          "type": "string",
          "description": "On-chain signal: thin, unbacked, unlocks, heated, mint, whales, fakes"
        },
        "hasCode": {
          "type": "boolean",
          "default": false,
          "description": "Only tokens with commits by people in the last 90 days"
        },
        "hasFees": {
          "type": "boolean",
          "default": false,
          "description": "Only tokens whose users paid fees in the last 30 days"
        },
        "category": {
          "type": "string",
          "description": "e.g. \"DePIN\", \"Lending\", \"AI\""
        }
      },
      "additionalProperties": false
    }
    arguments 60 lines
  • sources_disagree open 2h ago

    Tokens where CoinGecko and CoinMarketCap disagree most on a metric, among tokens both put at $1M or more. Use for questions about which market caps or supply figures differ.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "lang": {
          "enum": [
            "en",
            "ru"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the text answer: en or ru"
        },
        "limit": {
          "type": "integer",
          "default": 6,
          "maximum": 25,
          "minimum": 1,
          "description": "How many to return, 1 to 25"
        },
        "metric": {
          "enum": [
            "price",
            "supply",
            "mcap",
            "volume"
          ],
          "type": "string",
          "default": "mcap",
          "description": "Which figure: price, supply (circulating), mcap (market cap) or volume (24h)"
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • market_gauges open 2h ago

    The market as a whole right now, from what CryptoCoinStat reads: risk appetite 0–100 (funding, which side the last day of liquidations hit, how many top alts are up over a week, Google search interest; each part shown), altcoin season 0–100 (how many of the top 100 alts beat bitcoin over 90 days), leverage 0–100 (open-interest-weighted funding and how many perp markets run hot), real volume (the share of venue-reported volume their order books could carry), 24h liquidations split into longs and shorts, unlocks due in 30 days in dollars and days of depth, and search interest against its 90-day mean. With the change over a day or a week. Use when someone asks about market sentiment, fear and greed, altcoin season, leverage or liquidations across the market.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "lang": {
          "enum": [
            "en",
            "ru"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the text answer: en or ru"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • token_check unknown never probed

    What can be checked about one crypto token: code activity on GitHub, fees and TVL, whether CoinGecko and CoinMarketCap agree on price, supply, market cap and volume, and, for the top 1000, what the chain says: paper vs real market cap (order-book depth), how much of the reported volume the order books could carry and which venues they couldn’t, owner powers over the contract, top-10 wallet share, unlocks in the next 30 days, copies and wrappers of the token on other chains, supply on each chain with how bridged copies are backed, leverage (open interest on Binance, Bybit, OKX and Hyperliquid against market cap and depth, funding, 24h liquidations, Hyperliquid liquidations within 5% of the price) and the token’s latest signals. With read dates. Use when someone asks about a token, whether a project is alive or used, whether its market cap is real, how much leverage sits on it, or whether it is safe from the contract side.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "ru"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the text answer: en or ru"
        },
        "query": {
          "type": "string",
          "description": "Token name or ticker, e.g. \"UNI\""
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • recent_signals unknown never probed

    What changed on-chain for the top 1000 tokens in the last month, newest first: unlocks within a week that the market can’t absorb (unlock), contract owners gaining powers or handing the contract on (admin), large holders sending to or taking from exchange addresses, or locked tokens reaching wallets (whale), pool liquidity falling 30%+ (drain), new dangerous copies under the ticker with real money in their pools (fake), a home-chain mint its vesting and emission schedule doesn’t cover (mint), a bridged copy losing its backing or supply growing on another chain with no mint at home (bridge), and an exchange announcing it lists or delists the token, spot or perpetuals (listing: OKX, Bybit, KuCoin, Bitget, from their own announcement APIs), an exploit of the token’s protocol with its reported loss (hack, from DeFiHackLabs), and the project’s website going dark or its domain parked (site). Each money signal is sized against 2% order-book depth and a day of trading volume. Filter by kind or by token. Use when someone asks what is happening with a token, about whale moves, upcoming unlocks, or risks to watch.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "kind": {
          "enum": [
            "unlock",
            "mint",
            "bridge",
            "admin",
            "whale",
            "drain",
            "fake",
            "hack",
            "listing",
            "site"
          ],
          "type": "string",
          "description": "Only this kind: unlock, mint, bridge, admin, whale, drain, fake, hack, listing, site"
        },
        "lang": {
          "enum": [
            "en",
            "ru"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the text answer: en or ru"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 30,
          "minimum": 1,
          "description": "How many to return, 1 to 30"
        },
        "token": {
          "type": "string",
          "description": "Token name or ticker, e.g. \"UNI\""
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • check_contract unknown never probed

    Given a token contract address (EVM 0x… or Solana), say what it is: a token’s own contract, an official deployment, a listed wrapper or bridge, or a copy trading under a real token’s ticker that no list names, and whether that copy’s owner can take or freeze tokens. Use before anyone buys or bridges by address, or when a link or airdrop names a contract. Covers the top 1000 tokens.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "address"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "ru"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the text answer: en or ru"
        },
        "address": {
          "type": "string",
          "minLength": 20,
          "description": "Contract or mint address"
        }
      },
      "additionalProperties": false
    }
    arguments 24 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 ef243023def9e230.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ef243023def9e230/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/ef243023def9e230/badge.svg)](https://brick.blue/agent/ef243023def9e230?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.