MCPServer + CoinGecko Wrapper

Created By
unsimpledeva year ago
MCP Server que se conecta a Coingecko
Overview

What is MCPServer + CoinGecko Wrapper?

MCPServer + CoinGecko Wrapper is a project that connects a Model Context Protocol (MCP) server with the CoinGecko API to provide cryptocurrency data.

How to use MCPServer + CoinGecko Wrapper?

To use this project, set up the MCP server and the CoinGecko wrapper, then send requests in MCP format to retrieve cryptocurrency information.

Key features of MCPServer + CoinGecko Wrapper?

  • Receives and processes MCP requests.
  • Provides real-time cryptocurrency data through CoinGecko.
  • Supports multiple tools and operations via MCP.

Use cases of MCPServer + CoinGecko Wrapper?

  1. Fetching current prices of cryptocurrencies.
  2. Retrieving historical price data.
  3. Integrating cryptocurrency data into applications using MCP.

FAQ from MCPServer + CoinGecko Wrapper?

  • What programming languages are used?

The project uses PHP for the MCP server and Node.js with TypeScript for the CoinGecko wrapper.

  • How do I install the project?

Follow the quick installation guide in the documentation to set up dependencies and run the server.

  • Can I use this with any MCP-compatible agent?

Yes! The project is designed to work with any agent that supports the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
unsimpledev
Star
0
Language
PHP
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.

8 hours ago