Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Local gut check before risky agent actions: calibrated safe/intended probabilities, no API calls.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GUTSY_URL, GUTSY_INFERENCE_DIR, GUTSY_PROCEED_MIN, GUTSY_BLOCK_MINYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"gutsy": {
"command": "uvx",
"args": [
"gutsy-mcp"
],
"env": {
"GUTSY_URL": "your-value",
"GUTSY_INFERENCE_DIR": "your-value",
"GUTSY_PROCEED_MIN": "your-value",
"GUTSY_BLOCK_MIN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add gutsy --env GUTSY_URL=your-value --env GUTSY_INFERENCE_DIR=your-value --env GUTSY_PROCEED_MIN=your-value --env GUTSY_BLOCK_MIN=your-value -- uvx gutsy-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"gutsy": {
"command": "uvx",
"args": [
"gutsy-mcp"
],
"env": {
"GUTSY_URL": "your-value",
"GUTSY_INFERENCE_DIR": "your-value",
"GUTSY_PROCEED_MIN": "your-value",
"GUTSY_BLOCK_MIN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"gutsy": {
"type": "stdio",
"command": "uvx",
"args": [
"gutsy-mcp"
],
"env": {
"GUTSY_URL": "your-value",
"GUTSY_INFERENCE_DIR": "your-value",
"GUTSY_PROCEED_MIN": "your-value",
"GUTSY_BLOCK_MIN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
GUTSY_URL envGUTSY_INFERENCE_DIR envGUTSY_PROCEED_MIN envGUTSY_BLOCK_MIN envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account kouhxp, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 31 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Happo
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Review Happo's visual and accessibility diffs: inspect comparisons, accept or reject, report flakes.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A local gut check for coding agents. Before Claude Code, Codex, Cursor or Copilot runs rm -rf, force-pushes, deploys or sends something, it calls gut_check and gets back calibrated probabilities that the action is intended and safe, plus a recommendation: proceed, confirm (ask the user first) or block.
Runs on your CPU with gutsy (0.8B, 775 MB GGUF). No API calls, no per-call cost, deterministic, and your code never leaves the machine.
It's a fast second opinion that adds friction where it's warranted. It is not a security boundary: the agent decides whether to call it and writes the context it sees, and a 0.8B model is weak at ambiguity and multi-step rules (see the model card). Keep your normal permission settings on. Default thresholds aren't tuned for your workflow; log the probabilities and adjust them.
git clone https://github.com/kouhxp/gutsy
pip install -e gutsy/gutsy-inference hf download kouhxp/gutsy --include "gutsy-0.8b-v04*" --local-dir gutsy/gutsy-inference/models cd gutsy/gutsy-inference && cp models.example.json models.json gutsy-inference check && gutsy-inference serve # http://127.0.0.1:8765
Or set GUTSY_INFERENCE_DIR=/path/to/gutsy/gutsy-inference and gutsy-mcp starts it on first use.
Claude Code:
claude mcp add gutsy -- uvx gutsy-mcp
Cursor (.cursor/mcp.json) / Claude Desktop:
{ "mcpServers": { "gutsy": { "command": "uvx", "args": ["gutsy-mcp"] } } }
VS Code (.vscode/mcp.json):
{ "servers": { "gutsy": { "type": "stdio", "command": "uvx", "args": ["gutsy-mcp"] } } }
Codex (~/.codex/config.toml):
[mcp_servers.gutsy]
command = "uvx" args = ["gutsy-mcp"]
Then tell the agent when to use it (CLAUDE.md, AGENTS.md, .cursor/rules):
Before deleting files, rewriting git history, force-pushing, touching databases,
deploying, publishing or sending anything, call
gut_check. If it doesn't return
proceed, stop and ask me.
An MCP tool only runs if the agent remembers to call it. The hook runs on every risky-looking Bash command regardless. It can only ask or deny, never auto-approve.
uv tool install gutsy-mcp # puts gutsy-hook on PATH
.claude/settings.json:
{
"hooks": { "PreToolUse": [ { "matcher": "Bash", "hooks": [{ "type": "command", "command": "gutsy-hook", "timeout": 60 }] } ] } }
block becomes a confirmation prompt by default; set GUTSY_HOOK_ALLOW_DENY=1 to deny outright.
gut_check(action, context="", user_request="") returns:
{
"recommendation": "confirm", "reason": "Not confident enough to proceed without the user.", "p_intended": 0.41, "p_reversible": 0.08, "verdict_probabilities": {"proceed": 0.22, "confirm": 0.61, "block": 0.17}, "reject": 0.04, "confidence": 0.42 }
| env var | default | |
|---|---|---|
GUTSY_URL | http://127.0.0.1:8765 | runtime URL |
GUTSY_INFERENCE_DIR | lets gutsy-mcp start the runtime | |
GUTSY_MODEL | runtime default | model name from models.json |
GUTSY_PROCEED_MIN | 0.85 | |
GUTSY_BLOCK_MIN | 0.50 | |
GUTSY_API_KEY | if you run serve --api-key-env |
License: Apache 2.0.