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/Juror-AI/jurorWrote 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/juror-ai/juror/juror-juror)<a href="https://agentmods.dev/mcp/juror-ai/juror/juror-juror"><img src="https://agentmods.dev/badge/mcp/juror-ai/juror/juror-juror/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/juror-ai/juror/juror-juror"><img src="https://agentmods.dev/badge/mcp/juror-ai/juror/juror-juror.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
juror 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 12d 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
{
"juror": {
"type": "http",
"url": "https://app.juror.dev/mcp"
}
}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.
- 12d ago First seen · 6 lines scan A 7ae21ddcef28
juror is an MCP server published in the GitHub repository Juror-AI/juror (123 stars, last pushed yesterday), 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
argot
Flags code foreign to your repo's patterns, learned from git history. Local; statistics, no LLM. Runs locally from the @tmonier/argot npm package.
norma
Deterministic AI code review, with an audit record. Governance inside the agent loop. Remote server at api.qualityclouds.ai.
cejel
MCP server "cejel" as configured in BargLabs/cejel. Runs in Docker (ghcr.io/barglabs/cejel@sha256:f1cd2356cc0072ad08e24fcddc379206ee07f5699b9a633164326917f665b6d6).
build-quality-agent
Claude-powered git pre-push diff reviewer for indie OSS projects. Runs locally from the build-quality-agent Python package.
ovecc
Architecture guardrails for AI-written code: dependency graph, impact, dead code, CI gate. Runs locally from the ovecc 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.