Probe V0 vs verimcp
Probe V0 is an MCP server published by lexbritten. Marketplaces we read that list it: 1 (Official MCP Registry). verimcp is an MCP server published by rudranaresh0201. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-03. 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 |  Probe V0 |  verimcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.2 Downloads/month (PyPI): 89 Downloads/week (PyPI): 34 Forks (GitHub): 0 Stars (GitHub): 1 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 | Probe V0 | verimcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (probe-evidence.probe-lab.workers.dev/mcp) | On your machine (verimcp) |
| 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) | github.com/lexbritten/probe-mcp | github.com/rudranaresh0201/mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | 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
Probe V0
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
verimcp
Transparent MCP proxy that independently re-verifies tool-call claims before the Host trusts them.
How to run each
Probe V0 As a remote MCP server
claude mcp add --transport http probe https://probe-evidence.probe-lab.workers.dev/mcpverimcp As a local MCP server: PyPI package
claude mcp add --transport stdio verimcp -- uvx verimcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Probe V0 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: Probe V0 · What it can do: verimcp · 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.