Ext Ops Panel
Open dashboard
Comparison

Curate-Ipsum vs io.github.rigour-labs/rigour

Curate-Ipsum is an MCP server published by egoughnour. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.rigour-labs/rigour is an MCP server published by rigour-labs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceCurate-Ipsumio.github.rigour-labs/rigour
Official MCP Registry Listed
Version: 2.5.1
Downloads/month (PyPI): 123
Downloads/week (PyPI): 21
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 7.0.14
Downloads/month (npm): 9 547
Downloads/week (npm): 1 425
Forks (GitHub): 1
Stars (GitHub): 29
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 7.0.14
Downloads/month (npm): 9 547
Downloads/week (npm): 1 425
Forks (GitHub): 1
Stars (GitHub): 29
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Curate-Ipsum vs io.github.rigour-labs/rigour
FactCurate-Ipsumio.github.rigour-labs/rigour
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)29 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)Not published2026-10-19
Where it runs (differs)On your machine (curate-ipsum)On your machine (@rigour-labs/mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 0Not published
Licence (differs)Not statedMIT
Repository (differs)github.com/egoughnour/curate-ipsumgithub.com/rigour-labs/rigour
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Curate-Ipsum

In its own words, on Official MCP Registry:

Code synthesis through belief revision, mutation testing, and verification

io.github.rigour-labs/rigour

In its own words, on Official MCP Registry:

Lets coding agents review their change, find an existing helper, and recall the team's lessons.

How to run each

Curate-Ipsum As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio curate-ipsum -- uvx curate-ipsum

io.github.rigour-labs/rigour As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio rigour -- npx -y @rigour-labs/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.rigour-labs/rigour publish no settings it asks for, so we do not compare settings.

What it can do: Curate-Ipsum · What it can do: io.github.rigour-labs/rigour · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built