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/ToremLabs/Proof-MCPWrote 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/toremlabs/proof-mcp/proof)<a href="https://agentmods.dev/mcp/toremlabs/proof-mcp/proof"><img src="https://agentmods.dev/badge/mcp/toremlabs/proof-mcp/proof/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/toremlabs/proof-mcp/proof"><img src="https://agentmods.dev/badge/mcp/toremlabs/proof-mcp/proof.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
proof 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 1mo 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago First seen · 10 lines scan A 8574ec02f896
proof is an MCP server published in the GitHub repository ToremLabs/Proof-MCP (0 stars, last pushed 1mo ago), licensed AGPL-3.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
diffgate
A deterministic guardrail your coding agent runs on itself — reviews only the changed lines and returns structured findings before the code reaches disk. Zero LLM tokens, 0 false blocks on a public corpus. Same engine and same verdict in your agent (MCP). Runs locally from the diffgate-review npm package.
review-assist-mcp
Turns an AI coding agent session into a reviewable Intent Document, validated against the diff. Runs locally from the review-assist-mcp npm package.
juror
MCP server "juror", hosted remotely at app.juror.dev, as configured in Juror-AI/juror.
grok-build
MCP server "grok-build" as configured in Reederey87/grok-build-codex-plugin. Launched with /bin/sh ${PLUGIN_ROOT}/mcp-server/bin/grok-build-mcp. Needs 1 environment variable to run.
dingdawg-code-review
AI code review — security, quality, performance. Learns your patterns. Receipted. Runs locally from the dingdawg-code-review npm package. Needs 1 environment variable to run.
council-ai
MCP server "council-ai", hosted remotely at mcp.council-ai.app, as configured in omarkeshk/council-review.