awesome-crypto s

This MCP repository is a curated directory of Crypto-focused MCP (Model Context Protocol) servers. Each entry points to a separate MCP server implementation that exposes datasets and capabilities for AI agents, such as on-chain data, market data, news, price feeds, and other blockchain-relevant information. There is no single runtime in this directory; instead, you would deploy or connect to individual MCP servers described in the listings and then query them through MCP tooling or your own agent workflows. Use the tools described in the MCP ecosystem (e.g., MCP toolchains, clients, or editors) to discover, authenticate, and request data from the servers that fit your needs. If you’re building an agent workflow, you can pair these servers with your LLM prompts to enrich responses with real-time crypto data, on-chain state, or market analytics.

Prerequisites:

• Node.js and npm (if you plan to run Node-based MCP tooling or servers)
• Python (if any Python-based MCP tooling is used in your environment)
• Access to the internet to fetch MCP server implementations

installation steps:

1. Install MCP tooling or MCPHub or any MCP manager you prefer following its documentation.
2. Browse the repository to identify an MCP server entry that matches your data needs (e.g., on-chain data, price feeds, news).
3. For a selected server, follow its specific installation instructions (the individual MCP server README usually provides commands). If only a directory listing is present, you can typically deploy the MCP server by cloning its repository and running its standard start command (e.g., npm run start, python -m module, or docker run) as described in that server’s docs.
4. Configure any required environment variables (API keys, network settings, or authentication tokens) as described by the server’s documentation.
5. Start the server and verify it’s reachable via its MCP endpoint or localhost port. Ensure your MCP client can discover and query the server.

Tips and common considerations:

• Many MCP servers require API keys or network access to crypto data providers; prepare and protect these credentials.
• Check the server’s supported MCP actions (e.g., token data, price feeds, historical data, on-chain events) to ensure it aligns with your use case.
• If you’re using an MCP client or manager, you may need to register the server’s endpoint, authentication method, and data schemas.
• Some entries may be implemented as services you connect to rather than self-hosted runtimes; in those cases, you’ll typically point your MCP client to a remote URL or API and use standard queries.
• Environment variables commonly include API_KEY, REGION, NETWORK, or MODE; consult each server’s docs for exact requirements.