Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch
README.md
# REI Crypto MCP Server - Beta

FastMCP implementation of the in-house MCP servers used by Units of the Rei Network.
You can use them without providing API keys at app.reisearch.box or you can use them with other MCP clients deploying them yourself.

Everything is to be considered still in beta. Expect things to be added or changed with no warnings.

## Current MCP servers:
- DefiLlama Pro API
- CoinGecko Pro API
- Arkham Intelligence API
- Elfa AI API
- Codex API

Codex at the moment is just used for searching a contract address from the name. Deeper implementation will come in the near future.
Codex uses GraphQL for it's query system. Edit the query to hardcode some parameters in case you need stricter filtering.

## Prerequisites

- Python 3.12
- `uv` package manager
- API keys for the services you plan to use

## Installation

1. Clone the repository:
```bash
git clone https://github.com/0xReisearch/crypto-mcp-beta
cd crypto-mcp-beta
```

2. Install uv (if not already installed):
```bash
curl -LsSf https://astral.sh/uv/install.sh | sh
```

3. Create and activate a virtual environment with uv:
```bash
uv venv
source .venv/bin/activate  # On Unix/macOS
# or
.venv\Scripts\activate  # On Windows
```

4. Install dependencies from pyproject.toml:
```bash
uv pip install .
```

5. Set up your environment variables:
```bash
cp .env_example .env
```

Edit `.env` with your API keys:
```
ARKHAM_API_KEY=<YOUR ARKHAM_API_KEY>
CG_API_KEY=<YOUR_CG_API_KEY>
DEFILLAMA_API_KEY=<YOUR_DEFILLAMA_API_KEY>
CODEX_API_KEY=<YOUR_CODEX_API_KEY>
ELFA_API_KEY=<YOUR_ELFA_API_KEY>
```

## Running the Servers

You can run each server individually:

```bash
# Run DefiLlama server
uv run defillama_server.py

# Run CoinGecko server
uv run cg_server.py

# Run Arkham server
uv run arkham_server.py

# Run Codex server
uv run codex_server.py

# Run Elfa AI server
uv run elfa_server.py
```

## Configuring Claude Desktop

To use these servers with Claude Desktop, you need to configure the `claude_desktop_config.json` file. This file is typically located in:
- Windows: `%APPDATA%/claude-desktop/claude_desktop_config.json`
- macOS: `~/Library/Application Support/claude-desktop/claude_desktop_config.json`
- Linux: `~/.config/claude-desktop/claude_desktop_config.json`

Example configuration:
```json
{
    "mcpServers": {
        "arkham": {
            "command": "ssh",
            "args": [
                "user@your-host",
                "cd /path/to/crypto_mcp && /path/to/uv run arkham_server.py"
            ]
        },
        "coingecko": {
            "command": "ssh",
            "args": [
                "user@your-host",
                "cd /path/to/crypto_mcp && /path/to/uv run cg_server.py"
            ]
        },
        "defillama": {
            "command": "ssh",
            "args": [
                "user@your-host",
                "cd /path/to/crypto_mcp && /path/to/uv run defillama_server.py"
            ]
        },
        "codex": {
            "command": "ssh",
            "args": [
                "user@your-host",
                "cd /path/to/crypto_mcp && /path/to/uv run codex_server.py"
            ]
        },
        "elfa": {
            "command": "ssh",
            "args": [
                "user@your-host",
                "cd /path/to/crypto_mcp && /path/to/uv run elfa_server.py"
            ]
        }
    }
}
```

Replace the following:
- `user@your-host`: Your SSH username and host
- `/path/to/crypto_mcp`: The absolute path to where you cloned this repository
- `/path/to/uv`: The absolute path to your uv installation (usually in `~/.local/bin/uv` on Unix systems)

## API Documentation

- [DefiLlama API Documentation](https://defillama.com/pro-api/docs)
- [CoinGecko API Documentation](https://docs.coingecko.com/reference/introduction)
- [Codex API Documentation](https://docs.codex.io/reference/overview)
- [Elfa AI Api Documentation](https://www.elfa.ai/) - Contact Elfa directly for api access.
- [Arkham Intelligence](https://intel.arkm.com/) - You need to contact Arkham directly for api access.

## Feedback

If you encounter any issues or have suggestions for improvements:

1. For bug reports or feature requests, please open an issue in this repository
2. For general feedback or questions, you can leave a comment in the repository discussions


Made with ❤️ by [Rei Network](https://reisearch.box)

TDQS

B3.1/5.0

Scored across 61 tools

Disambiguation3/5

Tools are generally distinct by resource type (e.g., bridges, prices, protocols), but there is notable overlap in some areas. For example, multiple price-related tools (get_current_prices, get_historical_prices, get_price_chart, get_price_percentage) could cause confusion about which to use for specific price queries. Similarly, overview and summary tools for derivatives, dexs, and options have overlapping purposes that might require careful reading of descriptions to differentiate.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun pattern throughout, all starting with 'get_' followed by a descriptive noun phrase (e.g., get_bridge_details, get_historical_prices). There are no deviations in naming style, making it easy to predict tool names and understand their general purpose at a glance.

Tool Count2/5

With 61 tools, the count is excessive for a single server, making it overwhelming and difficult for an agent to navigate efficiently. While the server covers a broad crypto domain (prices, bridges, protocols, yields, etc.), the toolset feels bloated and could benefit from consolidation or modularization into more focused servers.

Completeness4/5

The toolset provides extensive coverage across multiple crypto domains (e.g., prices, bridges, protocols, yields, stablecoins), with CRUD-like operations for many resources. However, there are minor gaps, such as limited update or delete operations (typical for read-heavy APIs) and some areas like user data or emissions lacking full lifecycle coverage, though agents can likely work around these given the breadth of read operations.

Maintenance

ActivityInactive
ResponsivenessNo issues