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/rancher-mcp)<a href="https://agentmods.dev/mcp/rex/mcp-rancher/rancher-mcp"><img src="https://agentmods.dev/badge/mcp/rex/mcp-rancher/rancher-mcp/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/rancher-mcp"><img src="https://agentmods.dev/badge/mcp/rex/mcp-rancher/rancher-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rancher-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 11d 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
{
"rancher-mcp": {
"command": "uvx",
"args": [
"rancher-mcp"
],
"env": {
"RANCHER_URL": "",
"RANCHER_TOKEN": "",
"RANCHER_VERIFY_SSL": "",
"RANCHER_INSTANCES_JSON": ""
}
}
}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.
- 11d ago First seen · 14 lines scan A fe840238c48a
rancher-mcp is an MCP server published in the GitHub repository rex/mcp-rancher (1 stars, last pushed 3d 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
mcp-k8s-ro
MCP server "mcp-k8s-ro" as configured in your-ko/mcp-k8s-ro. Runs in Docker (ghcr.io/your-ko/mcp-k8s-ro:1.2.1). Needs 1 environment variable to run.
k8s-mcp-go
MCP server "k8s-mcp-go" as configured in kaneg/k8s-mcp-go. Launched with https://github.com/kaneg/k8s-mcp-go/releases/download/v0.4.6/k8s-mcp-go_0.4.6_da.
kubernetes-readonly-mcp
A read-only Kubernetes MCP server for safely interacting with Kubernetes clusters. Runs locally from the kubernetes-readonly-mcp Python package.
ovh-api-mcp
MCP server "ovh-api-mcp" as configured in davidlandais/ovh-api-mcp. Runs in Docker (ghcr.io/davidlandais/ovh-api-mcp:0.3.0). Needs 7 environment variables to run.
mcp-k8s-ephemeral-job
MCP server "mcp-k8s-ephemeral-job" as configured in inhuman/mcp-k8s-ephemeral-job. Runs in Docker (docker.io/idconstruct/mcp-k8s-ephemeral-job:v0.7.1). Needs 18 environment variables to run.
interactive-terminal
MCP server for real interactive terminal sessions — REPLs, SSH, databases, Docker. Runs locally from the mcp-interactive-terminal npm package. Needs 3 environment variables to run.