villager-hp vs BotClaw · Agent Observer
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. BotClaw · Agent Observer is an MCP server published by botclaw.tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 | ||
|---|---|---|
| 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: 1.2.0 No figure published 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 · | BotClaw · Agent Observer |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (botclaw.tech/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ashley-pettit/villager-hp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago |
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.
-
Search and read the Claude Platform documentation and API reference.
-
Screenshots MCP by InsightfulPipe
Hosted Screenshots MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
-
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…
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
BotClaw · Agent Observer
Read-only agent radar, weekly editions, sourced guides, scenario choices and revision sync.
How to run each
villager-hp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
BotClaw · Agent Observer As a remote MCP server
claude mcp add --transport http agent-observer https://botclaw.tech/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only BotClaw · Agent Observer 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
Neither one's marketplaces publish the settings it asks for.
What it can do: villager-hp · What it can do: BotClaw · Agent Observer · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.