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.
npx agentmods add mcp/mrnh/rigor/rigor-mcpgit 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.svg" alt="Measured on agentmods" 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 4d 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.
- 4d 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 16d 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
pubmed-mcp-server
Search PubMed/Europe PMC, fetch articles and full text (PMC/EPMC/Unpaywall), citations, MeSH terms. Runs locally from the @cyanheads/pubmed-mcp-server npm package. Needs 4 environment variables to run.
patent-literature-search-mcp
Search 200M+ patents and 216M+ scientific papers using natural language and structured filters. Remote server at connect.patsnap.com.
pubcrawl
PubMed & Europe PMC literature search, US/UK drug labelling, and clinical trials for AI assistants. Runs locally from the @pharmatools/pubcrawl npm package. Needs 1 environment variable to run.
openfda-mcp-server
Query FDA data on drugs, food, devices, and recalls via openFDA. STDIO or Streamable HTTP. Runs locally from the @cyanheads/openfda-mcp-server npm package. Needs 8 environment variables to run.
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.
regen-compute
Regenerative AI — fund verified ecological regeneration from your AI sessions via Regen Network. Estimate your footprint, browse carbon and biodiversity credits, and retire them on-chain via credit card. Runs locally from the regen-compute npm package.