Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Free UX and AI-agent readiness snapshot for any website. No sign-up, no API key.
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.
VERIFUX_API_URLYou 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": {
"snapshot": {
"command": "npx",
"args": [
"-y",
"@verifux/mcp"
],
"env": {
"VERIFUX_API_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add snapshot --env VERIFUX_API_URL=your-value -- npx -y @verifux/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"snapshot": {
"command": "npx",
"args": [
"-y",
"@verifux/mcp"
],
"env": {
"VERIFUX_API_URL": "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": {
"snapshot": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@verifux/mcp"
],
"env": {
"VERIFUX_API_URL": "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.
VERIFUX_API_URL 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 7, 2026
The registry name was verified with the GitHub account Verifux, 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 (1.0.4) reached the registry 5 days ago.
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, Systemdox
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.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
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.
One tool, run_snapshot. Point it at any URL and it reports what an agent actually finds when it arrives: a band, a pass rate, the top findings, and whether the page declares an agent surface at all.
Zero dependencies. No sign-up. No API key.
Claude Code
claude mcp add verifux -- npx -y @verifux/mcp
Any MCP client (Claude Desktop, Cursor, and others)
{
"mcpServers": { "verifux": { "command": "npx", "args": ["-y", "@verifux/mcp"] } } }
Then just ask: *"run a Verifux snapshot on example.com"*.
A real run, pasted verbatim:
Verifux snapshot for example.com
Band: Mixed - 13 of 16 automated checks passed Findings: 0 critical, 2 major, 1 minor
Top findings: [MAJOR] No Organization or FAQPage structured data for AI answer engines [MAJOR] No H1 heading on the page [MINOR] No meta description for search engines or AI summaries to quote
AI agent surface: none detected
That last line is the one almost nobody checks. `none detected` means nothing an agent looks for was found: no declared tools, no /.well-known/mcp.json, no /agents.md.
We got exactly that on our own site. The file existed. We were serving it at the wrong path, and
nothing anywhere warned us. One path, and the whole surface was invisible.
Agent readiness is the only part of a site that can break without anyone noticing. No error, no alert, nothing in a dashboard. Just traffic that never arrives.
| Name | run_snapshot |
| Takes | url, any publicly reachable URL. Nothing else |
| Returns | Band (Strong / Mixed / Weak / Poor), pass rate over named automated checks, top findings, and whether an agent surface is declared |
| Env | VERIFUX_API_URL to point at a different backend. Defaults to https://api.verifux.app |
It deliberately has no score out of 100. That belongs to the full 54-checkpoint audit, and two different numbers out of 100 would contradict each other.
The same check as a CLI, with a CI mode that fails the build when the band drops:
npx @verifux/cli your-site.com --ci --min-band mixed
→ [Verifux/verifux-cli](https://github.com/Verifux/verifux-cli)
This is the free snapshot: a fast, deterministic read. The full audit lives at [verifux.app](https://verifux.app).
This repo is the client shim. The audit engine behind api.verifux.app is not open source.
MIT · built by Verifux