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/ravnlab/review-gate-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/ravnlab/review-gate-mcp/review-gate-mcp)<a href="https://agentmods.dev/mcp/ravnlab/review-gate-mcp/review-gate-mcp"><img src="https://agentmods.dev/badge/mcp/ravnlab/review-gate-mcp/review-gate-mcp/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/ravnlab/review-gate-mcp/review-gate-mcp"><img src="https://agentmods.dev/badge/mcp/ravnlab/review-gate-mcp/review-gate-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
review-gate-mcp 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
{ "review-gate-mcp": { "command": "npx", "args": [ "-y", "review-gate-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.
- 1mo ago First seen · 9 lines scan A a28f7f5730b0
review-gate-mcp is an MCP server published in the GitHub repository ravnlab/review-gate-mcp (0 stars, last pushed 3mo 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
ax-platform
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client. Remote server at paxai.app.
elicitly-free-dev
MCP server "elicitly-free-dev" as configured in elicitly/elicitly. Runs packages/elicitly/dist/cli.mjs with node.
elicitly-free
Local (stdio) MCP server that gives your prompts and Agent Skills MCP elicitation — human-in-the-loop dialogs (elicitconfirm, elicitform) and the elicitdoctor capability report, with no server of your own. Runs locally from the elicitly npm package.
ebb-ai
Model Context Protocol server for ebb-ai — carbon-aware scheduling tools for any MCP-compatible agent. Runs locally from the @ebb-ai/mcp npm package.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.
thalovant-mcp
Connect MCP clients to Thalovant control-plane and hub runtime APIs over stdio or Streamable HTTP. Runs locally from the @thalovant/mcp-server npm package.