Watchgoose vs MCP Registry Monitor
Watchgoose is an MCP server published by bartekrutkowski. Marketplaces we read that list it: 1 (Official MCP Registry). MCP Registry Monitor is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |   Watchgoose |  MCP Registry Monitor |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.3 Downloads/month (npm): 411 Downloads/week (npm): 59 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 32 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 | Watchgoose | MCP Registry Monitor |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 32 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release (differs) | 2026-10-24 | Not published |
| Where it runs (differs) | Remote server (mcp.watchgoose.com/mcp) | Not stated |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/bartekrutkowski/watchgoose-mcp | github.com/nirholas/mcp-notify |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-26 | no remote endpoint we check |
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
Watchgoose
Monitor cron jobs and recurring work through a project-scoped Watchgoose connection.
MCP Registry Monitor
Monitor MCP registry for new servers - Discord Slack notifications alerts
How to run each
Watchgoose As a remote MCP server
claude mcp add --transport http watchgoose-mcp https://mcp.watchgoose.com/mcpRequires: WATCHGOOSE_API_KEY (secret)
MCP Registry Monitor
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.
Only Watchgoose 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 MCP Registry Monitor publish no settings it asks for, so we do not compare settings.
What it can do: Watchgoose · What it can do: MCP Registry Monitor · Compare two other plugins
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.