MCP Crypto Server

Created By
yanqinghaoa year ago
Overview

what is MCP Crypto Server?

MCP Crypto Server is a high-performance cryptocurrency market data and analysis platform that provides real-time market data, advanced analytics, and news aggregation.

how to use MCP Crypto Server?

To use MCP Crypto Server, clone the repository, set up the environment, and start the server. You can then connect via MCP clients to access market data and analysis tools.

key features of MCP Crypto Server?

  • Real-time market data from multiple exchanges
  • Historical data analysis
  • LLM integration for market insights
  • Scalable architecture for high request volumes
  • Multi-exchange support via CCXT
  • Crypto news aggregation and sentiment analysis

use cases of MCP Crypto Server?

  1. Analyzing cryptocurrency market trends
  2. Accessing real-time and historical market data
  3. Generating AI-driven insights and trading recommendations
  4. Monitoring news sentiment related to cryptocurrencies

FAQ from MCP Crypto Server?

  • Can MCP Crypto Server connect to all cryptocurrency exchanges?

Yes! It supports multiple exchanges through the CCXT library.

  • Is MCP Crypto Server free to use?

Yes! The server is open-source and free to use.

  • What technologies are used in MCP Crypto Server?

It is built using FastMCP, CCXT, TimescaleDB, and Python.

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

21 hours ago