Skip to main content
Glama
AbstractGlitch

glitch-toolkit

by AbstractGlitch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to glitch-toolkit

No user-submitted related servers found.

    Related Servers

    • project-surface

      Richie11747
      A
      license
      Not graded
      quality
      A
      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

    • repo-health

      chenyinrusi
      A
      license
      Not graded
      quality
      C
      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

    • Gumi-MCP

      igv8101
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely inspect a local repository's code and metadata while blocking private data from leaving the machine, providing read-only tools for search, change tracking, and integrity verification.
      MIT

    • IRIS Regression Memory

      haleema-ignite
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic behavioral regression review of pull-request diffs by checking changed code against approved incident-derived contracts. It exposes read-only tools to assess diffs and pull requests, list and fetch contracts, and report outcomes over stdio without mutating repositories.
      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

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources