Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/whitestone1121-web/signalbrainWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/whitestone1121-web/signalbrain/signalbrain)<a href="https://agentmods.dev/mcp/whitestone1121-web/signalbrain/signalbrain"><img src="https://agentmods.dev/badge/mcp/whitestone1121-web/signalbrain/signalbrain/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/whitestone1121-web/signalbrain/signalbrain"><img src="https://agentmods.dev/badge/mcp/whitestone1121-web/signalbrain/signalbrain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
signalbrain scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"signalbrain": {
"command": "uvx",
"args": [
"signalbrain",
"signalbrain[mcp]"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 10 lines scan A 68ee9cf55dce
signalbrain is an MCP server published in the GitHub repository whitestone1121-web/signalbrain (0 stars, last pushed 16d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
evalview-mcp
Open-source testing and regression detection framework for AI agents. Golden baseline diffing, CI/CD integration, works with LangGraph, CrewAI, OpenAI, Anthropic Claude, HuggingFace, Ollama, and MCP. Runs locally from the evalview Python package. Needs 1 environment variable to run.
o3r
Experimental package — This module provides a MCP Server. Runs locally from the @o3r/mcp npm package.
performance_profiler
MCP server "performanceprofiler" as configured in probelabs/visor. Runs ./tools/performance-analyzer.js with node. Needs 2 environment variables to run.
code_analyzer
MCP server "codeanalyzer" as configured in probelabs/visor. Runs ./mcp/analyzer.py with python3. Needs 1 environment variable to run.
security_scanner
MCP server "securityscanner" as configured in probelabs/visor. Runs ./mcp/security.js with node. Needs 2 environment variables to run.
dependency_checker
Check for outdated, incorrect, and unused dependencies. Runs locally from the npm-check npm package. Needs 1 environment variable to run.