Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
verifyfirst
Overview
Description from the maker (original English)
Look up what your verification method cannot see: 48 failures that report success.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- PyPIPython’s uv installed (for the uvx command)
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": {
"verifyfirst": {
"command": "uvx",
"args": [
"verifyfirst-mcp"
]
}
}
}Run this in your terminal
claude mcp add verifyfirst -- uvx verifyfirst-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"verifyfirst": {
"command": "uvx",
"args": [
"verifyfirst-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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"verifyfirst": {
"type": "stdio",
"command": "uvx",
"args": [
"verifyfirst-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.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account simulacra, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32375 servers in this category
- Published to the registry more recently than 30% of the other 32375 servers in this category
- Basic checks equal to or better than 100% of the other 32375 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is verifyfirst safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.8.0) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, DiffCI
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
DiffCI
by DiffCI
Fail-closed, change-aware verification for AI coding agents with affected-test guidance.
Computer or cloudUpdated today
Install
README from the maker
Open the README
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.
verifyfirst-mcp
An MCP server for what your verification method cannot see.
A failure that crashes is cheap. A failure that *reports success* is expensive: the screenshot looks fine, the command exits zero, the endpoint returns 200, and the bug ships.
This server exposes verifyfirst.dev — a registry of 48 such failures, organised by the instrument that missed them rather than by the technology involved, because the instrument is what you know before you know the bug.
Install
uvx verifyfirst-mcp # run it directlypip install verifyfirst-mcp # or install it
Register with Claude Code:
claude mcp add verifyfirst -- uvx verifyfirst-mcpOr any MCP client:
{"mcpServers": { "verifyfirst": { "command": "uvx", "args": ["verifyfirst-mcp"] } } }
Tools
| Tool | What it does |
|---|---|
from_symptom(description) | Start here when something is wrong but you do not know why. Describe what you see — "deploy ran but nothing changed", "200 but the data is wrong" — and get the failures that produce that appearance, each with its check. |
blind_spots(instrument) | The one to reach for mid-task. What an instrument cannot see, terse. Takes loose names — curl, 200, pgrep, systemctl, stdout, playwright all resolve. |
list_instruments() | All six instruments. |
get_instrument(id) | Full detail plus every recorded failure it missed, each with its check. |
search(query) | Substring search across the registry. |
get_entry(id) | One entry, e.g. NS-001. |
get_protocol() | A five-step checklist for claiming work is done. |
Example
> blind_spots("screenshot")screenshot (A rendered image) is blind to:
- Time. A still frame cannot distinguish 'renders one frame then stops' from 'renders one frame correctly'.
- Whether scripts ran at all, as opposed to running and producing this. ...
Notes
Zero dependencies — Python standard library only. Works offline from a bundled copy of the registry; pass --remote to read the live one, which falls back to the bundle on any failure.
Every entry in the registry is a failure that genuinely occurs, marked observed (diagnosed first-hand) or documented (primary source cited and the check reproduced). None are hypothetical.
CC0-1.0 — public domain. Maintained by Zion Labs.