Mcp For Argocd
Repository: mcp-for-argocd
Author: argoproj-labs · Source status: Clear source
An implementation of Model Context Protocol (MCP) server for Argo CD.
Score basis:Clear source · Low risk signals · Universal
Compare skills
Pick 2–4 skills and compare what really matters: fit, risk, install effort, and community signal.
Comparison matrix
Highlights show current best; tooltip explains diff/best rules.
SAS-v2.1 diff rules / risk tag notes
Start with the matrix. Open this section when you need to understand audit grades, top threats, control gaps, and best-value highlights.
Suggested baseline
Search to add skills, or paste 2–4 comma-separated slugs.
How differences are detected
A row is marked different when selected skills have distinct values. Only-differences mode hides rows that are identical.
How best values are highlighted
Audit score, evidence confidence, trust score, and community signal prefer higher values; execution risk and install friction prefer lower values.
How to read risk tags
Risk tags come from SAS-v2.1 public-evidence signals and point to command, network, secret, context, or supply-chain items to review before install.
Selected audit signals
mcp-ssh-manager
Execution risk:High
Threat tags:unexpected code execution, data exfiltration, human approval gap
Control gaps:missing license, broad permissions, shell without guardrails
mcpcan
Execution risk:High
Threat tags:unexpected code execution, identity privilege abuse, data exfiltration
Control gaps:missing license, broad permissions, shell without guardrails
certctl
Execution risk:High
Threat tags:unexpected code execution, identity privilege abuse, data exfiltration
Control gaps:missing license, broad permissions, shell without guardrails
| Dimension | mcp-ssh-manager | mcpcan | certctl |
|---|---|---|---|
| SAS-v2.1 pre-install audit | |||
Threat tags | unexpected code execution, data exfiltration, human approval gap | unexpected code execution, identity privilege abuse, data exfiltration | unexpected code execution, identity privilege abuse, data exfiltration |
Permission summary | Permission review, Network, Command | Permission review, Network, Secrets, Command | Permission review, Network, Secrets, Command |
Evidence confidence | 65% | 67% | 67% |
| Source & provenance | |||
Provenance | bvisible/mcp-ssh-manager | Kymo-MCP/mcpcan | shankar0123/certctl |
Freshness | 2026-04-07 | 2026-04-03 | 2026-04-08 |
| Risk & trust | |||
Trust score | 79 | 81 | 79 |
Audit signals | No explicit signals | needs credentials, network access | network access |
| Install & compatibility | |||
Install friction | 40 | 55 | 40 |
| Community | |||
Stars | 137 | 717 | 286 |
Repository: coolify-mcp
Author: StuMason · Source status: Clear source
MCP server for Coolify — 38 optimized tools for managing self-hosted PaaS through AI assistants Topics: ai, claude, coolify, deployment, devops, infrastructure, mcp, model-context-protocol, paas, self-hosted, typescript.
Score basis:Clear source · Low risk signals · Universal
Repository: claude-code
Author: anthropics · Source status: Clear source
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT}
Score basis:Clear source · High risk signals · Claude