VeyraX vs Vitafin
VeyraX is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
VeyraX is an MCP server published by VeyraX. No marketplace we read lists it any more. Vitafin is an MCP server published by vitafin.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  Vitafin | |
|---|---|---|
| Docker MCP Catalog | Removed on 2026-10-26 Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 659 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 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 | VeyraXno longer listed · | Vitafin |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 48 | 0 |
| Pulls (Docker Hub) (differs) | 18 659 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/veyrax) | Remote server (vitafin.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/hakki123mrk/vitafin-plugin |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
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 VeyraX
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Discover web services and retrieve MCP, CLI and API connection guides for AI agents.
-
Find MCP servers, APIs, tools and skills by intent. Free key: POST /api/agents/register
-
vivesca io.github.terry-li-hm/vivesca
Opinionated MCP server — Pydantic output schemas, 7 domains, built to evolve.
-
Secure and manage MCP servers through the Speakeasy AI Control Plane from your agent.
-
Debug background jobs — runs, traces, spans, schedules, queues and deployments.
-
forai.tools — let your agent find the right tool
Lets your agent find the right MCP server, tool or service for a task, in one call. Ads labelled.
What each says it does
VeyraX
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
Vitafin
Money tracker, every account in its own currency: cards, loans, budgets, bills, splits, net worth.
How to run each
VeyraX
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Vitafin As a remote MCP server
claude mcp add --transport http vitafin https://vitafin.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vitafin has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Vitafin publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Vitafin publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: Vitafin · 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.