check_tripwires
Preview which tripwires would fire for a given file path, without reading the file.
LABSCO SUMMARY
The correction is attached to the file, so it arrives with the next read instead of depending on someone remembering it.
read_file is the whole mechanism: the context is injected before the code is seen, which is earlier than a review and earlier than a test. What keeps it auditable rather than opaque is explain, which renders exactly what would be injected for a path including the dependencies and the entries that were suppressed, and check_tripwires, which answers the same question without opening the file at all. Retiring a rule is a soft disable that sets active: false and leaves the YAML in place, so the reason it existed outlives the decision to stop firing it.
What it is
A project-local safety-note system: tripwires stored as YAML and matched to paths, injected into file reads, with tools to preview what would fire and why.
What you get
- read_file, which reads a file with the matching tripwire context injected, in place of a raw read.
- create_tripwire, which records a new one with its triggers, severity, tags, context and what it was learned from.
- list_tripwires filtered by path, tag or severity, and deactivate_tripwire, which sets active: false in the YAML rather than deleting the file.
- check_tripwires, which previews what would fire for a path without reading the file, and explain, which shows the matched tripwires, their dependencies, the suppressed entries and the rendered injection.
- Project navigation relative to the project root: list_directory, file_stat for type, size and modified and created times, and search_files by glob pattern.
Requirements
Nothing to supply — no account, no key. A project root, since paths and glob searches are resolved relative to it, and the YAML files the tripwires live in.
Setup effort
One command — npx -y @tripwire-mcp/tripwire serve --project .
USE CASES
01
Opening a file that has caught someone out before
Reading through this tool injects the matching tripwires with the content, so the warning arrives before the edit rather than in review. The same match can be previewed without reading the file at all.
02
Writing down a correction so it does not have to be repeated
A tripwire records its triggers, a severity, tags, the context to inject and what it was learned from, so the next person gets the reasoning rather than only the rule.
03
Working out why a warning appeared on this file
The explanation renders exactly what would be injected for the path, including which tripwires matched, what they depend on, and which entries were suppressed and therefore never shown.
04
Retiring a rule that no longer applies
Deactivating sets active: false in the YAML instead of deleting it, so the reason the rule existed survives the decision to stop firing it.
05
Finding out how much of the project a rule would cover
Glob search and directory listing resolve relative to the project root, so the set of files a trigger matches can be enumerated and each one checked before the rule is written.
9 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_tripwire
Create a new tripwire to prevent future mistakes. Use when corrected on a pattern that should be remembered.
deactivate_tripwire
Soft-disable a tripwire without deleting the file. Sets active: false in the YAML.
explain
Show exactly what would be injected for a file path and why. Returns matched tripwires, dependencies, suppressed entries, and the rendered injection.
file_stat
Get file or directory metadata (type, size, modified, created).
list_directory
List files and directories at a path relative to the project root.
list_tripwires
List all active tripwires, optionally filtered by path, tag, or severity.
read_file
Read a file with tripwire context auto-injected. Use instead of raw file reads to get safety-critical context before modifying code.
search_files
Search for files matching a glob pattern relative to the project root.
BEFORE YOU INSTALL
What to know first
Tools you get
9 tools when we connected.
Requires
Node.js >= 18
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 9 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @tripwire-mcp/tripwire serve --project .MCP Clients
Claude Code, Cursor
JSON
{
"mcpServers": {
"tripwire": {
"command": "npx",
"args": [
"-y",
"@tripwire-mcp/tripwire",
"serve",
"--project",
"."
]
}
}
}
