com.robinsaige/verifier vs MCP Registry Validator — Check Endpoints Actually Resolve
com.robinsaige/verifier is an MCP server published by robinsaige.com. Marketplaces we read that list it: 1 (Official MCP Registry). MCP Registry Validator — Check Endpoints Actually Resolve is an MCP server published by operatorsheets. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  com.robinsaige/verifier | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 No figure published Not marked · First seen |
Listed, marked deprecated Version: 0.2.1 No figure published 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 | com.robinsaige/verifier | MCP Registry Validator — Check Endpoints Actually Resolve |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (robinsaige.com/mcp) | Remote server (mcp-uptime.theopslog.workers.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-23 | Answered with HTTP 404 (6 days ago) |
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
com.robinsaige/verifier
MCP tool observatory: do registry servers answer, and are their answers true? No key.
MCP Registry Validator — Check Endpoints Actually Resolve
Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.
How to run each
com.robinsaige/verifier As a remote MCP server
claude mcp add --transport http verifier https://robinsaige.com/mcpMCP Registry Validator — Check Endpoints Actually Resolve As a remote MCP server
claude mcp add --transport http mcp-uptime https://mcp-uptime.theopslog.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Neither endpoint responded at the last daily 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: com.robinsaige/verifier · What it can do: MCP Registry Validator — Check Endpoints Actually Resolve · 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.