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/argoproj-labs/mcp-for-argocdWrote 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/argoproj-labs/mcp-for-argocd/argocd-mcp)<a href="https://agentmods.dev/mcp/argoproj-labs/mcp-for-argocd/argocd-mcp"><img src="https://agentmods.dev/badge/mcp/argoproj-labs/mcp-for-argocd/argocd-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/argoproj-labs/mcp-for-argocd/argocd-mcp"><img src="https://agentmods.dev/badge/mcp/argoproj-labs/mcp-for-argocd/argocd-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
argocd-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 2d 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
{
"argocd-mcp": {
"command": "npx",
"args": [
"argocd-mcp@latest",
"stdio"
],
"env": {
"NODE_TLS_REJECT_UNAUTHORIZED": "0",
"ARGOCD_BASE_URL": "<argocd_url>",
"ARGOCD_API_TOKEN": "<argocd_token>"
}
}
}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.
- 2d ago First seen · 14 lines scan A 5f621bc14bee
argocd-mcp is an MCP server published in the GitHub repository argoproj-labs/mcp-for-argocd (587 stars, last pushed yesterday), licensed Apache-2.0. 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-10-15.
Other mcp servers, from other repositories
argocd-mcp-server
MCP server for ArgoCD GitOps continuous delivery integration. Runs locally from the argocd-mcp-server Python package.
radar
MCP server "radar" as configured in skyhook-io/radar. Runs in Docker (ghcr.io/skyhook-io/radar:1.9.2).
mcp
DevCycle MCP server for feature flag management. Remote server at mcp.devcycle.com.
devops-mcp
Unified MCP server for Kubernetes, ArgoCD, Prometheus, PagerDuty, and Loki. Runs locally from the @notharshhaa/devops-mcp npm package. Needs 9 environment variables to run.
spinnaker-mcp
MCP server exposing Spinnaker CD platform via Gate API for pipeline and deployment management. Runs locally from the spinnaker-mcp npm package. Needs 4 environment variables to run.
release-readiness-triage-mcp
Aggregates CI failures, cross-references flakiness history, and outputs GO/NOGO release verdicts. Runs locally from the release-readiness-triage-mcp npm package.