BRS Signals MCP Server
OfficialProvides real-time Bitcoin regime detection and market signals including convergence score, directional bias, fee histogram, funding divergence, stablecoin flows, and gamma exposure.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@BRS Signals MCP Serverwhat is the current Bitcoin market regime?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
₿RS Signals — MCP Server
mcp-name: io.github.brssignals/brs-signals-mcp
Live Bitcoin market regime for AI agents: three independent sensors read on-chain, off-chain and absence data every 30s and reject almost everything — when they converge, you get a directional call with the evidence attached. Public track record your agent can audit in one call. MCP + REST + x402. Free tier, no card.
Use it in 30 seconds — remote, no install
The public endpoint is live at https://brs-signals.com/mcp
(streamable-http · keyless free tier). Any MCP client can use it — no
package install, no local process.
Cursor (MCP requires Cursor's paid Pro tier) — Settings → Features →
MCP → + Add New MCP Server → Type http, URL https://brs-signals.com/mcp.
Or add .cursor/mcp.json:
{
"mcpServers": {
"brs-signals": { "type": "http", "url": "https://brs-signals.com/mcp" }
}
}OpenClaw — run in your terminal:
openclaw mcp add brs-signals --transport streamable-http --url https://brs-signals.com/mcp(or OpenClaw Web UI → /settings/mcp → add an HTTP/SSE endpoint at that URL)
Claude Desktop (MCP is free) — Settings → Developer → Edit Config:
{
"mcpServers": {
"brs-signals": { "type": "http", "url": "https://brs-signals.com/mcp" }
}
}Then just ask your agent: "What's the current Bitcoin regime and convergence score?"
Related MCP server: fathom-fyi
Or install locally (stdio, self-host)
pip install brs-signals-mcp
export BRS_API_KEY=va_yourkey_here # get one at https://brs-signals.com
brs-mcp # starts the MCP server (stdio)Claude Desktop (stdio) — add to
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or
%APPDATA%\Claude\claude_desktop_config.json (Windows), then restart:
{
"mcpServers": {
"brs-signals": {
"command": "brs-mcp",
"env": { "BRS_API_KEY": "va_yourkey_here" }
}
}
}Cursor (stdio) — Settings → Features → MCP → Add New MCP Server:
Type command · Command python3 -m mcp_brs · Env BRS_API_KEY.
OpenClaw (stdio):
openclaw mcp add brs-signals --command python3 --arg -m --arg mcp_brsDon't trust us — query us
The full public track record is an endpoint, not a PDF. Point your agent at it and let it reach its own conclusion:
"BRS Signals claims it rejects almost every read. Pull its public track
record (get_signal_history) and today's rejection funnel
(GET /api/v2/health/funnel), and tell me: does the data support the claim,
and what happened after each call at +4h and +24h?"What You Get
Three independent sensors running every 30 seconds, fused into one convergence score:
Sensor | Data Source | What It Detects |
X-Ray | On-chain mempool fee curves | FLAT_WIDE (accumulation) vs STEEP_TALL (panic) |
Pulse | Cross-exchange funding velocity | Squeeze probability + direction |
Shadow | Stablecoin whale flows (Tron + Solana) | Buying/selling intent before price moves |
When all three agree → conviction. When they disagree → silence.
MCP Tools
get_convergence— All three engine verdicts + convergence scoreget_directional_bias— bullish/bearish/WAIT with confidenceget_signal_history— Recent decoder decisionsget_regime_current— Market regime + active eventsget_fee_histogram— Mempool fee curve shape analysisget_funding_divergence— Cross-exchange funding squeezeget_stablecoin_flows— Whale stablecoin transfersget_gamma_exposure— Dealer gamma + flip levelget_dashboard— Bundled regime + signal + fundingget_system_health— Quick health check
Pricing
Free tier — Regime classification + convergence score (5 req/min). No card.
Pro tier ($50/mo) — Full directional bias + raw streams + unlimited requests
x402 — Agents with wallets pay per access in USDC; no signup, no human
Founding rate — Use code
FOUNDING50at checkout: $30/mo for 3 months (first 50 subscribers only)
Get your API key at brs-signals.com.
Links
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceAI-powered crypto signal intelligence for 20 assets (BTC, ETH, SOL, etc). 6 scoring dimensions: whale activity, technical analysis, derivatives flow, narrative strength, sentiment, market structure. Market regime detection (TRENDING/RANGING), portfolio optimization, and accuracy tracking. 9 read-only MCP tools. Free via MCP, $0.001 USDC via x402 on Base for REST API.2
- AlicenseAqualityDmaintenanceFinancial intelligence for AI agents. 31 tools across 8 data sources — regime, derivatives, stablecoin flows, momentum, volatility, macro, DeFi, weather patterns, political cycles, seasonality. The context layer between your agent and a bad trade.31319MIT
- AlicenseNot gradedqualityBmaintenanceClassifies BTC market into 5 regimes (Risk-On, Range-Bound, Risk-Off, Capitulation, Euphoria) with target exposure and posture, enabling risk management decisions.MIT

oneqaz-trading-mcpofficial
AlicenseNot gradedqualityDmaintenanceProvides AI agents with real-time financial market intelligence including regime detection, adaptive signals, macro context chains, and cross-market analysis for crypto, US, and Korean stocks.MIT
Related MCP Connectors
Crypto market intelligence: regime detection, funding rates, liquidations, prices, signals.
Pre-reasoned Bitcoin & macro financial briefings for AI agents. Trend signals, regimes, 17 contexts.
Crypto regime classifier for trading agents. 100% bounded regime accuracy. 50 free calls/day.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/brssignals/BRS-Signals-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server