Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SignalBrain

PYPI · SIGNALBRAIN

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

Available components

−84 this week 0 Trust /100

Last scanned (6 days ago)

Scores higher than 0% of PyPI servers

Category CI/CD and DevOps

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • No malware found by supply-chain analysis.Pass
  • Known CVEs could not be checked: we could not find this package in its registry.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency0
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 29 Oct 26 −17
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 −17
    • Malware scan: pass → unverified ▼ security
  • 27 Oct 26 −16
    • Tool safety: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 26 Oct 26 −17
    • Stability: 0.97 → pass security
  • 25 Oct 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 24 Oct 26 0
    • Known CVEs: pass → unverified ▼ security
    • Install scripts: pass → unverified ▼ security
    • Provenance: pass → fail ▼ security
    • The code this package runs automatically changed: its declared build backend security
    • The attested source repository moved: whitestone1121-web/signalbrain security
    • Dependency health: pass → unverified ▼ functional
    • License: pass → fail ▼ functional
    • Maintenance: pass → fail ▼ functional
    • Licence: Apache-2.0 functional
  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Oct 2026 · Analysed pypi/signalbrain@0.1.6

Provenance Package not found

The registry answered that no such package exists, so no provenance could be looked up.

Result Package not found
Ecosystem pypi
Reason Metadata unavailable

Background: How many MCP packages publish verified provenance →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

How do I install the SignalBrain MCP server?

SignalBrain runs locally as a PyPI package, launched with uvx signalbrain. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · signalbrain

# add to Claude Code
claude mcp add whitestone1121-web-signalbrain -- uvx signalbrain
Common questions

What is the SignalBrain MCP server?

SignalBrain is an MCP server listed in the public MCP registry as io.github.whitestone1121-web/signalbrain. Verifiable receipts for governed process changes; emit, validate, and gate trust. This page covers its PyPI package (signalbrain).

Is the SignalBrain MCP server safe to use?

SignalBrain scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the SignalBrain MCP server still maintained?

SignalBrain has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.