Curated Crypto MCP Server List by Luke Fan

Overview

This repository is a curated list of MCP (Model Context Protocol) servers focused on the cryptocurrency and blockchain space, assembled by Luke Fan. It collects public MCP server endpoints, short descriptions, activity indicators, and security notes so developers and researchers can compare offerings, join active communities, and pick the right server for their workflows.

MCP servers provide a simple, standardized way to expose model context, tools, or plugins to LLM clients (for example, serving retrieval contexts, tool endpoints, or model extensions). This curated list is intended as a neutral, community-maintained index: it helps you discover servers, evaluate their features, and perform quick checks before integrating them into your applications. The canonical list lives on GitHub: https://github.com/badkk/awesome-crypto-mcp-servers

Features

• Curated and focused on crypto-related MCP servers and communities
• Short metadata for each entry: name, URL, supported models/tools, tags, status
• Activity indicators (last-seen or community links) to surface maintained servers
• Security and privacy notes where available (TLS, API keys, rate limits)
• Simple format intended for easy parsing and integration into tools or dashboards
• Community-driven: add, update, or flag entries via GitHub PRs

Installation / Configuration

The list is maintained as a normal Git repository. To get a local copy:

# clone the repository
git clone https://github.com/badkk/awesome-crypto-mcp-servers.git
cd awesome-crypto-mcp-servers

# inspect the list (typically Markdown or JSON/YAML files)
ls -la

Typical quick checks you can run against an MCP server entry (replace SERVER_URL with the URL from the list):

1. HTTP HEAD to check availability:

curl -I https://SERVER_URL/.well-known/mcp

2. Basic JSON discovery request (some MCP servers expose discovery at a known path):

curl -s https://SERVER_URL/.well-known/mcp | jq .

3. TLS certificate inspection:

echo | openssl s_client -servername SERVER_URL -connect SERVER_URL:443 2>/dev/null | openssl x509 -noout -subject -dates

Adding an MCP server to your client (example JSON snippet)

{
  "name": "Example Crypto MCP",
  "url": "https://mcp.example.crypto",
  "description": "Provides on-chain retrieval contexts and trading tools",
  "supported_models": ["gpt-4o-mini", "local-llama"],
  "tls": true,
  "auth": "api_key",
  "community": "https://discord.gg/example"
}

Persist this snippet in your client config or discovery registry and use your client’s standard discovery routine to consume the endpoint.

Available Resources

• GitHub repository (primary index): https://github.com/badkk/awesome-crypto-mcp-servers
• Typical discovery endpoints to check on servers: /.well-known/mcp, /mcp/discovery, /status
• Community/contact links included per-entry: Discord, Telegram, X/Twitter, GitHub issues
• Tools that help validate servers: curl, jq, openssl, nmap (for port checks), and basic HTTP clients

Use Cases

• Compare servers before integrating a retrieval or tool plugin:
  • Example: You want an MCP server that exposes on-chain data retrieval and a WebSocket tool. Use the list to filter entries with tags “on-chain”, “websocket”, then run the discovery and TLS checks.
• Join active communities to ask questions or request features:
  • Example: Find a server with a linked Discord. Join, ask about rate limits, and test sample queries in a sandbox channel.
• Security vetting before production use:
  • Example: For a trading bot, choose servers that explicitly require API keys and serve over TLS. Run certificate inspection and measure latency with curl.
• Monitoring and fallbacks:
  • Example: Use two or three curated servers from the list as fallbacks. Implement periodic HEAD checks and switch clients if a primary server becomes unavailable.
• Research and benchmarking:
  • Example: Collect response times and supported model lists from several servers to benchmark retrieval latency or model compatibility for crypto-specific prompts.

Practical comparison guide (table)

Use the curated list as a starting point. Always perform validation (availability, TLS, auth, and simple functional tests) before wiring a third-party MCP server into production systems.