Skip to main content
Glama
fernedy

ops-mcp

by fernedy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ops-mcp

No user-submitted related servers found.

    Related Servers

    • SIFTGuard

      sodiq-code
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous digital forensics and incident response by wrapping SIFT Workstation tools as MCP tools and orchestrating a multi-agent AI pipeline for evidence analysis and remediation planning.
      2
      MIT

    • gitmem

      josephy02
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides MCP tools that give AI agents persistent, append-only memory in a git repository, letting them record observations, decisions, and corrections while retrieving context briefs, current facts, conflicts, and traceable event history without a vector database.
      4 npm
      MIT

    • Forensics MCP Server

      Ghosthunter5599
      F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to perform digital forensics and incident response tasks by dynamically discovering and utilizing host tools for memory analysis, metadata extraction, threat detection, and file dissection.
      5
      1
      -

    • 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
    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

    A3.8/5.0

    Scored across 3 tools

    Disambiguation2/5

    container_autopsy and container_obituary substantially overlap—both diagnose why a container died, examine logs, and output a markdown report. An agent would struggle to reliably choose between them despite the slight difference in depth and tone. git_sins is the only clearly distinct tool.

    Naming Consistency4/5

    All three tools follow a consistent lowercase_snake_case pattern with a domain prefix and a thematic noun: container_autopsy, container_obituary, git_sins. The pattern is predictable and readable, though the playful nouns deviate slightly from conventional verb_noun naming.

    Tool Count3/5

    Three tools is on the thin side for a server named 'ops-mcp', but the set is tightly focused on diagnostics and forensics. It feels more like a themed utility collection than an operational coverage layer, which is acceptable but not rich.

    Completeness3/5

    The scope is narrow—container death investigation and git history analysis—and within that scope the tools cover their stated purposes. However, the two container tools are redundant rather than complementary, and there is no action-oriented tooling (e.g., restart, cleanup) that an 'ops' user might expect.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources