app.certman/server vs CorroborateMe
app.certman/server is an MCP server published by certman.app. Marketplaces we read that list it: 1 (Official MCP Registry). CorroborateMe is an MCP server published by cnrcode.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  app.certman/server |  CorroborateMe |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 0.1.4 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 | app.certman/server | CorroborateMe |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Remote server (mcp.certman.app) | Remote server (corroborateme.com/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 (differs) | Not stated | github.com/cnr-consulting/corroborate-me |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | Responded 37 h ago, requires a key |
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
app.certman/server
Create and manage your own Certificate Authority for internal HTTPS.
CorroborateMe
Prove end users to agents and apps: login-links, OIDC clients, and API keys over remote MCP
How to run each
app.certman/server As a remote MCP server
claude mcp add --transport http app-certman-server https://mcp.certman.appCorroborateMe As a remote MCP server
claude mcp add --transport http corroborateme https://corroborateme.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints 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: app.certman/server · What it can do: CorroborateMe · 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.