Skip to main content
Glama
coreyhiggins

ops-toolbox

by coreyhiggins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ops-toolbox

No user-submitted related servers found.

    Related Servers

    • Cimon-MCP

      Commander17X
      A
      license
      A
      quality
      C
      maintenance
      Offline MCP server with runbooks for high-volume logs, metrics, traces, and event streams. Search and diagnose symptoms without external dependencies.
      4
      MIT

    • mcp-incident-copilot

      ShreyAC962
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides guarded, audited, read-only access to ops tooling (alerts, metrics, logs, deploys, runbooks) and a triage agent that diagnoses incidents end-to-end with CI-verified root cause analysis.
      MIT

    • automation-health-mcp

      chainwright
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for auditing automation health, finding failures, stale logs, and non-functional endpoints that report success while quietly failing.
      7
      MIT

    • runtime-inspector-mcp

      ludi-uni
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server to inspect allowlisted Docker containers, systemd services, JSONL logs, and HTTP health endpoints without arbitrary shell access.
      MIT

    • elastic-mcp

      jrvalinas
      A
      license
      B
      quality
      D
      maintenance
      Small production-oriented MCP server for diagnosing incidents from Elasticsearch logs with unknown schema. It provides tools for log discovery, retrieval, and issue diagnosis.
      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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: log tailing, endpoint checking, and runbook search/add. There is no overlap in purpose or resource type.

    Naming Consistency4/5

    Names are clear and readable, but they follow two patterns: verb_noun (tail_log, check_endpoint) and noun_verb (runbook_search, runbook_add). This minor inconsistency is not confusing but prevents a perfect score.

    Tool Count5/5

    With 4 tools, the set is well-scoped for an operations toolbox. Each tool serves a clear purpose without redundancy or bloat.

    Completeness4/5

    The set covers the primary operations for its domain: log inspection, endpoint validation, and runbook management (search/add). Minor gaps like runbook deletion exist, but the core workflow is complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources