glitch-toolkit
Related Servers
Alternatives to glitch-toolkit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides 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.1MIT
- AlicenseAqualityDmaintenanceValidates release hygiene in local repositories with network-free, read-only tools for checking repo structure, version alignment, and generating release checklists.3MIT
- AlicenseBqualityBmaintenanceEnables 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.6MIT
- AlicenseBqualityBmaintenanceChecks AI agents' claims against primary evidence, with no model; observes only what you grant.8108 PyPIApache 2.0

PrufGate MCPofficial
AlicenseBqualityBmaintenanceExposes 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.101Apache 2.0
TDQS
Scored across 3 tools
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.
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.
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.
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.