Rigour MCP server

Read from the package source without running it. The installed server may list more.

• rigour_agent_deregister

  Deregister an agent from the multi-agent session. Use when an agent completes its work or needs to release its scope for another agent.

• rigour_agent_register

  Register an agent in a multi-agent session. Use this at the START of agent execution to claim task scope and enable cross-agent conflict detection. Required for Agent Team Governance.

• rigour_cache_stats

  Returns detailed performance stats across all 4 cache layers (exact hits, semantic hits, partial hits, misses, hit rate, tokens served from cache).

• rigour_checkwrite action

  Run quality gate checks on the project. MUST be called before declaring any coding task complete. Checks code complexity, file size, required docs, security patterns, and more. Returns PASS or FAIL with details. **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 structured fix instructions with exact fil

• rigour_check_deepwrite action

  Run quality gates WITH deep LLM-powered analysis. Three-step pipeline: AST extracts facts → LLM interprets → AST verifies. Local-first by default (Qwen2.5-Coder-0.5B lite sidecar), or bring your own API key for any cloud provider.

• rigour_check_pattern

  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_checkpoint

  Record a quality checkpoint during long-running agent execution. Use periodically (every 15-30 min) to enable drift detection, quality monitoring, and compact subagent handoffs. Triggers incremental pattern index refresh when filesChanged is provided. Essential for GPT-5.3 coworking mode — call BEFORE rigour_handoff to compress context under 2K tokens.

• rigour_context_explain

  Audits why specific files/services were included or excluded, cache hit/miss status, invalidation reasons, and prior agent requests.

• rigour_context_scope

  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.

• rigour_context_stats

  Returns context retrieval efficiency, candidate tokens vs returned tokens, potential avoided tokens, cache hit rate, and repeated reads prevented.

• rigour_deep_stats

  Get deep analysis statistics from SQLite storage. Returns recent scan scores, top issues, and score trends for a repository.

• rigour_explain

  Explain WHY quality gates failed in human-readable language. Use this to understand the reasoning behind each violation before fixing. For machine-readable fix instructions, use rigour_get_fix_packet instead.

• rigour_forgetwrite action

  Remove a stored memory by key.

• rigour_get_config

  Returns the current Rigour configuration (rigour.yml) for agent reasoning.

• rigour_get_fix_packet

  Call this after rigour_check returns FAIL. Returns a prioritized Fix Packet with exact violations, file locations, and step-by-step fix instructions. Apply fixes in severity order (critical first), then re-run rigour_check to verify. Repeat until PASS. **After applying all fixes, tell the user what Rigour caught and that fixes were applied.**

• rigour_handoff

  Handoff task to another agent in a multi-agent workflow. Use when delegating a subtask or completing your scope. Enables verified handoff governance.

• rigour_handoff_accept

  Accept a pending handoff from another agent. Use to formally acknowledge receipt of a task and verify you are the intended recipient.

• rigour_hooks_checkwrite action

  Run the fast hook checker on specific files. Same checks that run inside IDE hooks (Claude, Cursor, Cline, Windsurf). Catches: hardcoded secrets, hallucinated imports, command injection, file size. Completes in <100ms. NEW: Pass 'text' param for DLP mode — scans user input for credentials (AWS keys, API tokens, database URLs, private keys, JWTs) before agent processing.

• rigour_hooks_init

  Generate hook configs for AI coding tools (Claude, Cursor, Cline, Windsurf). Installs real-time quality checks and non-blocking DLP credential warnings by default. Pass dlp=false to disable DLP hooks only.

• rigour_index

  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. Use semantic=true for embedding-based search.

• rigour_list_gates

  Lists all configured quality gates and their thresholds for the current project.

• rigour_mcp_get_settings

  Get Rigour MCP runtime settings for this repository (.rigour/mcp-settings.json).

• rigour_mcp_set_settings

  Set Rigour MCP runtime settings for this repository. Currently supports deep_default_mode: off | quick | full.

• rigour_recall

  Load project memory and stored conventions. CALL THIS at the START of every coding task (before reading files) to restore team decisions, naming conventions, and architectural preferences. Returns index health status and uses semantic cache on repeat calls — second recall with the same key is served from cache.

• rigour_remember

  Store a persistent instruction or context that the AI should remember across sessions. Use this to persist user preferences, project conventions, or critical instructions. IMPORTANT: You must provide both 'key' (a short snake_case identifier) and 'value' (the full text to remember).

• rigour_review

  Perform a high-fidelity code review on a pull request diff. Analyzes changed files using all active quality gates.

• rigour_runwrite action

  Execute a command under Rigour supervision. This tool can be INTERCEPTED and ARBITRATED by the Governance Studio.

• rigour_run_supervisedwrite action

  Run a command under FULL Supervisor Mode. Iteratively executes the command, checks quality gates, and returns fix packets until PASS or max retries reached. Use this for self-healing agent loops.

• rigour_security_auditwrite action

  Runs a live security audit (CVE check) on the project dependencies.

• rigour_status

  Quick PASS/FAIL check with JSON-friendly output for polling current project state.

• rigour_task_cost

  Returns both verified actual model usage/cost (from Cursor Admin API or imported CSV) and Rigour estimated avoided context/cost USD.

• Code scan59 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 5 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

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, Claude Desktop or Cursor 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 5 days ago (2026-09-14). The latest release is v6.2.2.