Rigour

Created By
rigour-labs4 months ago
Deterministic quality gates for AI coding agents. Rigour runs 23 automated checks on every file AI writes — structural analysis, security scanning, AI-drift detection, and agent governance. Works as an MCP server for Claude Desktop, Cursor, and Cline. Supports TypeScript, JavaScript, Python, Go, Ruby, and C#. Forces AI agents to write production-grade code with PASS/FAIL enforcement.
Overview

Paste this in the Content field:

# Rigour — Deterministic Quality Gates for AI Coding Agents

Rigour is an MCP server that forces AI agents to write production-grade code. It runs 23 automated quality checks on every file the agent writes, returning PASS/FAIL results that the agent must address before proceeding.

## Why Rigour?

AI coding agents (Claude, GPT, Copilot) generate code fast — but without quality enforcement. Rigour acts as a leash, not a suggestion. Every file gets scanned for:

- **Structural issues**: file size, cyclomatic complexity, deep nesting, long functions
- **Security vulnerabilities**: SQL injection, XSS, hardcoded secrets, command injection, path traversal
- **AI-drift patterns**: duplicated functions across files, hallucinated imports, context window quality degradation, inconsistent error handling
- **Agent governance**: retry loop breaking, checkpoint enforcement, environment alignment

## Two-Score System

Every scan produces:
- **AI Health Score** — measures AI-specific code quality (drift, hallucinations, async safety)
- **Structural Score** — measures traditional code quality (complexity, size, patterns)

Both scores use severity-weighted deductions: critical issues cost 20 points, high costs 10, medium costs 5.

## Quick Start

Add to your Claude Desktop or Cursor config:

```json
{
  "mcpServers": {
    "rigour": {
      "command": "npx",
      "args": ["-y", "@rigour-labs/mcp"]
    }
  }
}

Supported Languages

TypeScript, JavaScript, Python, Go, Ruby, C#

Server Config

{
  "mcpServers": {
    "rigour": {
      "command": "npx",
      "args": [
        "-y",
        "@rigour-labs/mcp"
      ]
    }
  }
}
Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
rigour-labs
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago