@rigour-labs/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @rigour-labs/mcp@7.0.14
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
1 tool with commands in capitals or very long text
- Gives the agent orders in
rigour_check:Run quality gate checks on the project. MUST be called before declaring any coding task complete. By default it judges your change as the stop h
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
rigour_check cwd, scope, files, deep, pro, apiKey, provider, apiBaseUrl, modelName
Run 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_packet cwd, offset, limit
After 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_remember cwd, key, value, scope
Store 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_brief cwd, goal, files
Before 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_recall cwd, key, query
Load 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.
6 more tools
rigour_check_pattern cwd, name, type, intent, signature, keywords, file
CALL 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_review cwd, base, diff, files, mode
Review 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_verdict cwd
What 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_ack cwd, file, function, verdict, note
Record 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_index cwd, semantic, force, output
Build 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_scope cwd, query, limit, taskId, agentId
CALL 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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22.13 |
| Source | github.com/rigour-labs/rigour |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-JFL7sboO3Q+OZZJkmKl9PeW0AA9v1ngUQQUcMfoENz1yGq5dRh3uwO8Ib/2kKRbjoBA8mIA2KijZgAh9ZiXfZw== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40rigour-labs/mcp)
New version out? Ask for a fresh report.