Veridu vs io.github.rigour-labs/rigour
Veridu is an MCP server published by michaelw-pr. 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: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
| Marketplace |  Veridu |  io.github.rigour-labs/rigour |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 No figure published Not marked · First seen |
Listed Version: 7.0.14 Downloads/month (npm): 24 335 Downloads/week (npm): 18 414 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
| Fact | Veridu | io.github.rigour-labs/rigour |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 29 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release (differs) | 2026-10-15 (worse) | 2026-10-19 (better) |
| Where it runs (differs) | Remote server (api.veridu.io/mcp) | On your machine (@rigour-labs/mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/rigour-labs/rigour |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 6 days ago, requires a key | no remote endpoint we check |
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
Veridu
Your agent verifies its change before commit; PR review that knows what depends on your change.
io.github.rigour-labs/rigour
Lets coding agents review their change, find an existing helper, and recall the team's lessons.
How to run each
Veridu As a remote MCP server
claude mcp add --transport http veridu https://api.veridu.io/mcpio.github.rigour-labs/rigour As a local MCP server: npm package
claude mcp add --transport stdio rigour -- npx -y @rigour-labs/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Veridu has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Veridu · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.