Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Go/no-go check for AI-built apps. Finds production problems locally and returns fixes.
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.
You 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": {
"sigship": {
"command": "npx",
"args": [
"-y",
"sigship",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add sigship -- npx -y sigship mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sigship": {
"command": "npx",
"args": [
"-y",
"sigship",
"mcp"
]
}
}
}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": {
"sigship": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sigship",
"mcp"
]
}
}
}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.
These 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 7, 2026
The registry name was verified with the GitHub account sigship, 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.1) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP
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.
Local-only Python MCP server for the Files.com API.
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.
The go/no-go check for AI-built apps. By zoof04.
SIGSHIP reads your repo on your own machine and writes the postmortem before the outage. It exits 0 only when it finds nothing serious, which gives your coding agent a real test for done.
npx sigship
No signup. No telemetry. No dependencies. Your code never leaves your machine.
SEV-1 A database table has no row level security
supabase/migrations/001_init.sql:1 Table profiles is created without row level security. Anyone with your public Supabase key can read this table. That key ships in your JavaScript.
NO-GO 1 SEV-1, 0 SEV-2, 2 SEV-3. Exit 1.
| Exit code | Meaning |
|---|---|
0 | GO. No SEV-1 or SEV-2 findings. |
1 | NO-GO. Something blocks launch. |
2 | SIGSHIP could not run. |
GO means these checks found nothing that blocks launch. It does not prove the app is safe.
In your terminal
npx sigship # check this folder
npx sigship --prompt # print every fix as one prompt for your AI tool npx sigship --json # machine-readable output npx sigship --strict # also block on SEV-3
On every pull request
npx sigship init
This adds a GitHub Actions workflow and a definition of done in AGENTS.md. It never overwrites an existing file.
Inside your coding agent
Claude Code:
claude mcp add sigship -- npx -y sigship mcp
Cursor, in .cursor/mcp.json:
{ "mcpServers": { "sigship": { "command": "npx", "args": ["-y", "sigship", "mcp"] } } }
The agent gets two tools, sigship_check and sigship_explain, and an instruction not to say it is done while the verdict is NO-GO.
SEV-1: live secrets in code, a committed .env with secrets, server secrets with browser-visible names, AI keys in the browser, missing Supabase row level security, policies that let anyone write, unverified Stripe webhooks, and user input inside SQL.
SEV-2: AI routes with no rate limit, roles stored in localStorage, and unsanitised HTML.
SEV-3: wildcard CORS, secrets in logs, no error boundary, no error tracking, no tests, and no lockfile.
SIGSHIP uses pattern checks. It can miss real problems and flag safe code. It reads code, so it can't see settings changed only in a dashboard.
MIT