VeyraX vs PetKit
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). PetKit is an MCP server published by dirkjanfaber. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  PetKit |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 470 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.1 Downloads/month (npm): 779 Downloads/week (npm): 43 Forks (GitHub): 0 Stars (GitHub): 0 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 | PetKit |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 48 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 18 470 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/veyrax) | On your machine (mcp-server-petkit) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/dirkjanfaber/mcp-server-petkit |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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.
PetKit
Unofficial MCP server for PetKit smart feeders: status, feeding history and schedule control.
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)
PetKit As a local MCP server: npm package
claude mcp add --env "PETKIT_EMAIL=<YOUR_PETKIT_EMAIL>" --env "PETKIT_PASSWORD=<YOUR_PETKIT_PASSWORD>" --env "PETKIT_REGION=<YOUR_PETKIT_REGION>" --transport stdio mcp-server-petkit -- npx -y mcp-server-petkitRequires: PETKIT_EMAIL, PETKIT_PASSWORD (secret), PETKIT_REGION
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of PetKit publish no list of tools, so we do not compare tools.
Settings each asks for
Only VeyraX asks for
VEYRAX_API_KEY (secret)
Only PetKit asks for
PETKIT_EMAILPETKIT_PASSWORD (secret)PETKIT_REGIONPETKIT_TIMEZONE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: VeyraX · What it can do: PetKit · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.