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/qualityclouds/norma-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/qualityclouds/norma-mcp/norma)<a href="https://agentmods.dev/mcp/qualityclouds/norma-mcp/norma"><img src="https://agentmods.dev/badge/mcp/qualityclouds/norma-mcp/norma/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/qualityclouds/norma-mcp/norma"><img src="https://agentmods.dev/badge/mcp/qualityclouds/norma-mcp/norma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
norma 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
{
"norma": {
"url": "https://api.qualityclouds.ai/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A 4fbfe8a41a67
norma is an MCP server published in the GitHub repository qualityclouds/norma-mcp (5 stars, last pushed 12d 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
juror
MCP server "juror", hosted remotely at app.juror.dev, as configured in Juror-AI/juror.
verificate
MCP server "verificate", hosted remotely at mcp.verificate.ai, as configured in VerificateAI/verificate-mcp-quickstart.
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.
mcp-code-sanitizer
Strict AI code reviewer MCP server powered by Groq — finds bugs, vulnerabilities and security issues. Runs locally from the mcp-code-sanitizer Python package. Needs 1 environment variable to run.
forgecraft
CLI + MCP sentinel for engineering standards — SOLID, testing, architecture, CI/CD — auto-tailored to your stack. Minimal MCP footprint (200 tokens) via CLI-first design. Runs locally from the forgecraft-mcp npm package.
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.