ssl-manager vs Upcheck
ssl-manager is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
ssl-manager is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. Upcheck is an MCP server published by upcheck.so. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Upcheck | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 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 | ssl-managerno longer listed · | Upcheck |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (mcp.upcheck.so/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 15 h ago, requires authentication |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of ssl-manager
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
sslwebsites io.github.jyswee/sslwebsites
SSL certificate management for coding agents. Issue, renew, monitor certs. 10 tools stdio.
-
GoGetSSL - read-only certificate expiry tracking, renewal prep (products, prices, DCV emails, CSR checks), and reseller balance and invoice reconciliation
-
Security grades, SSL/TLS, headers and uptime for your domains, plus a CI deploy gate.
-
mcp-ssl-inspector io.github.geekmarine/mcp-ssl-inspector
Audits TLS/SSL handshake latency, HSTS headers, and HTTPS availability on the edge.
-
ssl-cert-mcp io.github.mrfentmen/ssl-cert-mcp
Inspect TLS certificates of a host: issuer, expiry, and SAN. No key required.
-
Quick HTTPS/SSL check of any website, cybersecurity glossary and KrakenShield prices.
What each says it does
ssl-manager
Check SSL configs, generate renewal scripts, fix TLS settings
Upcheck
Monitor website uptime, SSL certificates, DNS, domain expiry and page changes, and manage alerts.
How to run each
ssl-manager
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Upcheck As a remote MCP server
claude mcp add --transport http upcheck https://mcp.upcheck.so/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Upcheck 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: ssl-manager · What it can do: Upcheck · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.