mcp-server-coingecko: A CoinGecko MCP server

Created By
bestjanea year ago
CoinGecko API 服务实现
Overview

what is mcp-server-coingecko?

mcp-server-coingecko is a Model Context Protocol server designed for querying cryptocurrency data through the CoinGecko API. It allows users to interact with the API to retrieve cryptocurrency prices, historical data, and market information.

how to use mcp-server-coingecko?

To use mcp-server-coingecko, run the server using the command uv run mcp-coingecko-server and utilize the provided functions to query cryptocurrency data.

key features of mcp-server-coingecko?

  • Access to current cryptocurrency prices
  • Retrieval of historical price data
  • Detailed information about specific cryptocurrencies
  • Trending coins data for the last 24 hours

use cases of mcp-server-coingecko?

  1. Fetching the current price of Bitcoin or Ethereum.
  2. Analyzing historical price trends for various cryptocurrencies.
  3. Identifying trending cryptocurrencies in the market.

FAQ from mcp-server-coingecko?

  • What kind of data can I retrieve?

You can retrieve current prices, historical data, detailed information about cryptocurrencies, and trending coins.

  • Is there a limit to the number of queries?

The API has rate limits, so please refer to the CoinGecko API documentation for details.

  • Can I use this server for commercial purposes?

Please check the licensing terms of the CoinGecko API for commercial use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bestjane
Star
1
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

12 minutes ago