devops_explain_change

2 registry entries were observed exposing a tool named devops_explain_change — none of them flagged as a privileged capability.

Spelled devops_explain_change, devops__explain_change in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,174 of 40,560 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. @notharshhaa/devops-mcpMCPcommunitytrust 60/100 · B
    v2.1.1
    ↓ 285/wk
    ★ 4

    Unified MCP server for DevOps engineers — query and manage Kubernetes, ArgoCD, Prometheus, and PagerDuty from any MCP-compatible AI agent.

    ClaudeCursorCopilotGemini
    DevOps MCP ContributorsMIT6d agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolkubernetesargocdprometheuspagerduty
  2. io.github.NotHarshhaa/devops-mcpMCPcommunitytrust 60/100 · B
    v2.1.0
    ★ 3

    Unified MCP server for Kubernetes, ArgoCD, Prometheus, PagerDuty, and Loki

    ClaudeCursorCopilotGemini
    io.github.NotHarshhaaUnknown4mo agonpmGitHubobserved · static extraction
    mcp

All indexed toolsSearch the registry for devops_explain_change