Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Independent deterministic verification for AI-written software. Local, evidence-backed checks.
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.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
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.
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 b2ige2-a11y, 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.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Hunter Killer
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.
Liquidation walls, snapshot age, evidence labels and a public record. Managed OAuth.
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.
B2IGE Verify is deterministic verification infrastructure for AI-written software. It runs real programs under declared contracts, records evidence, and produces a bounded PASS/FAIL/INCONCLUSIVE/ERROR result without asking the coding agent to grade its own work. BlindTest makes the boundary concrete: hidden tests exercise the produced program without exposing the suite or oracle to the agent.
B2IGE Verify v0.3.0 is the current public release. The final release record documents its exact-main qualification, platform boundaries, and public asset set.
| Platform | Native archive |
|---|---|
| macOS Apple Silicon | b2ige-0.3.0-aarch64-apple-darwin.tar.gz |
| macOS Intel | b2ige-0.3.0-x86_64-apple-darwin.tar.gz |
| Linux x86_64 | b2ige-0.3.0-x86_64-unknown-linux-gnu.tar.gz |
Also download SHA256SUMS and verify the matching archive before extracting. See installation details for prerequisites and offline validation.
Choose the archive for the host, then verify, extract, and put bin on PATH:
B2IGE_RELEASE_URL=https://github.com/b2ige2-a11y/b2ige-verify/releases/download/v0.3.0
B2IGE_ARCHIVE=b2ige-0.3.0-aarch64-apple-darwin.tar.gz curl -fL -O "$B2IGE_RELEASE_URL/$B2IGE_ARCHIVE" curl -fL -O "$B2IGE_RELEASE_URL/SHA256SUMS"
if command -v shasum >/dev/null 2>&1; then shasum -a 256 "$B2IGE_ARCHIVE" # compare with SHA256SUMS else sha256sum "$B2IGE_ARCHIVE" # compare with SHA256SUMS fi tar -xzf "$B2IGE_ARCHIVE" cd "${B2IGE_ARCHIVE%.tar.gz}" export PATH="$PWD/bin:$PATH" b2ige --version
The archive is ready for the adoption flow or the product-specific commands. Docker is required for BlindTest; missing prerequisites remain a readiness or non-PASS result.
BlindTest asks: does the produced program actually work? It runs visible checks against a correct and a buggy implementation, then executes sealed hidden cases in an attested Docker boundary. The correct implementation passes, the buggy implementation fails, and the sanitized Agent view is checked for private-value leakage.
From a source checkout or the source archive, with Docker available:
docker pull node:24.18.1-bookworm-slim
scripts/demo-blindtest.sh
The demo performs real execution and records evidence; its output is not canned terminal text. See the BlindTest example for the bounded secrecy boundary and the threat model for its limits.
| Product | Question | What it checks |
|---|---|---|
| BlindTest | Does it actually work? | Sealed hidden tests against an agent-produced target inside the declared Docker boundary. |
| BehaviorSeal | Did it change? | Trusted reference/candidate behavior under equivalent deterministic experiments. |
| SideEffect Proof | Did it actually happen? | Committed local SQLite effects under retries and fault schedules, not inferred attempts. |
inspect → init → prepare → trust approve → doctor → verify ID
prepare is non-authoritative: it discovers inputs and writes a reviewable draft. Trust approval remains an interactive human/trusted-controller decision. doctor reports readiness, not verification. verify ID resolves the approved identity and produces the real, evidence-backed result. Read the adoption guide for the full boundary.
These are committed measurements on the bounded B2IGE Verify Bench v1 corpus, not a claim of exhaustive correctness or a replacement for product evidence.
| Measurement (on the benchmark corpus) | Observed |
|---|---|
| Known bugs detected | 16 / 16 |
| False PASS | 0 |
| False FAIL | 0 |
| Verified reproduction | 16 / 16 |
| Hidden leakage observed | 0 |
| Agent private-value leakage | 0 |
| Mutation adequacy: known benchmark mutants | 2 / 2 |
All numbers above are on the benchmark corpus only. Bounded testing cannot establish complete correctness.
See the measured snapshot and benchmark methodology.
| Platform | Support boundary |
|---|---|
| macOS Apple Silicon | Native release |
| macOS Intel | Native release |
| Linux x86_64 | Native release; Docker and full benchmark CI |
| Windows x64 | Source/build plus bounded CLI smoke only; not VERIFIED_NATIVE |
| Linux arm64 | Deferred |
macOS binaries are unsigned and unnotarized. See installation and platform details for Docker, source-build, and archive boundaries.
Missing evidence cannot become PASS. Models do not assign verdicts. A result is bounded by the declared experiment, evidence, and platform scope.
Read the threat model, contracts, and evidence model before relying on a result.
Use the documentation index for getting started, product guides, trust and architecture, benchmarks, release history, and developer resources. The false PASS report accepts only synthetic or sanitized details; never upload hidden suites, private canaries, raw human evidence, or credentials.
Start with CONTRIBUTING.md, the architecture, and the security policy. Changes to verifier authority, evidence, contracts, or schemas require deliberate review; missing evidence must never be converted into success.
B2IGE Verify is licensed under Apache-2.0. No telemetry, hosted service, or paid API is required. Product names and trademarks are covered separately by TRADEMARKS.md.