villager-hp vs Mnemoverse Memory
villager-hp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
villager-hp is a plugin bundle for AI coding tools published by Ash. No marketplace we read lists it any more. Mnemoverse Memory is an MCP server published by mnemoverse. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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 |  Mnemoverse Memory | |
|---|---|---|
| Community marketplace ashley-pettit/villager-hp | Removed on 2026-10-15 Version: 2.8.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.17.0 Downloads/month (npm): 1 590 Downloads/week (npm): 594 Forks (GitHub): 5 Stars (GitHub): 27 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.16.0 Downloads/month (npm): 1 590 Downloads/week (npm): 594 Forks (GitHub): 5 Stars (GitHub): 27 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 | villager-hpno longer listed · | Mnemoverse Memory |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 0 | 27 |
| Forks (GitHub) (differs) | 0 | 5 |
| Last release (differs) | Not published | 2026-10-30 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/ashley-pettit/villager-hp | github.com/mnemoverse/mcp-memory-server |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 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 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.
-
Lets Claude check its own claude.ai plan quota: percent used of the session and weekly limits (including per-model weekly limits), when each resets, and where usage is on pace to…
-
Create Hevy routines and analyze your training from chat. Unofficial; BYO Hevy PRO API key.
-
A virtual pet above your prompt that grows from the work Claude does: evolves by what Claude does most, gets sick from tool errors, plays mini games, and spends coins in a shop…
-
Log meals, weight and workouts in Hearth and review your progress. Subscription required.
-
Search and read the Claude Platform documentation and API reference.
What each says it does
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
Mnemoverse Memory
Hosted agent memory that learns from outcomes, with shared rooms. No key: mcp.mnemoverse.com/mcp
How to run each
villager-hp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Mnemoverse Memory As a remote MCP server
claude mcp add --transport http mcp-memory-server https://mcp.mnemoverse.com/mcpRequires: MNEMOVERSE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Mnemoverse Memory 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
The marketplaces of villager-hp publish no settings it asks for, so we do not compare settings.
What it can do: villager-hp · What it can do: Mnemoverse Memory · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.