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/bvolpato/ivygrepWrote 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/bvolpato/ivygrep/ivygrep-ivygrep)<a href="https://agentmods.dev/mcp/bvolpato/ivygrep/ivygrep-ivygrep"><img src="https://agentmods.dev/badge/mcp/bvolpato/ivygrep/ivygrep-ivygrep/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/bvolpato/ivygrep/ivygrep-ivygrep"><img src="https://agentmods.dev/badge/mcp/bvolpato/ivygrep/ivygrep-ivygrep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ivygrep 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
{
"ivygrep": {
"command": "ig",
"args": [
"--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 · 8 lines scan A 904a566ae6f2
ivygrep is an MCP server published in the GitHub repository bvolpato/ivygrep (6 stars, last pushed 2d 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
octocode
AI-powered code indexer with semantic search and knowledge graphs. Runs locally from the @muvon/octocode npm package.
foremerge
MCP server "foremerge" as configured in naw103/foremerge. Launched with foremerge mcp.
codenib
A multi-view data system for serving repository context to coding agents. Runs locally from the codenib Python package.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Runs in Docker (ghcr.io/verivus-oss/sqry:4.8.16).
sverklo
MCP server "sverklo" as configured in sverklo/sverklo. Launched with /opt/homebrew/bin/sverklo .. Needs 1 environment variable to run.
devtime
Local-first Engineering Intelligence for software repositories. Runs locally from the devtime-ei Python package.