Skip to main content
Glama
glitch-toolkit

glitch-toolkit

Related Servers

Alternatives to glitch-toolkit

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query a repository's verified semantic model, including capabilities, ownership, contracts, constraints, impact, health, and verification status, without re-deriving project facts. It exposes read-only tools for inspecting, reasoning about, and verifying the provenance-tracked surface.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only repository health scanning tools for drift detection, module reachability, prompt bloat, evidence calibration, and registration completeness, enabling agents to diagnose repositories via MCP.
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents and builders to run governance assessments including A³ scorecards, evidence-chain templates, compliance checklists, passport lookup, privacy/credential scanning, and doctrine knowledge routing, with traceable audit-ready outputs. It provides local, zero-dependency tools for AI governance self-assessment and registration readiness.
      6
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Exposes nine read-only tools that let a coding agent audit a repository for fabricated fallbacks, hollow or weakened tests, silently disabled checks and missing authorization scoping. Agents can run the six deterministic engines on changed or whole-repository code and get structured findings back without modifying anything.
      10
      1
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: glitch_status reports installation state, glitch_check runs validation checks, and glitch_ledger_tail reviews audit history. There is no meaningful overlap between the three tools.

    Naming Consistency5/5

    All tool names share a consistent glitch_ prefix and snake_case noun style, making the naming predictable and uniform. Minor differences in compound length do not create confusion.

    Tool Count5/5

    Three tools is well-scoped for a narrow read-only inspection server. Each tool earns its place by covering a distinct aspect of the same workflow without redundancy.

    Completeness5/5

    The toolkit covers the core needs of the domain: checking what is installed, validating whether checks pass, and reading the audit ledger. Since the server is explicitly read-only, absent write or apply tools are not gaps.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data