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/rozetyp/grounder-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/rozetyp/grounder-mcp/grounder)<a href="https://agentmods.dev/mcp/rozetyp/grounder-mcp/grounder"><img src="https://agentmods.dev/badge/mcp/rozetyp/grounder-mcp/grounder.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
grounder 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
{
"grounder": {
"command": "uvx",
"args": [
"grounder-mcp"
],
"env": {
"GROUNDER_API_KEY": ""
}
}
}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 · 11 lines scan A 5e598bde5586
grounder is an MCP server published in the GitHub repository rozetyp/grounder-mcp (0 stars, last pushed 25d 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
local-history
MCP server "local-history" as configured in xxczaki/local-history-mcp. Runs dist/index.js with node. Needs 1 environment variable to run.
chrome-mcp-server
MCP server "chrome-mcp-server", hosted remotely at 127.0.0.1, as configured in iloveitaly/llm-ide-rules.
stripe
Stripe's hosted MCP server: lets the agent work with customers, products, prices and payment links. Remote server at mcp.stripe.com.
greedy-token
MCP server "greedy-token" as configured in svasenkov/greedy-token. Launched with greedy-token-mcp. Needs 1 environment variable to run.
toolradar
MCP server for Toolradar — search, compare, and get pricing for 8,600+ software tools. Works with Claude Desktop, Claude Code, Cursor, and any MCP-compatible AI assistant. Runs locally from the toolradar-mcp npm package. Needs 1 environment variable to run.
qobrix-crm-mcp
MCP server "qobrix-crm-mcp" as configured in gca-ltd/qobrix-crm-mcp. Runs locally from the qobrix-crm-mcp npm package.