CoinGecko-app

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Keyless CoinGecko MCP server with visual widgets for crypto prices, charts, coin comparisons, trending coins and news.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "CoinGecko-app": {
      "url": "https://mcp.coingecko.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (13)

• get-coin-markets read-only

  Get current market data (price, market cap, FDV, 24h volume, supply, market cap rank) for a list of CoinGecko coin ids, or for the top N coins by market cap. One coin renders a price card with an interactive chart (24h–Max range, price/market-cap toggle); several render a grid of cards. Use this when the user asks for the price or market data of specific coins, for a top-N leaderboard by market cap, or for a chart or price history of one coin — for a chart, also pass chartDays (e.g. 'ETH price last 90 days' → ids ["ethereum"], chartDays "90"). Provide either ids or topN, not both. To compare or contrast 2–4 specific coins (e.g. "BTC vs ETH"), use compare-coins instead. Not financial advice.

  Parameters:

  • ids — array — CoinGecko coin *ids* (not tickers), e.g. ["bitcoin", "ethereum", "solana", "zcash"]. Up to 20. Map user tickers/names to ids yourself.
  • topN — integer — Return the top N coins by market cap (1–20). Provide either ids or topN, not both; ids wins if both are given.
  • chartDays — string — Chart range for the price card when the request resolves to exactly one coin: 1=24h, 7=7d, 30=1m, 90=3m, 365=1Y, max=all-time, ytd=year-to-date. Pass it when the user asks for a chart or price history of one coin. Ignored for multiple coins.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• compare-coins read-only

  Compare 2–4 coins side by side — price, market cap, FDV, multi-window price change (1h/24h/7d/30d), volume, supply, distance from all-time high — in a visual widget. Use this when the user asks to compare, contrast, or pit specific coins against each other (phrasing like 'compare', 'vs', 'versus', 'against', e.g. 'BTC vs ETH vs SOL'). Map tickers to ids yourself. Not for a single coin (use get-coin-markets) and not financial advice.

  Parameters:

  • ids (required) — array — Two to four CoinGecko coin *ids* (not tickers) to compare, e.g. ["bitcoin", "ethereum", "solana"]. Map user tickers/names to ids yourself.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• get-coin-market-chart read-only

  Get a single coin's historical price and market cap series over a date range, as data: up to 120 evenly spaced points plus start and end timestamps. Use this when the user needs the numbers behind a price history, e.g. to compute a return or find the high and low over a period. To show a chart of one coin, call get-coin-markets with chartDays instead. Not for the current spot price (use get-coin-markets) and not financial advice.

  Parameters:

  • id (required) — string — CoinGecko coin id, e.g. 'bitcoin'
  • days (required) — string — Chart date range: 1=24h, 7=7d, 30=1m, 90=3m, 365=1Y, max=all-time, ytd=year-to-date

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• get-coin-history read-only

  Get a coin's price, market cap and 24h volume on a specific past date (snapshot at 00:00 UTC). Use this when the user asks what a coin was worth on a given date, e.g. 'BTC price on Jan 1 2024'. Not for current prices (use get-coin-markets) or price ranges over time (use get-coin-market-chart), and not financial advice.

  Parameters:

  • id (required) — string — CoinGecko coin id, e.g. 'bitcoin'
  • date (required) — string — Snapshot date, YYYY-MM-DD (UTC). Must be a past date on or after 2013-04-28; for today's price use get-coin-markets.
  • vsCurrency — string — Fiat quote currency (lowercase ISO code). Defaults to usd.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• get-coin-info read-only

  Get descriptive project information about a coin: what it is (a short description), its categories/sectors, official links (website, explorer, Twitter/X, Reddit, GitHub, Telegram) and launch date. Use this when the user asks what a coin *is* or wants background on a project, e.g. 'what is Chainlink?' or 'tell me about Solana'. Not for prices or market data (use get-coin-markets) and not financial advice.

  Parameters:

  • id (required) — string — CoinGecko coin id, e.g. 'bitcoin'

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• search-coingecko read-only

  Resolve a name, ticker, CoinGecko id, network, category, exchange, NFT collection, or exact token contract address to a structured CoinGecko identity. Use this when a user's crypto reference is ambiguous or an exact id/address must be resolved before another tool call. Optional type and chain hints narrow the lookup; token name/ticker searches require chain. Returns one selected match only when the upstream evidence is unique, otherwise explicit alternatives. Data-only, cacheless, and not for prices or financial advice.

  Parameters:

  • query (required) — string — Name, ticker, CoinGecko id, or exact contract address to resolve
  • type — string — Optional entity-type hint: coin, category, network, token, exchange, or nft
  • chain — string — CoinGecko asset-platform id used to scope token searches, e.g. ethereum or base

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• search-coins read-only

  Deprecated: use search-coingecko for all new resolution and routing. This compatibility tool searches only CoinGecko coins by name or ticker and returns the legacy coin-id list. Use this when an existing caller requires the old search-coins response shape, and only for that compatibility case. Not for prices — call get-coin-markets with a resolved id.

  Parameters:

  • query (required) — string — Coin name or ticker to search, e.g. 'bitcoin' or 'ethereum'

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• get-trending read-only

  Get the coins trending on CoinGecko in the last 24 hours, with market cap rank, price and 24h change. Use this when the user asks what's hot, trending, or popular right now. Not for prices of specific coins (use get-coin-markets) and not financial advice.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• get-categories read-only

  Get a ranked leaderboard of crypto categories (sectors/narratives like DeFi, Layer 1, memes, AI, RWA) by total market cap and 24h change. Use this when the user asks which sectors, narratives, or themes are hot, big, or moving. Order by market cap (default) or 24h change. Not for individual trending coins (use get-trending) or overall market health (use get-global-market), and not financial advice.

  Parameters:

  • order — string — Sort dimension: 'market_cap' for the largest sectors (default), 'market_cap_change_24h' for the hottest sectors by 24h change.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• get-global-market read-only

  Get a snapshot of the overall crypto market: total market cap, 24h change, total volume, BTC/ETH dominance, plus current price and 24h change for the top-cap coins (BTC, ETH, SOL, BNB, XRP). Use this when the user asks how the crypto market is doing overall. For prices of other/arbitrary coins, use get-coin-markets.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• get-top-gainers-losers read-only

  Get the top gaining and top losing coins over a time window (1h, 24h or 7d), with price and change. Use this when the user asks what's pumping, dumping, or moving today. Not for a single coin's price (use get-coin-markets). Data only — never frame as a buy/sell signal. Requires a CoinGecko Pro API key.

  Parameters:

  • duration — string — Time window for the ranking; defaults to 24h

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• get-crypto-news read-only

  Get recent crypto news headlines — global, or filtered to one coin via coinId. Use this when the user asks for the latest news, headlines, or updates about crypto in general or about a specific coin. Headlines and links are presented verbatim; never summarized as bullish/bearish and never financial advice. Not for what a coin is (use get-coin-info) or price data (use get-coin-markets).

  Parameters:

  • limit — integer — How many articles to return, 1–20, default 10
  • coinId — string — CoinGecko coin id to filter news to, e.g. 'bitcoin'. Omit for global headlines. Map user tickers/names to ids yourself.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• send_feedback

  Records feedback about this MCP server, including unexpected tool failures, unhelpful responses, or missing capabilities observed by the agent or reported by the user.

  Parameters:

  • content (required) — string — The feedback content, stripped of any PII.
  • source (required) — string — Who initiated the feedback: "user" or "model".

  Hints: read-only no · destructive no · idempotent not declared · open-world yes

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.