Remote MCP Server for Analyzing Tokens using CoinGecko Market Data

Created By
Charged-Particlesa year ago
MCP Server for Analyzing Tokens using the Coin Gecko API. Includes RSI, EMA, MACD, Bollinger Bands, Golden-Cross and Death-Cross.
Overview

what is MCP Token Analyzer?

MCP Token Analyzer is a remote server application that analyzes cryptocurrency tokens using market data from the CoinGecko API. It provides various technical indicators to help users make informed trading decisions.

how to use MCP Token Analyzer?

To use MCP Token Analyzer, you need to develop it locally by installing the necessary dependencies and building the project. After that, connect your local MCP server to Claude Desktop by editing the configuration file as per the provided instructions.

key features of MCP Token Analyzer?

  • Analyzes tokens using CoinGecko market data
  • Provides technical indicators like RSI, EMA, MACD, and Bollinger Bands
  • Supports Golden-Cross and Death-Cross analysis

use cases of MCP Token Analyzer?

  1. Analyzing cryptocurrency tokens for investment opportunities
  2. Monitoring market trends using technical indicators
  3. Assisting traders in making data-driven decisions

FAQ from MCP Token Analyzer?

  • What technical indicators does MCP Token Analyzer support?

It supports RSI, EMA, MACD, Bollinger Bands, Golden-Cross, and Death-Cross.

  • Is there a guide for setting up the server?

Yes! Detailed instructions are provided in the project documentation.

  • What programming language is used for MCP Token Analyzer?

The project is developed using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Charged-Particles
Star
0
Language
TypeScript
License
MIT 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.

16 hours ago