Crypto Fear & Greed Index
kukapayLABSCO SUMMARY
The author calls it beta and says things will change without warning — take that at face value.
This is an internal toolset published as-is rather than a product with a compatibility promise, which is fine for research and bad for anything you schedule. The genuine value is the bundling: crypto questions almost always span price, protocol metrics and on-chain attribution, and normally that is three integrations and three keys. Being able to start against their hosted instance without keys is the right way to find out whether the combination is worth wiring up properly.
What it is
The in-house servers the Rei Network runs, bundled into one implementation. Each covers a different provider, so one connection reaches several crypto data sources.
What you get
- DeFi protocol and chain metrics
- Market data from a major price aggregator
- On-chain intelligence and entity attribution
- Social and attention signal
- A contract-address lookup by project name, with deeper querying described as still to come
Requirements
Python 3.12 and the uv package manager, plus API keys for whichever providers you intend to use. There is also a hosted option that needs no keys. MIT licensed.
Setup effort
Build from source — clone the repository, then follow the project's own run instructions
USE CASES
01
Answering a question that spans sources
Price, protocol metrics and on-chain data behind one connection.
02
Finding a token's contract
Look it up by project name.
03
Trying it without commitment
The hosted instance needs no API keys.
BEFORE YOU INSTALL
What to know first
Requires
- Python 3.12
- ARKHAM_API_KEY in your environment
- CG_API_KEY in your environment
- DEFILLAMA_API_KEY in your environment
- CODEX_API_KEY in your environment
- ELFA_API_KEY in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/0xReisearch/crypto-mcp-betaMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"arkham": {
"command": "ssh",
"args": [
"user@<YOUR_HOST>",
"cd <YOUR_PATH_TO_CRYPTO_MCP> && <YOUR_PATH_TO_UV> run arkham_server.py"
]
},
"coingecko": {
"command": "ssh",
"args": [
"user@<YOUR_HOST>",
"cd <YOUR_PATH_TO_CRYPTO_MCP> && <YOUR_PATH_TO_UV> run cg_server.py"
]
},
"defillama": {
"command": "ssh",
"args": [
"user@<YOUR_HOST>",
"cd <YOUR_PATH_TO_CRYPTO_MCP> && <YOUR_PATH_TO_UV> run defillama_server.py"
]
},
"codex": {
"command": "ssh",
"args": [
"user@<YOUR_HOST>",
"cd <YOUR_PATH_TO_CRYPTO_MCP> && <YOUR_PATH_TO_UV> run codex_server.py"
]
},
"elfa": {
"command": "ssh",
"args": [
"user@<YOUR_HOST>",
"cd <YOUR_PATH_TO_CRYPTO_MCP> && <YOUR_PATH_TO_UV> run elfa_server.py"
]
}
}
}The configuration on this page does not set ARKHAM_API_KEY, CG_API_KEY, DEFILLAMA_API_KEY, CODEX_API_KEY and ELFA_API_KEY; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
