VeyraX vs Domain and Certificate Tracker MCP
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). Domain and Certificate Tracker MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-07. 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 |  VeyraX |  Domain and Certificate Tracker MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 842 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Forks (GitHub): 17 Stars (GitHub): 72 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 | VeyraX | Domain and Certificate Tracker MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 48 (worse) | 72 (better) |
| Pulls (Docker Hub) (differs) | 18 842 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 17 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/veyrax) | On your machine (https://github.com/Servosity/msp-skills/releases/download/domain-cert-tracker-v0.1.0/domain-cert-tracker-mcp.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 6, secrets among them: 2 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/servosity/msp-skills |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-11-06 |
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
VeyraX
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
Domain and Certificate Tracker MCP
Every client's domains and certificates in one inventory: what expires, unlocks or changes.
How to run each
VeyraX As a local MCP server: Docker image
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyraxRequires: VEYRAX_API_KEY (secret)
Domain and Certificate Tracker MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install domain-cert-tracker@msp-skillsRequires: DOMAIN_CERT_TRACKER_MCP_HTTP_TOKEN (secret), PRINTING_PRESS_CLIENT_PROFILE (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Domain and Certificate Tracker MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only VeyraX asks for
VEYRAX_API_KEY (secret)
Only Domain and Certificate Tracker MCP asks for
DOMAIN_CERT_TRACKER_BASE_URLDOMAIN_CERT_TRACKER_MCP_HTTP_TOKEN (secret)DOMAIN_CERT_TRACKER_MCP_READ_ONLYDOMAIN_CERT_TRACKER_NO_LOCAL_DATADOMAIN_CERT_TRACKER_USER_AGENTPRINTING_PRESS_CLIENT_PROFILE (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: VeyraX · What it can do: Domain and Certificate Tracker MCP · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.