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.
npx agentmods add mcp/hyperion-gpu/proofflow-v0.1/proofflowgit clone --depth 1 https://github.com/Hyperion-GPU/ProofFlow-v0.1Wrote 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/hyperion-gpu/proofflow-v0.1/proofflow)<a href="https://agentmods.dev/mcp/hyperion-gpu/proofflow-v0.1/proofflow"><img src="https://agentmods.dev/badge/mcp/hyperion-gpu/proofflow-v0.1/proofflow.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
proofflow 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 4d 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
{
"proofflow": {
"command": "proofflow-mcp",
"env": {
"PROOFFLOW_BASE_URL": "http://127.0.0.1:8787"
}
}
}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.
- 4d ago First seen · 8 lines scan A 06f9f692225c
proofflow is an MCP server published in the GitHub repository Hyperion-GPU/ProofFlow-v0.1 (48 stars, last pushed 27d ago), licensed MIT. 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-30.
Other mcp servers, from other repositories
mcp-rampart
Security toolkit for FastAPI-based MCP servers — pre-flight audit + runtime prompt-injection guardrail. Runs locally from the mcp-rampart Python package.
cloud-audit
Open-source, read-only AWS security scanner. 110 checks across 25 services, 31 attack-chain rules, 64 IAM escalation methods (incl. lateral AssumeRole graph), Proof Mode exploitability verification, data perimeter and Bedrock AgentCore checks, Blast Radius CLI, Threat Feed, What-If simulator, AI-SPM, 6 compliance…
krait-solodit
MCP server "krait-solodit" as configured in ZealynxSecurity/krait. Runs mcp-servers/solodit/build/index.js with node.
pseolint
Penalty-risk audit for programmatic SEO sites: verdict, risk score, and a fix manifest. Runs locally from the @pseolint/mcp npm package. Needs 2 environment variables to run.
warrant
Verify what an AI agent decided — signed, hash-addressed decision records with reasons you can re-run on your own machine. Runs locally from the warrant-verify Python package. Needs 3 environment variables to run.
verifiable-agent-audit-trail
Tamper-evident records of AI agent decisions. Verify offline, or publish a proof link. Runs locally from the @darkmatterhub/mcp-server npm package. Needs 4 environment variables to run.