SignalBrain

io.github.whitestone1121-webPublished by GitHub account whitestone1121-webv0.1.6Updated Oct 24, 2026

Verifiable receipts for governed process changes; emit, validate, and gate trust

The publisher's own server: BrainDog

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant emit, validate, and gate signed receipts for governed process changes, so autonomy is earned by re-runnable evidence.

What you can do
SignalBrain exposes three MCP tools: emit_receipt, validate_receipt, and gate_status. The agent writes spec-compliant claims about a change, checks that a receipt exists byte-for-byte on the merged ref, and reads its own earned-autonomy standing per change class. The underlying CLI re-runs a receipt's own measurement commands and turns the ledger into TRUST/GATE or per-class ELIGIBLE/GATE decisions.
When to use it
Use it when autonomous coding agents change systems that matter and you want a verifiable record of what was claimed and whether it held. It suits teams that want to move past approving every action forever and instead let a process earn reduced review per change class.
Requirements
Runs locally over stdio as a PyPI package, started with uvx --from "signalbrain[mcp]" sb-mcp. Python and uvx are needed. No authentication, environment variables, or headers are declared; the README states plain files, a CLI, and a GitHub Action, with nothing to host and nothing phoning home.
Before you install
The project is 0.x alpha software; pin exact versions and expect breaking changes before 1.0. It verifies claim integrity, not total system correctness, and does not detect GPU or kernel faults, data poisoning, prompt injection, or production execution breaches unless you wire the CLI exit codes into your deploy, CI, scheduler, or circuit breaker. Scoring re-runs commands from receipts, so only score receipts you trust.

Installation

In SourceWeft

  1. Open SignalBrain 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.6LatestSep 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 Brain integrations