Watchpup
REMOTE · WATCHPUP.WATCHPUP.WORKERS.DEV · SCANNED SEP 26
Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_monitor). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1197 tokens (~99/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Watchpup MCP server?
Watchpup is a hosted endpoint at https://watchpup.watchpup.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · watchpup.watchpup.workers.dev
claude mcp add --transport http dev-workers-watchpup-watchpup-watchpup 'https://watchpup.watchpup.workers.dev/mcp'
{
"mcpServers": {
"dev-workers-watchpup-watchpup-watchpup": {
"url": "https://watchpup.watchpup.workers.dev/mcp"
}
}
} {
"servers": {
"dev-workers-watchpup-watchpup-watchpup": {
"type": "http",
"url": "https://watchpup.watchpup.workers.dev/mcp"
}
}
} [mcp_servers.dev-workers-watchpup-watchpup-watchpup] url = "https://watchpup.watchpup.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-workers-watchpup-watchpup-watchpup": {
"type": "remote",
"url": "https://watchpup.watchpup.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-workers-watchpup-watchpup-watchpup --url 'https://watchpup.watchpup.workers.dev/mcp' --transport streamable-http
mcp_servers:
dev-workers-watchpup-watchpup-watchpup:
url: "https://watchpup.watchpup.workers.dev/mcp" {
"McpServers": {
"dev-workers-watchpup-watchpup-watchpup": {
"Transport": "http",
"Url": "https://watchpup.watchpup.workers.dev/mcp"
}
}
} assistant mcp add dev-workers-watchpup-watchpup-watchpup -t streamable-http -u 'https://watchpup.watchpup.workers.dev/mcp'
{
"mcpServers": {
"dev-workers-watchpup-watchpup-watchpup": {
"type": "http",
"url": "https://watchpup.watchpup.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 0
- Stability: 0.97 → pass security
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- First check of Injection markers: pass security
- First check of Judged manipulation: pass security
- Tool “check_url” rewrote its description, which is the text the model reads security
- Schema quality: 90 → 99 ▼ functional
- First check of Destructive annotations: 100 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 1.0.0 → 1.1.0 functional
- “check_url” added an optional parameter “kind” cosmetic
- “check_url” reworded the description of “url” cosmetic
- “create_monitor” reworded the description of “kind” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://watchpup.watchpup.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=watchpup.workers.dev | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 65aa6c2949a061e213b0b5355fefa32a |
| SANs: watchpup.workers.dev, *.watchpup.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of watchpup.watchpup.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://watchpup.watchpup.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://watchpup.watchpup.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ack_incident Acknowledge an incident ~74
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 reminders).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Incident id (from list_incidents) |
| un | boolean | – | true = remove an existing acknowledgement |
No output schema declared.
No examples provided.
add_incident_note Add a postmortem note to an incident ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Incident id (from list_incidents) |
| note | string | yes | The note text ("" clears) |
No output schema declared.
No examples provided.
check_url Instant URL check (no account needed) ~172
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 streamable-HTTP MCP server endpoint and reports the server’s self-declared name/version/protocol — useful to tell "the MCP server is down" from "my client is misconfigured". Works without an API key (rate limit 30/hour per IP). For continuous monitoring with alerts, use create_monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | What to speak: plain HTTP (default) or an MCP initialize handshake |
| url | string | yes | Public http(s) URL to check, e.g. https://example.com — for kind=mcp the MCP endpoint URL, e.g. https://mcp.deepwiki.com/mcp |
No output schema declared.
No examples provided.
create_monitor Create a monitor ~304
Create a monitor. kind=http (needs url), tcp (target "host:port"), tls (target host[:port] — cert-expiry watch), domain (target — registration-expiry via RDAP), dns (target + rtype A/AAAA/MX/... , optional expect_value), heartbeat (dead-man’s switch for cron jobs/agent loops: needs name; response includes ping_url to curl from the job, and a ping_email address). Common options: name, interval (seconds, min 60), tags. http options: expect ("2xx,301"), keyword, keyword_absent:"absent", slow_ms (number or "auto"), method, headers, body, json_path/json_expect, header_name/header_expect. heartbeat options: grace (seconds), cron ("0 3 * * *") + tz, max_duration_s. Any other documented field (see /llms.txt) also works — extra properties are passed through.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | integer | – | Check interval in seconds, min 60 (heartbeat: expected ping interval) |
| kind | string | – | Monitor kind (default http; "mcp" monitors an MCP server via JSON-RPC initialize) |
| name | string | – | Display name (required for heartbeat, defaults to the target host otherwise) |
| target | string | – | For tcp/tls/domain/dns: host[:port] or domain name |
| url | string | – | For kind=http: the URL to check |
No output schema declared.
No examples provided.
delete_monitor Delete a monitor ~37
Permanently delete a monitor and all its check history, events and rollups. Cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id |
No output schema declared.
No examples provided.
get_account Account overview ~33
Who am I: account email, monitor count/limit, plan limits. Good first call to verify the API key works.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_monitor Get one monitor ~64
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_url and ping_email.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id (from list_monitors) |
No output schema declared.
No examples provided.
get_status_page Read a public status page ~56
Machine-readable state of any public Watchpup status page by slug: per-monitor status, uptime, incidents last 30d. No API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Status page slug (the part after /s/) |
No output schema declared.
No examples provided.
list_channels List alert channels ~35
Alert delivery channels on the account (email / webhook / Discord / Slack / ntfy / Telegram), their verification state and delivery health.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_incidents List incidents ~53
Downtime incidents (ongoing and resolved) across all monitors: start, duration, cause, acknowledgement, notes.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days, 1-90 (default 30) |
No output schema declared.
No examples provided.
list_monitors List monitors ~64
List all monitors on the account: current up/down status, kind, target, interval, last check. Optionally filter by tag.
| Name | Type | Req | Description |
|---|---|---|---|
| tag | string | – | Only monitors carrying ALL these tags (comma-separated), e.g. "prod" or "prod,eu" |
No output schema declared.
No examples provided.
update_monitor Update / pause / resume a monitor ~92
PATCH any monitor field: name, url, target, interval, expect, keyword, slow_ms, grace, cron, tags, sla_target, renotify, channels (alert routing)... Pause with {"status":"paused"}, resume with {"status":"new"}. Empty string clears optional fields.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id |
| status | string | – | "paused" stops checking; "new" resumes |
No output schema declared.
No examples provided.
What is the Watchpup MCP server?
Watchpup is an MCP server listed in the public MCP registry as dev.workers.watchpup.watchpup/watchpup. Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts. This page covers its hosted endpoint (https://watchpup.watchpup.workers.dev/mcp).
Is the Watchpup MCP server safe to use?
Watchpup scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Watchpup MCP server expose?
Watchpup exposes 12 tools: check_url, list_monitors, get_monitor, create_monitor, update_monitor, and 7 more. Their descriptions and schemas cost roughly 1,057 tokens of context every time the server is loaded.
Does the Watchpup MCP server require authentication?
No. We connected to Watchpup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Watchpup MCP server still maintained?
Watchpup is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.