Skip to main content
Glama
sixty-sh

@sixty-sh/mcp

Official
by sixty-sh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @sixty-sh/mcp

No user-submitted related servers found.

    Related Servers

    • DevContext

      sid-stack001
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to access live runtime observability data such as logs, deploys, and health metrics for evidence-based incident triage.
      1
      MIT

    • switch-trust-mcp

      sandbox-quantum
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives coding agents read-only access to an AI-SPM backend's flagged issues, inventory, and remediation guidance so they can fix the affected code, along with guardrail policies, LLM-interaction analytics, cost-optimization analyses, and red-teaming evaluation results.
      Apache 2.0
    • mnm-incident-investigator by MNM-Technology-LLC

      mnm-incident-investigatorofficial

      MNM-Technology-LLC
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables a local AI agent to investigate service incidents by querying read-only telemetry such as service health, metrics, logs, and traces, then produce verifiable assessments with evidence links and uncertainty.
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the finding lifecycle: list, view, claim, close, plus service health and installation. No overlap exists between the six tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (list_findings, get_finding, claim_finding, close_finding, check_service, install_sixty). This is a model of uniform naming.

    Tool Count5/5

    Six tools perfectly cover the core workflow of a performance-findings service: listing, inspecting, claiming, closing, plus setup and telemetry checks. None are redundant and none are missing.

    Completeness5/5

    The tool surface provides complete lifecycle coverage for findings (list, get, claim, close) and addresses operational needs (service health, installation). The only theoretical gap would be manual finding creation, which is outside the product's purpose since findings are auto-generated.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources