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/madrzak/rankgoat-cliWrote 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/madrzak/rankgoat-cli/rankgoat)<a href="https://agentmods.dev/mcp/madrzak/rankgoat-cli/rankgoat"><img src="https://agentmods.dev/badge/mcp/madrzak/rankgoat-cli/rankgoat/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/madrzak/rankgoat-cli/rankgoat"><img src="https://agentmods.dev/badge/mcp/madrzak/rankgoat-cli/rankgoat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rankgoat 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 9d 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
{
"rankgoat": {
"command": "npx",
"args": [
"-y",
"rankgoat",
"-y",
"rankgoat",
"mcp"
],
"env": {
"RANKGOAT_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.
- 9d ago First seen · 15 lines scan A 78421527a548
rankgoat is an MCP server published in the GitHub repository madrzak/rankgoat-cli (0 stars, last pushed 1mo 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
squirrelscan
MCP server "squirrelscan", hosted remotely at mcp.squirrelscan.com, as configured in squirrelscan/squirrelscan.
carto
MCP server "carto" as configured in theanshsonkar/carto. Launched with carto serve.
svelte
MCP server "svelte", hosted remotely at mcp.svelte.dev, as configured in oekazuma/svelte-vitals.
tierward
Read a Tierward project's governance state (doctor, team-settings, arch-audit, skills) over MCP. Runs locally from the tierward npm package.
workspaceguard
Per-workspace usage metering and fail-closed quota caps for shared self-hosted AI assistant deployments (Odysseus and compatible backends). Genuine independent Python port with the same CLI and --json shapes as the npm package. Runs locally from the workspaceguard-cli Python package.
seo-mcp
MCP server for Ahrefs free-tool data: backlinks, keyword research, keyword difficulty, and traffic estimation. Runs locally from the @qexle/seo-mcp npm package.