# dev.workers.watchpup.watchpup/watchpup

Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.0
- **Author:** dev.workers.watchpup.watchpup
- **License:** Unknown
- **Endpoints:** streamable-http https://watchpup.watchpup.workers.dev/mcp
- **Source:** https://watchpup.watchpup.workers.dev
- **Endpoint health:** reachable (last checked 2026-09-21T22:15:10.663Z, 5 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 content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-21T22:15:10.663Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.
**Findings**
- injection-shaped content (note) in the `check_url` tool: Links to undeclared domains: example.com, mcp.deepwiki.com

## Tools

12 declared. Observed from a live `tools/list` probe.
- `check_url` — Check any public URL RIGHT NOW: is it up, HTTP status, response time in ms. With kind:"mcp" it instead performs a real JSON-RPC initialize handshake against a s
- `list_monitors` — List all monitors on the account: current up/down status, kind, target, interval, last check. Optionally filter by tag.
- `get_monitor` — Full detail for one monitor: status, config, 24h latency percentiles and trend (http/tcp), SLA budget if a target is set. Heartbeat monitors include their ping_
- `create_monitor` — Create a monitor. kind=http (needs url), tcp (target "host:port"), tls (target host[:port] — cert-expiry watch), domain (target — registration-expiry via RDAP),
- `update_monitor` — PATCH any monitor field: name, url, target, interval, expect, keyword, slow_ms, grace, cron, tags, sla_target, renotify, channels (alert routing)... Pause with 
- `delete_monitor` — Permanently delete a monitor and all its check history, events and rollups. Cannot be undone.
- `list_incidents` — Downtime incidents (ongoing and resolved) across all monitors: start, duration, cause, acknowledgement, notes.
- `ack_incident` — Mark an ongoing incident as "someone is on it" — pauses still-down reminder alerts for that monitor until recovery. Set un=true to un-acknowledge (re-arms remin
- `add_incident_note` — Attach/replace a note (max 500 chars) on an incident. Notes publish with the incident on public status pages, their JSON and the Atom feed. Empty string clears.
- `list_channels` — Alert delivery channels on the account (email / webhook / Discord / Slack / ntfy / Telegram), their verification state and delivery health.
- `get_status_page` — Machine-readable state of any public Watchpup status page by slug: per-monitor status, uptime, incidents last 30d. No API key needed.
- `get_account` — Who am I: account email, monitor count/limit, plan limits. Good first call to verify the API key works.

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"watchpup\": {\n      \"type\": \"http\",\n      \"url\": \"https://watchpup.watchpup.workers.dev/mcp\"\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on someone else's infrastructure.
- Floor 32, ceiling 56 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- 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/dev.workers.watchpup.watchpup%2Fwatchpup
- Install plan: https://forgeregistry.com/api/v1/packages/dev.workers.watchpup.watchpup%2Fwatchpup/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/dev.workers.watchpup.watchpup%2Fwatchpup
- HTML page: https://forgeregistry.com/registry/dev.workers.watchpup.watchpup%2Fwatchpup
- 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.