# watchgoose-mcp

Monitor cron jobs and recurring work through a project-scoped Watchgoose connection.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.2
- **Author:** io.github.bartekrutkowski
- **License:** MIT
- **npm:** watchgoose-mcp
- **Endpoints:** streamable-http https://mcp.watchgoose.com/mcp
- **Source:** https://github.com/bartekrutkowski/watchgoose-mcp
- **Endpoint health:** reachable (last checked 2026-09-22T22:05:25.683Z, 3 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 18 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-05T20:22:02.146Z
- **Version scanned:** 0.1.2
- **CVEs:** none found by OSV at scan time

## Tools

10 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_checks` — List checks in this Watchgoose project, optionally filtered by slug or tags. A successful ping arms a new check; Watchgoose then expects the next success within
- `get_check` — Get one check by its stable unique_key, including its current state and schedule. Cron and OnCalendar checks use schedule plus grace; simple checks use timeout 
- `list_pings` — List recent signals for a check, newest first. Success arms or advances monitoring, /fail records failure, and /start begins runtime measurement. Source address
- `list_flips` — List retained status changes for a check, newest first, with optional time filters. In results, up: 1 means the check became up; up: 0 means any other status, i
- `list_channels` — List integration names and kinds available for check notifications. Only exact, unique integration names can be assigned to checks.
- `create_check` — Create a simple timeout check or a cron/OnCalendar schedule check. All fields are optional; schedule takes precedence over timeout. The new check remains unarme
- `update_check` — Update selected fields on an existing check. Omitted fields remain unchanged; schedule takes precedence over timeout, and integration names must match exactly.
- `pause_check` — Pause monitoring without deleting the check. Unless manual_resume is enabled, a later ping can automatically resume a paused check.
- `resume_check` — Resume a paused check and return it to the new state. The next successful ping arms its monitoring schedule.
- `delete_check` — Permanently delete a check and its retained monitoring history. This cannot be undone.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"watchgoose\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"watchgoose-mcp\"\n      ],\n      \"env\": {\n        \"WATCHGOOSE_API_KEY\": \"<YOUR_WATCHGOOSE_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `WATCHGOOSE_API_KEY` — Watchgoose API Key (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; runs locally and hosted.
- Floor 55, ceiling 55 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/watchgoose-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/watchgoose-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/watchgoose-mcp
- HTML page: https://forgeregistry.com/registry/watchgoose-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.