Rigour MCP server
io.github.rigour-labs/rigour·v7.0.14·27 starsLets coding agents review their change, find an existing helper, and recall the team's lessons.
not scanned yet
27 stars2.5k downloads/wk
Reviews
Write oneNobody has reviewed Rigour yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Rigour tools
No tool declarations could be read from the package source. They show once the server is installed.
How Rigour compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- GitHub stars
- 27
- more than 91% of 28,688 servers
- Downloads a week
- 2,547
- more than 95% of 12,191 servers with a package
Release history: 18 versions in the registry since 2026-09-14, latest 2026-10-19, typically one every 1 day.
Install Rigour in Claude Code, Cursor or VS Code
Runs npx -y @rigour-labs/mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add rigour -- npx -y @rigour-labs/mcp
What the publisher says
From the Rigour repository's README, as published. We do not edit it. Read it on GitHub
Rigour
Your coding agents write code. Rigour makes the codebase learn.
Rigour is a local-first engineering intelligence layer for coding agents. It gives agents the smallest useful context, enforces deterministic boundaries around observable work, and turns verified outcomes into reusable knowledge for the next task.
It is not another chat wrapper or a prettier linter dashboard. Rigour connects code, agent actions, decisions, proof, and learning into one evidence-backed system.
npx rigour-scan▶ Watch Rigour in action
Run this in any repository to see the first signal. No account or hosted service required.
Why teams use Rigour
See how agent work improves the codebase
Rigour Studio is an evidence map for engineering work—not just a dependency graph.
intent → context → policy → agent action → verification → outcome → learning
│ │ │
└──── advice + impact ────┴───────────────┘Open Studio to trace an agent run from the recommendation it received to the code it changed, the checks that ran, the risk it prevented, and the knowledge it left behind.
npx @rigour-labs/cli init
npx @rigour-labs/cli hooks init
npx @rigour-labs/cli studioThe five product areas stay simple:
- Map — connect code structure, agent activity, decisions, proof, and outcomes.
- Agents — inspect scopes, run history, handoffs, and the guidance each agent received.
- Review — understand gates, policy decisions, conflicts, and Fix Packets.
- Knowledge — explore patterns, memory, lessons, semantic recall, drift, and cost evidence.
- Settings — see index, graph, cache, learning, storage, and connectivity health.
Start in three minutes
1. Scan a repository
npx rigour-scanRigour runs local quality, security, and AI-drift checks and returns an actionable result.
2. Add the Rigour loop
npx @rigour-labs/cli init
npx @rigour-labs/cli hooks init --tool cursor
npx @rigour-labs/cli skills install --target codex,cursor
npx @rigour-labs/cli checkhooks init supports Cursor, Claude Code, Cline, and Windsurf. It checks observable writes as agents work; check is the full project verification step.
3. Give every agent the same good workflow
rigour skills install --target codex,cursorRigour Skills turn its evidence loop into small, reusable agent workflows:
- rigour-context asks for the smallest explainable scope before an agent reads code.
- rigour-verify closes a change with proof and a Fix Packet repair loop.
- rigour-handoff transfers verified state without replaying an entire session.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Rigour: common questions
- Is Rigour MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the Rigour safety report
- How do I install Rigour?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Rigour need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Rigour maintained?
- The last commit was 32 days ago (2026-10-03). The latest release is v7.0.14.
- How does Rigour compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); github stars 27 (more than 91% of 28,688 servers); downloads a week 2,547 (more than 95% of 12,191 servers with a package). Full comparison.