Seatrial MCP · Workflow
Install once, catch it three ways.
How the MCP server lives in a vibe-coder’s daily loop: setup, pre-generation interrupt, post-generation gate. Step through the flow or hit Play.
Seatrial MCP — workflowv0.7.0
Install once. Catch it three ways.
Detection on demand · pre-generation interrupt · post-generation gate. One MCP server, three layers, all running on your machine.
npm: shipsafe-mcp@0.7.0stdio MCP transportClaude Code · Codex · any host
0. Seatrial MCP workflow
How the MCP server is set up once, then catches security failures at three different moments in the dev lifecycle. Press Next or Play.
0 / 9
← / → to step · Space to play/pause · R to reset
One slot, two hooks
Step 2 writes .git/hooks/pre-commit. So does gauntlet, our review harness — and git only runs one of them. They are not the same tool and neither replaces the other:
shipsafe-mcp
Sentinel, one checkpoint
Scans staged source at commit time and blocks on critical-or-above. Static, sub-second, no model. This page.
npx -y shipsafe-mcp install-hooks
gauntlet
a reviewer, four checkpoints
Runs the coding agent you already pay for at the agent turn, the commit, the branch and the whole project — and remembers across all four what you already dismissed.
npm install -g gauntlet-review
To run both, install Gauntlet second and tell it so. It moves this page’s hook to .git/hooks/pre-commit.localand runs it first — the cheap gate before the one that costs model tokens — then reviews what survives:
gauntlet init --merge-precommit
Gauntlet is MIT, free, and sends nothing unless you turn it on. Source · npm