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/proofjson/mcp-proofjsonInstalling this writes the configuration, not the program: `mcp-proofjson` has to be on your PATH already, or the server will not start.
Wrote 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/proofjson/mcp-proofjson/mcp-proofjson)<a href="https://agentmods.dev/mcp/proofjson/mcp-proofjson/mcp-proofjson"><img src="https://agentmods.dev/badge/mcp/proofjson/mcp-proofjson/mcp-proofjson/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/proofjson/mcp-proofjson/mcp-proofjson"><img src="https://agentmods.dev/badge/mcp/proofjson/mcp-proofjson/mcp-proofjson.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-proofjson 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.
What it actually says
{
"mcp-proofjson": {
"command": "mcp-proofjson",
"args": [],
"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.
- 1mo ago First seen · 7 lines scan A fc4d96a8abfe
mcp-proofjson is an MCP server published in the GitHub repository proofjson/mcp-proofjson (0 stars, last pushed 4mo 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-31.
Other mcp servers, from other repositories
andru-intelligence
28 signed tools for founders + PE/VC operators: ICP scoring, deal classification, market signals. Runs locally from the mcp-server-andru-intelligence npm package. Needs 2 environment variables to run.
hs-audit-app
MCP server "hs-audit-app", hosted remotely at hs-audit-app.oga-surf-project.workers.dev, as configured in ogasurfproject-jpg/horizon-shield.
horizon-shield
MCP server "horizon-shield", hosted remotely at mcp.horizonshield.dev, as configured in ogasurfproject-jpg/horizon-shield.
horizon-shield-webmcp
Agent intake desk for property renovation. Read only, CORS open, fail closed, receipts recompute. Remote server at web.horizonshield.dev.
hs-hearing
Neutral, verification-gated MCP directory of Japan construction contractors (KIRA-audited). Remote server at hearing.horizonshield.dev.
hs-verify-gate
Conformance checker for MCP servers. Free, no key, verdicts recomputable and re-measured daily. Remote server at gate.horizonshield.dev.