Cerebrus Pulse MCP Server

Real-time crypto intelligence: technical analysis, sentiment, and funding rates

Local serverstdio

What is the Cerebrus Pulse MCP MCP server?

Cerebrus Pulse MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Real-time crypto intelligence: technical analysis, sentiment, and funding rates.

What you get

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.

Setting it up

Installation goes through your MCP client rather than a global install: point it at cerebrus-pulse-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Cerebrus Pulse MCP is connected, these are the calls the assistant has available:

  • cerebrus_health — Gateway health check
  • cerebrus_list_coins — List all available tickers (50+)
  • cerebrus_pulse — Multi-timeframe technicals (RSI, EMAs, BBands, VWAP, regime)
  • cerebrus_sentiment — Aggregated market sentiment + fear/greed
  • cerebrus_funding — Funding rate analysis with historical context
  • cerebrus_bundle — Pulse + sentiment + funding combined (20% discount)
  • cerebrus_screener — Scan all coins for top signals
  • cerebrus_oi — Open interest delta, percentile, trend
  • cerebrus_spread — Bid-ask spread + slippage estimates
  • cerebrus_correlation — BTC-altcoin correlation matrix
  • cerebrus_stress — Cross-chain arbitrage-derived market stress index
  • cerebrus_cex_dex — CEX vs DEX price divergence

Configuration and credentials

You will need 3 environment variables: CEREBRUS_WALLET_KEY, CEREBRUS_WALLET_KEY_SOLANA, CEREBRUS_BASE_URL. 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.

Before you rely on it

  • 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.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Cerebrus Pulse MCP.
  • 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 cerebrus pulse mcp mcp server does with a few real requests.

Choosing this one

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. Cerebrus Pulse MCP's toolset — cerebrus_health, cerebrus_list_coins, cerebrus_pulse and 11 more — is a fair guide to whether it matches your workflow. It is maintained by 0xsl1m; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cerebrus Pulse MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
cerebrus_healthGateway health check
cerebrus_list_coinsList all available tickers (50+)
cerebrus_pulseMulti-timeframe technicals (RSI, EMAs, BBands, VWAP, regime)
cerebrus_sentimentAggregated market sentiment + fear/greed
cerebrus_fundingFunding rate analysis with historical context
cerebrus_bundlePulse + sentiment + funding combined (20% discount)
cerebrus_screenerScan all coins for top signals
cerebrus_oiOpen interest delta, percentile, trend
cerebrus_spreadBid-ask spread + slippage estimates
cerebrus_correlationBTC-altcoin correlation matrix
cerebrus_stressCross-chain arbitrage-derived market stress index
cerebrus_cex_dexCEX vs DEX price divergence
cerebrus_basisChainlink oracle vs Hyperliquid basis
cerebrus_depegUSDC collateral health via Chainlink

How to install the Cerebrus Pulse MCP MCP server

{
  "mcpServers": {
    "cerebrus-pulse": {
      "command": "uvx",
      "args": ["cerebrus-pulse-mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CEREBRUS_WALLET_KEYCredential the server authenticates with.Yes
CEREBRUS_WALLET_KEY_SOLANACredential the server authenticates with.Yes
CEREBRUS_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Cerebrus Pulse MCP to cerebrus health.
  • Use Cerebrus Pulse MCP to cerebrus list coins.
  • Use Cerebrus Pulse MCP to cerebrus pulse.

Frequently asked questions

It connects Cerebrus Pulse MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (cerebrus_health, cerebrus_list_coins, cerebrus_pulse, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cerebrus Pulse MCP directly.