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
Rigour
Overview
Description from the maker (original English)
Lets coding agents review their change, find an existing helper, and recall the team's lessons.
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
- npmNode.js installed (for the npx 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": {
"rigour": {
"command": "npx",
"args": [
"-y",
"@rigour-labs/mcp"
]
}
}
}Run this in your terminal
claude mcp add rigour -- npx -y @rigour-labs/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"rigour": {
"command": "npx",
"args": [
"-y",
"@rigour-labs/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": {
"rigour": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@rigour-labs/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 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account rigour-labs, 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 32688 servers in this category
- Published to the registry more recently than 67% of the other 32688 servers in this category
- Basic checks equal to or better than 100% of the other 32688 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 Rigour 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 (7.0.14) reached the registry 19 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, 御府和田玉 在售作品查询
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 2 days ago
Install
御府和田玉 在售作品查询
by 163yu.com
Live in-stock Hetian jade from Yufu, Shanghai: prices, monthly price guide, book a viewing.
Runs in the 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.
Rigour
A reviewer that knows how your team works, whichever agent writes the code.
Whichever agent your engineers use, its work arrives already shaped by how your team builds software, and it gets closer to your standards every week.
Teams used to carry their judgment through people: the senior who briefed you before you started, the reviewer who caught what you missed, the engineer who remembered why the last attempt failed. Coding agents write faster than any person can brief, review or remember. The knowledge is still in your team; Rigour is how it reaches every agent, at the speed agents work.
Works with Claude Code, Cursor, Codex, Cline and Windsurf. Free, open source, and runs on your machine.
How it does it
- Brief before writing. Before an agent edits a file, it is told what your team asks of that file: the rules your repository wrote for it, the lessons your team learned on it, the points your team settled against. At most three items per file, each cited. Installed by
rigour setup(--no-briefto leave it out), orrigour_brieffor any agent with MCP. See The briefing. - Verify while writing and before push. Your team's checks and rules gate any agent's work: on every edit, before the agent says "done", and before
git push, where your formatter, linter, type check and the tests that touch the change run too. Opt-in, the change is also checked against the goal its pull request declares: files outside its scope, "done when" items it never did. See The goal check. - Review with your team's context, at your team's severity. A reviewer that reads every point from your last human review, checks each rule your repository wrote that the change touches, and takes your reviewer's own "Blocking / Should fix / Nits" over its own reading. What your team blocks and what it lets go is your repository's setting, not one global opinion. See The reviewer.
- Learn from outcomes. A review point becomes a lesson only on evidence: a person corrected an agent's work, someone on the team decided, or it recurred across authors. What happened after the merge (a later fix on its lines, a revert) is shown to a person to decide, never a promotion on its own, and a lesson the team keeps merging against cleanly is taken back. What it learns flows into the next briefing and the next review.
One piece of work is one task, whatever agents and people touch it, and rigour thread shows everything that happened to it: what was caught while the code was written and fixed before the push, what blocked, what each review found. See The task thread.
What it is, and what it is not
- It learns only from evidence: your rules files, review points that were acted on, people's corrections, and what happened after merge. A guess never becomes a rule.
- It shapes and checks the agent; it never changes the model. No training, no fine-tuning. Any agent, any model.
- Concrete taste it captures well ("bound the window at both ends", "rerun the code generator after changing the schema"). Design taste stays with your people: anything Rigour cannot show in code is a should-fix at most, never a block.
- One machine, many companies, nothing crosses. Profiles keep each employer's or client's memory, lessons and team apart, chosen by the repository you're in. See Profiles.
- It starts from what you have written down. On day one, the briefing and the reviewer carry your repository's own rules (AGENTS.md, CLAUDE.md, Cursor rules, Copilot instructions). Lessons join as your reviews give them evidence, so a team with little review history starts with little to brief, and the briefing is off until you turn it on.
What runs by default, and what it costs
| Default | Cost | |
|---|---|---|
| Checks on every edit, before "done", before push | On after rigour setup | Local; the after-edit check starts the CLI once per edit |
| Your team's tools before push | On | Your own formatter, linter, type check and tests |
| The reviewer | Off until enabled in Studio or rigour.yml | Your agent's own model and login, one long read per review; the record of each review shows its cost |
| A panel of judges | Off; mode: full or panel: on | One judge's cost per judge, plus a short cross-examination of what they disagree on |
| A judge through any OpenAI-compatible API | Off; reviewers: [api] | The provider's price for your key |
| The briefing | On with rigour setup (--no-brief, brief.enabled: false or RIGOUR_BRIEF=0 turns it off) | No model; with the credential scan on, +22 ms per edit and +121 ms on a file's first edit (measured on Rigour's own repository) |
| The task thread | On wherever the hooks run | A line per event in your git folder |
How it works
| When | What Rigour does | If something's wrong |
|---|---|---|
| Every edit | Fast checks on the file: secrets, imports that don't exist, proven bugs | The agent sees it at once |
| Before "done" | The whole branch against main: findings to fix, code nothing uses, risky patterns, a merge conflict | The agent keeps working (at most three times) |
Before git push | The same, plus your formatter, linter, type check and related tests, and the reviewer that remembers | The push is blocked, one line per problem |
| On the pull request | A quiet safety net: at most two comments, only on what wasn't already checked | — |
With the briefing on, a line comes before all of these: before each file's first edit, what your team asks of that file.
Get started
See what it finds first, changing nothing (on a branch with work on it):
npx @rigour-labs/cli review --base origin/mainWorth it? Set it up:
brew install rigour-labs/tap/rigour # or: npm install -g @rigour-labs/clirigour setup # in your repository
rigour setup connects Rigour to your agents, installs the three moments, and checks that everything works. By default it is personal: nothing in your working tree. The agent hooks are installed once per machine and stay silent in any repository you have not switched on, and switching this one on writes only inside .git/. When your team wants it for everyone who clones, rigour setup --team commits it to the repository instead. Either way it merges into the agent configs you already have rather than replacing them. Changed your mind? rigour uninstall takes out exactly what it put in. Get started walks through it.
Rigour is about 70 MB per version. Semantic search (about 250 MB on Linux, 280 MB on macOS) is installed once per machine by rigour setup and shared by every version; skip it with --no-semantic.
Using Claude Code? The plugin does all of it:
/plugin marketplace add rigour-labs/rigour-plugin/plugin install rigour@rigour-labs
Want the reviewer too? It is off until someone turns it on, and you choose how far to take it: for yourself in Studio's Setup page, or for the whole team in rigour.yml:
review:reviewer: enabled: true mode: full # one judge per vendor, up to judges; single (the default) is one judge panel: on # only what most judges confirm blocks; required: no one may turn it off judges: 3 # 2 or 3, one per vendor installed escalate: risk # add judges only for risky changes; measure it with rigour backtest first
The push goes through as soon as the checks pass; the reviewer then reads the pushed commit in the background (only when it has an open, non-draft pull request, so you pay for a model only when someone will read the push). rigour review --status shows its verdict and what ran; rigour review --reviewer --full is the hard stop before you ask a person to review. Your own choice wins for your runs, except where the team set a floor, and Rigour always says which judges actually ran and why.
Then open Studio to watch it work:
rigour studioThe commands you will use
| Command | What it does |
|---|---|
rigour setup | Gets your repository ready and checks it works |
rigour brief | What your team would tell an agent before this task: rules, lessons and settled points, each cited |
rigour thread | What happened to a task, across agents, checks, pushes and reviews |
rigour review | Reviews your current change, or a branch before you open a PR (--reviewer adds the reviewer that remembers; --scope lists what a fix round changed that the review never asked for) |
rigour studio | Shows what Rigour stopped, learned and gave your agents |
rigour doctor | Tells you what's working, what isn't, and how to fix it |
rigour uninstall | Takes out exactly what Rigour put in; your own settings and edited files stay |
Everything else is in rigour help --all.
Built to be trusted
- It blocks only on what it can show. A deterministic check blocks only after it has been run over real merged pull requests. The model reviewer's findings block only when they name a wrong outcome or a cost, and with a panel, only when most judges agree. Guesses about style or size never block you and never show up on a PR.
- Say "not a bug" once. That finding never comes back, and checks your team keeps overruling go quiet on their own.
- When it can't check, it says so. No reviewer answer, nothing to review, a tool that isn't installed: each is reported plainly, never as a clean pass.
- Your code stays on your machine. The checks run locally. Code leaves only for a model you choose: your agents' own CLIs for the reviewer, or a provider when you run a model review with your key. Team sync sends only lessons from your team's own repositories. Every network call Rigour can make, and how to turn each off, is in Security.
- You see what it costs. When a model is used, Rigour records the real cost of each run.
- You see what each judge knew. A judge reads your repository and what Rigour gives it. The Claude judge loads no one's personal instructions; where a judge cannot be kept from a person's own config (Codex, Cursor), the record of the review says what else it read.
- Measured in the open. Claims about what Rigour catches are tested on real pull requests in the public driftbench arena.
- Measured against your own reviewers.
rigour backtestreplays the review on commits your team reviewed, with the review hidden, and scores it: which of the reviewer's points it would have caught first, and whether it would have blocked anything they called good. See Backtest. - One rule for what blocks. The review, the stop hook and the push gate decide from the same rule, so they never disagree about a finding.
What it costs
Rigour is free. With an agent you need nothing else: the checks run locally, and the reviewer and the review of risky changes use your agent's own model and login. A model key is only for reviewing code written without an agent, and for the pull request bot.
For teams
Pull requests. Add one workflow file and Rigour reviews every PR, quietly. Make it a required check, and a PR can't dismiss its own findings or loosen its own settings. See Pull requests and CI.
One setup for everyone. rigour setup --team commits the configuration, and each teammate runs `ri
Only the beginning is shown; read the rest in the repo