Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/rigour-labs/rigourWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/rigour-labs/rigour/rigour-mcp-rigour)<a href="https://agentmods.dev/mcp/rigour-labs/rigour/rigour-mcp-rigour"><img src="https://agentmods.dev/badge/mcp/rigour-labs/rigour/rigour-mcp-rigour/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/rigour-labs/rigour/rigour-mcp-rigour"><img src="https://agentmods.dev/badge/mcp/rigour-labs/rigour/rigour-mcp-rigour.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rigour scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"rigour": {
"command": "npx",
"args": [
"-y",
"@rigour-labs/mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 10 lines scan A e735a86c1616
rigour is an MCP server published in the GitHub repository rigour-labs/rigour (26 stars, last pushed 19d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
vitest
A Model Context Protocol server for Vitest test execution and management. Runs locally from the @djankies/vitest-mcp npm package.
mcp-devtools
MCP server "mcp-devtools" as configured in rshade/mcp-devtools-server. Launched with ./start-mcp.sh. Needs 1 environment variable to run.
mcp
Visual-diff & change-detection tools that catch agentic UI drift for coding agents. Runs locally from the @corralimited/snapdiff-mcp npm package. Needs 2 environment variables to run.
test-intel
Coverage analysis, untested function detection and complexity scoring for TS and JS. Runs locally from the @barissozudogru/test-intel-mcp npm package.
forkflux-mcp
Model Context Protocol (MCP) adapter for ForkFlux, enabling AI coding assistants to securely publish and claim jobs. Runs locally from the forkflux-mcp Python package. Needs 2 environment variables to run.
mockpost
Local multi-channel message emulator for E2E testing, with an MCP server for LLM agents. Runs locally from the mockpost Python package. Needs 1 environment variable to run.