₿RS Signals — MCP Server
mcp-name: io.github.brssignals/brs-signals-mcp
Live Bitcoin market regime for AI agents: three independent sensors read pre-price data — fee curves, funding velocity, whale flows, absence — every 30s and reject almost everything. When they converge, you get a directional call with the evidence attached. The data doesn't exist in history; it exists right now and can't be reconstructed. 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?"
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_brs
Don'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
- Per-call ($0.01/query) — Pro bias, pay-as-you-go via x402 (USDC on
Solana): hit
/api/v2/bias/per-call, pay the 402, retry with?tx_signature=+ your free key. Capped at $50 per rolling 30 days, then converts to Pro — never more than $50 in any 30 days. Solana now, Base next. - 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
Metadata
Release files for brs-signals-mcp 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| brs_signals_mcp-0.1.4.tar.gz | 12.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| brs_signals_mcp-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.6 kB
Release files / brs_signals_mcp-0.1.4.tar.gz
| Download URL | brs_signals_mcp-0.1.4.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
884db95abb7fd6b773c444cc9dd157ce4b06e2e0ca1ca79c22ff5358f7fc6afa
|
|
BLAKE2b-256 checksum How to use checksums |
4b81a6391544f49986822b0cb665e4ea9744f665dd6193439e2f4f28f30921fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Release files / brs_signals_mcp-0.1.4-py3-none-any.whl
| Download URL | brs_signals_mcp-0.1.4-py3-none-any.whl |
|---|---|
| Size | 20.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46d91401008d4f86f2f5f4dd164ee82911a4f2d08735ad3d5129506a9382257f
|
|
BLAKE2b-256 checksum How to use checksums |
981b82f26b11c00ebf6c5e28e1e3889c8d63adb1793af67a7b6f12f5cbe09ac1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|