All servers / Developer / Rigour MCP server
Rigour MCP server
Rigour's MCP server: lets coding agents review their change, check for an existing helper before writing a new one, and recall the team's lessons. Works with Cl
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-19 on package version 7.0.14. Package: @rigour-labs/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (10.7 seconds including download)
- Tools offered: 11
- Last published: 2026-10-19
- Weekly downloads (npm): 1,131
- License: MIT · Direct dependencies: 5
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
rigour_check9 of 9 parameters describedRun quality gate checks on the project. MUST be called before declaring any coding task complete. By default it judges your change as the stop hook and push gate will: FAIL means something in it must be fixed. **Always show the user the headline summary from this tool's output** — it tells them what Rigour caught. If FAIL, call rigour_get_fix_packet for what to fix, with exact file:line.
rigour_get_fix_packet3 of 3 parameters describedAfter rigour_check FAILs: your change's must-fix items (they block you), then optional notes, paged, each with file:line and the fix. Stay in your change unless a must-fix item names a file. Page with next_offset; re-run rigour_check.
rigour_remember4 of 4 parameters describedStore an instruction or convention to remember across sessions. Provide 'key' (short snake_case) and 'value' (the full text). scope: 'repo' (default, this repository), 'user' (all your repositories), or 'team' (this repository, and shared as a team candidate that teammates' agents receive once a person promotes it). Values containing credentials are refused.
rigour_brief3 of 3 parameters describedBefore writing: with goal, the team's rules, lessons and settled points for the task (max 10, cited); with only files, its word on each file you will edit. A [must] you break blocks at review.
rigour_recall3 of 3 parameters describedLoad stored conventions. At the START of a task, call it with 'query' describing the task to get the few memories that match by meaning, plus promoted team knowledge when team mode is on. With 'key' it returns that memory; with neither, every repository and user memory.
rigour_check_pattern7 of 7 parameters describedCALL THIS BEFORE creating any new function, component, hook, or class. Checks if it already exists in the codebase (prevents duplication), checks for known security vulnerabilities, and BLOCKS writes to protected paths (.github/, CI/CD configs, rigour.yml). Always pass the target file path.
rigour_review5 of 5 parameters describedReview the change you just made before calling it done: runs Rigour's gates and keeps only findings on changed lines, each with file, line and a suggested fix. With no diff it reads your uncommitted work from git (new files included); pass base to review the whole branch (e.g. 'main'). Same verdict as `rigour review` in CI.
rigour_reviewer_verdict1 of 1 parameter describedWhat the model reviewer last decided for this branch: the confirmed items to fix (with id, file:line, consequence and evidence), the disputed ones that are not work, which mode ran, and whether the verdict is for the current commit. Read-only: never runs a model, never dismisses.
rigour_review_ack4 of 5 parameters describedRecord that you reviewed a function from rigour_review's review_task: verdict "fixed" (you fixed a defect) or "no_issue", with a note saying what you checked. Covers the function's current code only; editing it later puts it back in the task.
rigour_index4 of 4 parameters describedBuild or update the Rigour pattern index (.rigour/patterns.json). CALL THIS when the index is missing or stale — before rigour_context_scope or rigour_check_pattern. One AST pass extracts functions, classes, routes, and signatures for reuse, embedded locally so rigour_check_pattern can match by intent; semantic=false skips the embeddings.
rigour_context_scope5 of 5 parameters describedCALL THIS BEFORE reading source files. Returns a minimal editScope (3-10 files) with signatures from the pattern index instead of full file bodies. Uses semantic search when embeddings are available. If index is missing, instructs to call rigour_index first. Highest-impact token saver in the Rigour protocol.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.