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/rex/mcp-rancherWrote 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/rex/mcp-rancher/github)<a href="https://agentmods.dev/mcp/rex/mcp-rancher/github"><img src="https://agentmods.dev/badge/mcp/rex/mcp-rancher/github/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/rex/mcp-rancher/github"><img src="https://agentmods.dev/badge/mcp/rex/mcp-rancher/github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
github 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 1mo 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.
This is a copy
81% identical to github — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/github/github-mcp-server"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 16 lines scan A dafe1fdab762
github is an MCP server published in the GitHub repository rex/mcp-rancher (1 stars, last pushed 14d 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. It is 81% identical to github, differing in 13 lines, and is treated as a copy.
Other mcp servers, from other repositories
github
MCP server "github" as configured in rex/mcp-apple-reminders. Runs in Docker (ghcr.io/github/github-mcp-server). Needs 1 environment variable to run.
git_bash
MCP server "gitbash" as configured in code-yeongyu/oh-my-openagent. Runs ../../git-bash-mcp/dist/cli.js with node.
mcp-apple-obsidian
MCP server "mcp-apple-obsidian" as configured in rex/mcp-apple-obsidian. Runs locally from the mcp-apple-obsidian Python package.
github-ruleset-mcp
MCP server "github-ruleset-mcp" as configured in wilsonhj/github-ruleset-mcp. Runs locally from the github-ruleset-mcp npm package.
sequential-thinking
Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.