MCP.Market

Brs Signals MCP server

by brssignals·io.github.brssignals/brs-signals-mcp·v0.1.1·1 stars

Real-time Bitcoin regime-switch signals from three independent sensors. Free tier available.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Brs Signals yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Brs Signals tools (15, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_block_tip

    Current Bitcoin block height from mempool.space.

  • get_convergence

    Get the full Three Eyes convergence picture.

  • get_dashboard

    Get the full dashboard bundle: regime + signal + funding + suppressed signals.

  • get_directional_bias

    Get the current directional bias (bullish/bearish/WAIT) with confidence.

  • get_fee_histogram

    Get the current mempool fee curve shape and statistics.

  • get_funding_divergence

    Get cross-exchange funding rate divergence and squeeze probability.

  • get_gamma_exposure

    Get dealer gamma exposure and gamma flip level.

  • get_mempool_fees

    Live Bitcoin mempool fee rates from mempool.space.

  • get_mempool_stats

    Live mempool stats: pending tx count, total size in vbytes, total fees in BTC.

  • get_regime_current

    Get the current Bitcoin market regime with conviction.

  • get_signal_history

    Get recent decoder decisions (bullish/bearish/WAIT with ZLMA filtering).

  • get_stablecoin_flows

    Get stablecoin whale transfer flows (USDT on Tron, USDC on Solana).

  • get_system_counters

    Get live data counters: total signals fired, data points collected, days tracking.

  • get_system_health

    Quick health check of the BRS Signals system.

  • query_dbwrite action

    Run a read-only SQL query against the BRS SQLite database.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 7 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Brs Signals compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
15
the typical server has 7
Tools that change things
7%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers

What its tools let an agent do: 14 read · 1 change

Install Brs Signals in Claude Code, Cursor or VS Code

claude mcp add brs-signals-mcp -- uvx brs-signals-mcp
Add to Cursor

Brs Signals: common questions

Is Brs Signals MCP server safe?
Mostly: it is graded B (80/100). Read the Brs Signals safety report
How do I install Brs Signals?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Brs Signals need an API key?
Yes. The registry entry asks for BRS_API_KEY.
Is Brs Signals maintained?
The last commit was 48 days ago (2026-09-16). The latest release is v0.1.1.
How does Brs Signals compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 15 (the typical server has 7); tools that change things 7% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.