Skip to main content
Glama
kl987456

EngineeringOS MCP

by kl987456
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to EngineeringOS MCP

No user-submitted related servers found.

    Related Servers

    • SignalPilot

      zephyr45
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables evidence-first incident command: investigate outages, analyze evidence, approve simulated responses, verify recovery, and export postmortems through MCP tools.
      MIT

    • TraceLens MCP

      AaryanMadan54
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to query bundled synthetic logs, service metrics, and traces through three bounded read-only tools for evidence-first incident investigation.
      MIT

    • OpsLens AI MCP Server

      vp1410
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP tools to search engineering runbooks and historical incidents using semantic retrieval, supporting evidence-grounded incident investigation.
      -

    • Processkit

      raintr91
      A
      license
      Not graded
      quality
      D
      maintenance
      Standalone MCP harness for cross-system process evidence, code-change impact review, and natural-language repository checkout mapping, with optional accelerators like CodeGraph.
      1
      MIT

    • Faultline

      aawhan0
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP-native AI incident response system that empowers agents to investigate production incidents, collect evidence, hypothesize root causes, and drive controlled remediation and recovery verification.
      1
      -
    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

    C2.9/5.0

    Scored across 27 tools

    Disambiguation3/5

    Several tools have overlapping purposes and could be confused: repo_overview vs language_profile vs dependency_health vs software_inventory all gather similar inventory evidence; find_symbol vs map_find_symbol and dependency_graph vs map_dependency_graph are nearly identical except for local vs hosted scope; security_scan vs code_security_scan overlap in security scanning. Descriptions help somewhat, but boundaries are fuzzy.

    Naming Consistency3/5

    Mostly snake_case verb_noun style (e.g. index_code, search_code, run_tests), but there are notable deviations: 'investigate' and 'diagnostics' are noun-only, 'production_readiness' is a noun phrase, and 'cyclonedx_sbom' is a product name. The map_ prefixed tools add a second naming dimension.

    Tool Count2/5

    27 tools is heavy for a code analysis server, and several pairs are near-duplicates (map_ vs local variants), suggesting over-fragmentation rather than distinct value. It pushes into the 25+ range that typically signals excessive surface area.

    Completeness4/5

    The surface covers a wide lifecycle: indexing, symbol search, dependency analysis, testing, security, SBOM, and map ingestion/export. Minor gaps exist (e.g. no explicit tool for retrieving a full security report or package license compliance), but most core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources