brs-signals

endpoint

https://brs-signals.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is brs-signals live?

Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.

Is brs-signals free to use?

Yes — the hub reached it with no key and no payment.

What tools does brs-signals have?

5 tools: brs_decision_context, brs_market_state, brs_audit_track_record, brs_rejection_funnel, brs_system_status.

Is brs-signals safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• brs_market_state reads open 3h ago

  Canonical current market posture. Call this FIRST. Bundles the three public, keyless reads into one call: - regime structure (which game the market is playing) - three-eye convergence (how much the sensors agree) - system health (whether the instrument is operational) Returns market_structure, convergence, and system_health together with their as_of timestamps. If any read is stale or a sensor is down, that changes what every other answer means — check health before trusting a directional read. Free tier, no API key required.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "brs_market_stateArguments",
    "properties": {}
  }

  arguments 5 lines copy
• brs_audit_track_record reads open 10h ago

  The public proof: every call BRS has made and what Bitcoin did next. Returns the keyless track record — each entry carries timestamp, side (bullish/bearish), price at call time, confidence, regime, zone, and resolved +4h/+24h outcomes where the paper-trading log has them (return %, worst drawdown, best upside). Outcomes are fixed once written and never re-scored, so this is auditable evidence, not marketing. This is the "don't trust us — query us" surface: no API key and no payment are required. Use it to verify the system's real silence before trusting any signal. Args: limit: Number of recent calls to return (1–500, default 100).

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "brs_audit_track_recordArguments",
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 100,
        "maximum": 500,
        "minimum": 1
      }
    }
  }

  arguments 13 lines copy
• brs_rejection_funnel reads open 10h ago

  Why no signal? The pipeline funnel in one glance (public). Every cycle that does not become a signal died at a specific gate. This returns the cycle count at each gate in order, so an agent can draw a survival funnel and see where reads are rejected — the direct answer to "BRS rejects almost everything, prove it." Args: day: A specific UTC day (YYYY-MM-DD). Empty = today. days: Sum over the last N UTC days (e.g. 30). Ignored if day set. since: "launch" for every day on record, or a YYYY-MM-DD start date. Returns: cycles_total, emitted, signals_sent, per-gate counts, gate_order.

  mcp-tool

  1234567891011121314151617181920212223

  {
    "type": "object",
    "title": "brs_rejection_funnelArguments",
    "properties": {
      "day": {
        "type": "string",
        "title": "Day",
        "default": ""
      },
      "days": {
        "type": "integer",
        "title": "Days",
        "default": 0,
        "maximum": 365,
        "minimum": 0
      },
      "since": {
        "type": "string",
        "title": "Since",
        "default": ""
      }
    }
  }

  arguments 23 lines copy
• brs_system_status reads open 10h ago

  Instrument health, SLO standing, and the sample size behind every reading (free). Bundles two keyless reads plus a measured SLO block: - component health: collector/engine status and last-good timestamps - system counters: signals sent, data points collected, days collecting. "Signals sent" is the authoritative all-time count from decoder_decision_records — the same figure the funnel and the landing page show, so every surface agrees. - slo: status; CONFIGURED (compliance_pct + scope note) vs MEASURED (uptime_24h_pct, boot-epoch uptime, latency_ms) kept apart; an observation_window discloses the 24h coverage and flags insufficient history explicitly. compliance_pct scope is "registry metadata checks" only (see compliance_note) — NOT protocol conformance (BRS-021f: this server serves 2026-07-28 modern + legacy ≤ 2025-11-25) and NOT operational health (the measured fields above) Call this when any reading looks stale or absent, and to see exactly how small the sample behind a claim is. Small samples cannot prove an edge.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "brs_system_statusArguments",
    "properties": {}
  }

  arguments 5 lines copy
• brs_decision_context moves money unknown 3h ago

  Directional market context with evidence and caveats (Pro tier). Returns the current posture (bullish / bearish / WAIT) with the regime and zone it was read in, the reason, confidence, btc_price and timestamp. WAIT is the most common answer and means no edge is visible — it is context, not an instruction. Confidence is normalised against how much evidence was reachable: sent signals typically land 0.30–0.50, so compare against that distribution, not 1.0. Suppressed reads are shown (suppressed=true), never hidden. Payment (BRS-017): this is the metered Pro posture and is payable per-call via x402. Call it with no tx_signature first — if the result is status='error' with error.code='PAYMENT_REQUIRED', inspect error.payment: that carries the exact amount, currency, asset, networks, recipient, expiry and request_digest needed to build the settlement. Pay on an advertised rail, then re-call with the tx_signature (and matching chain/ref) to get the metered result. Retries are idempotent — the same tx_signature is never charged twice. A Pro key (BRS_API_KEY or a per-client key) skips payment entirely. Spend caps: max 3 re-calls per request; enforce your own max-per-call/max-per-day policy against error.payment before paying. Args: tx_signature: The signed x402 settlement tx from a prior payment. Empty on first call (you will receive the challenge instead). chain: Rail you paid on — "solana" or "base". Default "solana". ref: Optional attribution tag carried through to the payment ledger.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "title": "brs_decision_contextArguments",
    "properties": {
      "ref": {
        "type": "string",
        "title": "Ref",
        "default": ""
      },
      "chain": {
        "type": "string",
        "title": "Chain",
        "default": "solana"
      },
      "tx_signature": {
        "type": "string",
        "title": "Tx Signature",
        "default": ""
      }
    }
  }

  arguments 21 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.