About Cerebrus Pulse
Cerebrus Pulse is an MCP server for AI agents seeking real-time crypto analysis across 50+ Hyperliquid perpetuals. Its tools cover technical indicators, sentiment, funding rates, and liquidation data; paid endpoints use x402 micropayments.
Key features
- 01Coverage of 50+ perpetuals
- 02Multi-timeframe technical analysis
- 03Sentiment and fear-and-greed data
- 04Funding rate and open interest analysis
- 05Liquidation heatmaps and market stress
Use cases
- 01Screen perpetuals for market signals
- 02Review funding rates and sentiment
- 03Inspect liquidation zones across leverage tiers
MCP support
The MCP server exposes 15 crypto-market data tools. Some paid endpoints use x402 USDC micropayments, while free tools work without configuration.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMECerebrus Pulse MCP
mcp-name: io.github.0xsl1m/cerebrus-pulse-mcp
MCP server for Cerebrus Pulse — real-time crypto intelligence for AI agents. Provides 15 tools covering technical analysis, liquidation heatmaps, market stress, funding rates, and more across 50+ Hyperliquid perpetuals.
Tools
| Tool | Description | Cost |
|---|---|---|
cerebrus_health | Gateway health check | Free |
cerebrus_list_coins | List all available tickers (50+) | Free |
cerebrus_pulse | Multi-timeframe technicals (RSI, EMAs, BBands, VWAP, regime) | $0.025 |
cerebrus_sentiment | Aggregated market sentiment + fear/greed | $0.01 |
cerebrus_funding | Funding rate analysis with historical context | $0.01 |
cerebrus_bundle | Pulse + sentiment + funding combined | $0.05 |
cerebrus_screener | Scan all coins for top signals | $0.06 |
cerebrus_oi | Open interest delta, percentile, trend | $0.015 |
cerebrus_spread | Bid-ask spread + slippage estimates | $0.015 |
cerebrus_correlation | BTC-altcoin correlation matrix | $0.05 |
cerebrus_stress | Cross-chain arbitrage-derived market stress index | $0.02 |
cerebrus_cex_dex | CEX vs DEX price divergence | $0.02 |
cerebrus_basis | Chainlink oracle vs Hyperliquid basis | $0.02 |
cerebrus_depeg | USDC collateral health via Chainlink | $0.01 |
cerebrus_liquidations | Liquidation heatmap across 5 leverage tiers | $0.03 |
Paid endpoints use x402 micropayments (USDC on Base or Solana). Free tools work without any configuration.
Prices are checked against the API's live x402 manifest
(https://api.cerebruspulse.xyz/.well-known/x402) with
python scripts/check_prices.py --live, which CI runs. The auto-pay payee pin
is checked against a live 402 with python scripts/check_payto.py --live,
which CI and the release workflow run.
Install
Claude Desktop / Cursor / Windsurf
Add to your MCP config (claude_desktop_config.json, .cursor/mcp.json, etc.):
{
"mcpServers": {
"cerebrus-pulse": {
"command": "uvx",
"args": ["cerebrus-pulse-mcp"]
}
}
}
To enable automatic x402 payments for paid endpoints, add a wallet key. The
x402 client ships with the package, so the same uvx command pays; there is no
extra to install:
{
"mcpServers": {
"cerebrus-pulse": {
"command": "uvx",
"args": ["cerebrus-pulse-mcp"],
"env": {
"CEREBRUS_WALLET_KEY": "your-base-wallet-private-key",
"CEREBRUS_WALLET_KEY_SOLANA": "your-solana-wallet-private-key"
}
}
}
}
Automatic payment currently covers Base only. CEREBRUS_WALLET_KEY_SOLANA
is reserved for a future Solana signer — the API accepts Solana today, but you
would need to settle those payments yourself.
Use a dedicated hot wallet that holds a few dollars of USDC on Base, never a main wallet: the key sits in plain text in the MCP config.
Auto-payment has spend limits, checked before anything is signed:
- no single payment above
CEREBRUS_MAX_PAYMENT_USD(default0.10; the priciest tool costs $0.06); - no more than
CEREBRUS_MAX_SPEND_USDin total while the server process runs (default1.00; restart the server to reset it). The--jsonCLI starts a new process on every call, so this budget cannot span CLI calls, and the CLI does not auto-pay unless you opt in (see CLI Usage); - only USDC on Base, and only to an address in
CEREBRUS_ALLOWED_PAYTO(default: the published Cerebrus Pulse Base address), so a hijacked or mistypedCEREBRUS_BASE_URLcannot redirect payments.
A refused payment returns "status": "payment_blocked" with the reason; a
malformed limit disables auto-payment rather than lifting the limit.
Without a wallet key, paid tools still work as discovery: they return the exact price, network, and recipient so the calling agent can pay however it likes.
pip
pip install cerebrus-pulse-mcp
CLI Usage
The server includes a --json flag for direct CLI access without an MCP client:
# List all available CLI tools
cerebrus-pulse-mcp --json
# Free endpoints
cerebrus-pulse-mcp --json health
cerebrus-pulse-mcp --json list-coins
# Paid endpoints (return the payment terms unless CLI auto-pay is on, below)
cerebrus-pulse-mcp --json pulse BTC
cerebrus-pulse-mcp --json funding ETH lookback_hours=48
cerebrus-pulse-mcp --json screener top_n=10
cerebrus-pulse-mcp --json liquidations SOL
Arguments can be passed positionally (for coin) or as key=value pairs.
The CLI does not auto-pay by default, even with CEREBRUS_WALLET_KEY set.
Every call is a new process with a fresh CEREBRUS_MAX_SPEND_USD budget, so
the budget cannot stop a script that runs the CLI in a loop. Set
CEREBRUS_CLI_AUTOPAY=1 to let it pay anyway: each call may then sign one
payment of up to CEREBRUS_MAX_PAYMENT_USD, and limiting how many calls run
is up to your script.
Configuration
| Environment Variable | Description | Required |
|---|---|---|
CEREBRUS_BASE_URL | API base URL (default: https://api.cerebruspulse.xyz) | No |
CEREBRUS_WALLET_KEY | Base wallet private key for x402 auto-payment | No |
CEREBRUS_MAX_PAYMENT_USD | Largest single payment auto-pay may sign (default: 0.10) | No |
CEREBRUS_MAX_SPEND_USD | Total auto-pay may sign per server process (default: 1.00); does not span --json CLI calls | No |
CEREBRUS_CLI_AUTOPAY | Set to 1 to let the --json CLI auto-pay (default: off, because the budget resets on every CLI call) | No |
CEREBRUS_ALLOWED_PAYTO | Comma-separated payTo addresses auto-pay may pay (default: the published Cerebrus Pulse Base address) | No |
CEREBRUS_WALLET_KEY_SOLANA | Reserved; Solana auto-payment not yet implemented | No |
Example Response
$ cerebrus-pulse-mcp --json health
{
"status": "ok",
"engine": "available",
"kill_switch": "enabled",
"version": "1.2.0"
}
Development
git clone https://github.com/0xsl1m/cerebrus-pulse-mcp.git
cd cerebrus-pulse-mcp
pip install -e .
Links
- Cerebrus Pulse — API documentation and guides
- x402 Protocol — HTTP 402 micropayment standard
- PyPI Package
- Changelog
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.