VeyraX vs villager-hp
villager-hp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). villager-hp is a plugin bundle for AI coding tools published by Ash. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-19. 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 |  VeyraX | |
|---|---|---|
| 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 |
| Community marketplace ashley-pettit/villager-hp | Not listed | Removed on 2026-10-15 Version: 2.8.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 | VeyraX | villager-hpno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 48 | 0 |
| Pulls (Docker Hub) (differs) | 18 470 | 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) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| 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/ashley-pettit/villager-hp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
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 villager-hp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Save, search, and compile valuable knowledge from your Claude conversations.
-
View your Claude Rank stats, leaderboard position, badges, and usage history. Syncs Claude Code usage to clauderank.com.
-
Create Hevy routines and analyze your training from chat. Unofficial; BYO Hevy PRO API key.
-
Displays real-time usage percentages (5h session, 7d weekly, context window), reset countdowns, burn rate, and exhaustion prediction in your Claude Code terminal status line…
-
Mines every Claude Code session into a local SQLite database and provides a /mine skill with 18+ natural language query intents. Track costs, tokens, tools, projects, errors…
-
Hosted agent memory that learns from outcomes, with shared rooms. No key: mcp.mnemoverse.com/mcp
What each says it does
VeyraX
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
villager-hp
Your Claude session and weekly usage limits as an animated villager health card, with a weekly pace hourglass, rank badges and a death screen at 0 HP
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)
villager-hp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of villager-hp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of villager-hp publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: villager-hp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.