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/dmytrome/groundhogWrote 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/dmytrome/groundhog/groundhog-mcp)<a href="https://agentmods.dev/mcp/dmytrome/groundhog/groundhog-mcp"><img src="https://agentmods.dev/badge/mcp/dmytrome/groundhog/groundhog-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
groundhog-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 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
{
"groundhog-mcp": {
"command": "uvx",
"args": [
"groundhog-mcp"
],
"env": {}
}
}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 3d55e8a8d3b2
groundhog-mcp is an MCP server published in the GitHub repository dmytrome/groundhog (0 stars, last pushed today), 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
web-fetcher
MCP server "web-fetcher" as configured in akanthed/SecureAI-Scan. Runs locally from the some-mcp-fetch-server npm package. Needs 1 environment variable to run.
devharness
MCP server that connects AI assistants to Chrome DevTools Protocol for runtime debugging - set breakpoints, inspect variables, monitor network traffic, and automate browser interactions. Runs locally from the devharness npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
browser-use
Make websites accessible for AI agents. Runs locally from the browser-use Python package.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
playwright
MCP server "playwright" as configured in langwatch/langwatch. Launched with bash -c d=$PWD; while [ "$d" != / ] && [ ! -f "$d/dev/scripts/playwright-mcp.sh".