What it does
Glitch Toolkit installs six guardrails into a repository and, on request, runs each one against a case it should refuse. A guardrail that no longer refuses anything fails the check instead of passing quietly. Each check finds the artifact, runs it, and confirms it refuses a broken case. The install command never writes CLAUDE.md, FLEET.md, FLOOR.md or PLAN.md, and it does not overwrite existing files unless --force is given. The FLOOR.md and PLAN.md templates ship deliberately unpassable.
It suits teams that want to catch guardrails that have silently stopped working. The MCP server offers three read-only tools to an agent: glitch_status, glitch_check and glitch_ledger_tail. It records every question and answer in an append-only JSONL ledger. It is designed to be run read-only first, so its results can be reviewed before any gating is added.
cli.py is a single file with no dependencies, and status and check work when it is copied into a repository. install needs the rest of the package. Nothing runs over the network, and the tool writes only inside the directory it is pointed at. The MCP extra should be installed in an isolated environment, using uvx or a virtualenv, and is configured in .mcp.json for Claude Code.
Limitations and requirements
The [mcp] extra pulls in many dependencies, and pip may upgrade packages already present in a global Python interpreter. The MCP server gates nothing: it cannot block or intercept actions and has no database connection, credential or network access. The --no-ledger option turns off ledger logging. Without the [mcp] extra, the server test suite is reported as SKIPPED. The install command requires the full package, not only cli.py. Existing artifacts are kept unless --force is used.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Glitch Toolkit
Read-only checks that fail a guardrail which is present but has stopped refusing anything
v0.1.4As shown on registry.modelcontextprotocol.io when we last read it