Brs Signals Mcp

io.github.brssignalsPublished by GitHub account brssignalsv0.1.1Updated Oct 24, 2026

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

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local MCP server that gives an assistant real-time Bitcoin regime-switch signals drawn from three independent sensors.

What you can do
  • Retrieve real-time Bitcoin regime-switch signals from the BRS Signals service.
  • Work with signals derived from three independent sensors.
  • No tool list is published, so the exact operations are not documented; the description only covers signal retrieval and a free tier.
When to use it
Useful when you want an assistant to pull current Bitcoin market-regime signals into a conversation or analysis, for example to check whether conditions have shifted. It is not a general market-data or trading server.
Requirements
Runs as a local process installed from the PyPI package brs-signals-mcp over stdio, so a Python environment is needed. Requires a BRS Signals API key supplied through the BRS_API_KEY environment variable; keys are obtained from the provider's site. A free tier is mentioned.
Before you install
The server needs an API key (BRS_API_KEY) that is passed as an environment variable, so keep it out of shared configs and logs. Signals are informational market indicators, not investment advice, and the free tier may have limits. No tool list is published, so review what it can do before granting access.

Installation

In SourceWeft

  1. Open Brs Signals Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Signals integrations