Skip to content

CryptoCoinStat MCP server

io.cryptocoinstat/mcpcryptocoinstat.iostreamable-httpv0.13.0Scanned

Checks on crypto tokens: live code, source gaps, real cap, owner powers, unlocks, signals.

6 tools: 5 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 5 write, 1 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

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 CryptoCoinStat MCP server can do

The CryptoCoinStat MCP server is published by cryptocoinstat.io, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: token_check, sources_disagree, check_contract, recent_signals and 1 more), but cannot delete data. 1 tool only reads.

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 once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 0.13.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.

6 tools

Changes things 5Claude Code: ask
  • check_contractGiven 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • market_gaugesThe 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, Go…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • recent_signalsWhat 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 handin…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • sources_disagreeTokens where CoinGecko and CoinMarketCap disagree most on a metric, among tokens both put at $1M or more.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • token_checkWhat 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 t…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • find_tokensFind tokens by category, live code, real fees, or an on-chain signal, e.g.No findings

    Why it is in this group

    • The name "find_tokens" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true

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.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:21 UTC, unchanged since Nov 16, 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
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://cryptocoinstat.io/api/mcp: tools/list returned 10 tools to an anonymous client, including token_check (write), sources_disagree (write), check_contract (write), recent_signals (write), market_gauges (write) and 3 more

    What this check looks for

Posture changes

  1. Nov 16, 2026
    • Tools that change things, listed without credentials: 5 to 8

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.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 8.View diff
    • Tools that change things, listed without credentials: 5 to 8
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.13.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http cryptocoinstat https://cryptocoinstat.io/api/mcp
claude mcp add --transport http cryptocoinstat https://cryptocoinstat.io/api/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cryptocoinstat__find_tokens"
    ],
    "ask": [
      "mcp__cryptocoinstat__token_check",
      "mcp__cryptocoinstat__sources_disagree",
      "mcp__cryptocoinstat__check_contract",
      "mcp__cryptocoinstat__recent_signals",
      "mcp__cryptocoinstat__market_gauges"
    ],
    "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 cryptocoinstat. 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/io.cryptocoinstat/mcp/verify?hash=9834c551f31bc088df441a6069158287a03137772a8578f4e2c764caefda7aaf" | jq -e '.changed == false'

Pinned hash 9834c551f31b, from Nov 8, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.cryptocoinstat/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.cryptocoinstat/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.cryptocoinstat/mcp.svg)](https://radar.anlyon.com/servers/io.cryptocoinstat/mcp)

Source: MCP Registry. Synced Nov 8, 2026, 16:18 UTC.

CryptoCoinStat MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the CryptoCoinStat MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the CryptoCoinStat MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the CryptoCoinStat 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 CryptoCoinStat MCP server have?

6 tools: 5 write, 1 read. token_check, sources_disagree, check_contract, recent_signals, market_gauges and find_tokens.

Does the CryptoCoinStat MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the CryptoCoinStat MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the CryptoCoinStat MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.