Crypto MCP Beta MCP Server

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. The crypto mcp beta mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 8 environment variables: 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. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by 0xReisearch; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the crypto mcp beta mcp server does with a few real requests.