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/Project-Navi/grippy-code-reviewWrote 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/project-navi/grippy-code-review/grippy-mcp)<a href="https://agentmods.dev/mcp/project-navi/grippy-code-review/grippy-mcp"><img src="https://agentmods.dev/badge/mcp/project-navi/grippy-code-review/grippy-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/project-navi/grippy-code-review/grippy-mcp"><img src="https://agentmods.dev/badge/mcp/project-navi/grippy-code-review/grippy-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grippy-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 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
{
"grippy-mcp": {
"command": "uvx",
"args": [
"grippy-mcp"
],
"env": {
"GRIPPY_TRANSPORT": "local",
"GRIPPY_PROFILE": "security",
"OPENAI_API_KEY": "",
"ANTHROPIC_API_KEY": "",
"GOOGLE_API_KEY": "",
"GROQ_API_KEY": "",
"MISTRAL_API_KEY": "",
"GRIPPY_BASE_URL": "http://localhost:1234/v1",
"GRIPPY_MODEL_ID": "devstral-small-2-24b-instruct-2512"
}
}
}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 · 19 lines scan A d0b0f539add5
grippy-mcp is an MCP server published in the GitHub repository Project-Navi/grippy-code-review (4 stars, last pushed 2mo 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.
coderegistry
Enterprise code intelligence for M&A, security audits, and tech debt. Hosted server with 200k free. Remote server at integrator.app.thecoderegistry.com.
ovecc
Architecture guardrails for AI-written code: dependency graph, impact, dead code, CI gate. Runs locally from the ovecc npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm run start-stdio.