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/VerificateAI/verificate-mcp-quickstartWrote 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/verificateai/verificate-mcp-quickstart/verificate)<a href="https://agentmods.dev/mcp/verificateai/verificate-mcp-quickstart/verificate"><img src="https://agentmods.dev/badge/mcp/verificateai/verificate-mcp-quickstart/verificate.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
verificate 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 7d 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
{
"verificate": {
"type": "http",
"url": "https://mcp.verificate.ai/mcp",
"headers": {
"Authorization": "Bearer ${VERIFICATE_TOKEN}"
}
}
}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.
- 7d ago First seen · 9 lines scan A 57a9ec0f7928
verificate is an MCP server published in the GitHub repository VerificateAI/verificate-mcp-quickstart (1 stars, last pushed 15d 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
norma
Deterministic AI code review, with an audit record. Governance inside the agent loop. Remote server at api.qualityclouds.ai.
juror
MCP server "juror", hosted remotely at app.juror.dev, as configured in Juror-AI/juror.
codesentinel-mcp
Codebase health MCP: dead code, cycles, coupling, architectural drift. Runs locally from the @cubiczan/codesentinel-mcp npm package.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package.
umbra
Trust score for AI-generated code: scan repos, guard agent file writes, get a 0-100 score. Runs locally from the @elberacasa/umbra 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.