Skip to main content
Glama
Sign In
@sixty-sh/mcp

@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
      C
      maintenance
      Enables coding agents to access live runtime observability data such as logs, deploys, and health metrics for evidence-based incident triage.
      1
      MIT

    • Core Web Vitals MCP Server

      surendranb
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to retrieve real-user performance metrics and 28-day field trends, run Lighthouse lab audits, and access remediation playbooks for LCP, INP, and CLS.
      7
      249 PyPI
      MIT

    • LeanGate

      lambdabypi
      A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to check whether a repository already provides the helper they are about to reimplement, surface bloat, missing error handling and security findings after each edit, and block task completion until blocking issues are fixed.
      7
      MIT

    • switch-trust-mcp

      sandbox-quantum
      A
      license
      B
      quality
      B
      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.
      37
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.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

    ActivityStale
    ResponsivenessNo recent community issues

    Resources