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/mrnh/rigorWrote 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/mrnh/rigor/rigor-mcp)<a href="https://agentmods.dev/mcp/mrnh/rigor/rigor-mcp"><img src="https://agentmods.dev/badge/mcp/mrnh/rigor/rigor-mcp/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/mrnh/rigor/rigor-mcp"><img src="https://agentmods.dev/badge/mcp/mrnh/rigor/rigor-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rigor-mcp 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 1mo 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
{
"rigor-mcp": {
"command": "uvx",
"args": [
"rigor-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.
- 1mo ago First seen · 9 lines scan A b2d0be6d81b5
rigor-mcp is an MCP server published in the GitHub repository mrnh/rigor (1 stars, last pushed 1mo 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-31.
Other mcp servers, from other repositories
gods-eye-geospatial-mcp
Gods Eye — civilian open-source geospatial awareness MCP. Wraps open-licence APIs (ESA Copernicus Sentinel-1/2/3/5p, OpenStreetMap, Overture, Ordnance Survey UK, INSPIRE EU, DEFRA) behind the MEOK Care Membrane ethics gate. For AI-agent situational awareness, environmental compliance, disaster response, agriculture.…
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.
mcp-synology
MCP server for Synology NAS — manage files on your NAS via Claude. Runs locally from the mcp-synology Python package.
swag-mcp
MCP server "swag-mcp", hosted remotely, as configured in jmagar/swag-mcp.
cdc-health-mcp-server
Search and query CDC public health data — mortality, vaccinations, surveillance, behavioral risk. Runs locally from the @cyanheads/cdc-health-mcp-server npm package. Needs 2 environment variables to run.
wet-mcp
Open-source MCP Server for web search, extract, crawl, academic research, and library docs with embedded SearXNG. Runs locally from the wet-mcp Python package. Needs 2 environment variables to run.