Watchgoose
io.github.bartekrutkowski/watchgoose-mcp
About Watchgoose
Watchgoose is an MCP server published by the GitHub account bartekrutkowski. Monitor cron jobs and recurring work through a project-scoped Watchgoose connection.
It runs on your own machine: your AI client starts it from the npm package watchgoose-mcp at version 1.1.3, or you can connect to the hosted version instead.
It asks for one secret: WATCHGOOSE_API_KEY. Give it a key with the least access that still works.
Version 1.1.3 was published on 24 October 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 10 automated checks on the registry entry and the package code: 8 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
WATCHGOOSE_API_KEY | Yes | Yes | Project-scoped Watchgoose API key: hcr_ read-only or hcw_ read-write. |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/bartekrutkowski/watchgoose-mcp |
| Version pinned | Pass | Every package has an explicit version |
| Remote uses HTTPS | Pass | All remote endpoints use https:// |
| Secrets requested | Info | Asks for 1 secret: WATCHGOOSE_API_KEY |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account bartekrutkowski |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | watchgoose-mcp@1.1.3 runs nothing at install |
| Code red flags | Pass | Read 3 files in watchgoose-mcp@1.1.3: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 3 files, including comments and the README |
Popularity & health: 53 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
0 forks, 0 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.bartekrutkowski/watchgoose-mcp |
|---|---|
| Publisher | GitHub account bartekrutkowski |
| How the name is verified | Name verified via GitHub account bartekrutkowski. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local package and a hosted remote |
| Packages | npm watchgoose-mcp 1.1.3 (stdio) |
| Remote endpoints | streamable-http https://mcp.watchgoose.com/mcp |
| Version | 1.1.3 |
| Published | |
| Last updated | |
| Source repository | https://github.com/bartekrutkowski/watchgoose-mcp |
| Website | https://watchgoose.com/docs/mcp/ |
| Category | Analytics & monitoring (assigned by keyword rule, not by hand) |
Related servers in Analytics & monitoring
- Honeybadger3/3Debug errors, query logs, create alarms, and monitor cron jobs from…
- Industrial Platform Web Monitor4/4Recurring webpage change, price, inventory and metadata monitoring…
- Website Change Monitor & Deterministic Diff4/4Deterministic webpage change detection, hashes and text diffs for…
- Tachyon GPU monitor6/6Read-only NVIDIA GPU monitor: bottlenecks, VRAM forecast, crash…
- mcp-meta-ad-library-monitor7/7Find a company active Facebook and Instagram ads through the Meta…
- website-change-monitor4/4Track page and price changes over time: diffs, history, and alerts…