Skip to main content
Glama
MyoungSoo7

k8s-traps

by MyoungSoo7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to k8s-traps

No user-submitted related servers found.

    Related Servers

    • mcp-k8s-observability

      NeoScraids
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect Kubernetes pods and cluster events, query Prometheus and Loki, and diagnose pod health with suggested actions through MCP tools.
      MIT

    • mimiops-mcp

      sergelogvinov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to safely observe and troubleshoot Kubernetes workloads, with limited recovery actions like pod deletion and Helm rollbacks, while preventing dangerous modifications.
      Apache 2.0

    • kubectl-mcp

      teresa-tran
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets AI agents inspect Kubernetes clusters in plain English, exposing read-only tools for pods, deployments, services, events, and logs, with mock and real backend support.
      MIT

    • mcp-openshift

      dockndevai
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to explore and operate OpenShift/Kubernetes clusters, offering read-only tools for projects, pods, logs, and resources, with opt-in higher modes for scaling, restarts, applying manifests, and deletions under safe-by-default guards.
      6
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: list_traps enumerates available checks, audit_manifests executes the checks, and explain_trap provides detailed breakdowns. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_traps, audit_manifests, explain_trap). The naming is predictable and immediately conveys the action and target.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped but each tool is essential: discovery, execution, and explanation. This is an appropriate minimal set for a specialized trap-checking utility.

    Completeness5/5

    The domain is well-covered: users can enumerate available traps, run the audit, and understand any trap's rationale and fix. No obvious gaps remain for the server's stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources