Watchpup
REMOTE · WATCHPUP.WATCHPUP.WORKERS.DEV · SCANNED AUG 8
Free uptime monitoring: HTTP/TCP/TLS/DNS checks, cron heartbeats, status pages, incident tools.
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 →
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 not yet verified: we couldn't determine whether a plaintext access path exists. 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1084 tokens (~90/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · watchpup.watchpup.workers.dev
claude mcp add --transport http dev-workers-watchpup-watchpup-watchpup 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": {
"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.
- 8 Aug 26 59
First indexed and scored.
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 8 Aug 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 |
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 |
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.
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) ~73
Check any public URL RIGHT NOW: is it up, HTTP status, response time in ms. Works without an API key (rate limit 10/hour per IP). For continuous monitoring with alerts, use create_monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL to check, e.g. https://example.com |
No output schema declared.
No examples provided.
create_monitor Create a monitor ~290
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) |
| 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.