mcpbeat Sign in

Watchpup MCP Server

by workers-watchpup-watchpup Your server? Claim it
not responding

Watchpup is listed as active in the registry but did not answer our last check. It exposes 12 tools.

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

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 92 checks
12
Tools
read from the server
80 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 26 August 2026. No other catalogue keeps this.

26 Aug a tool description was rewritten2 times that day check_url
26 Aug 2 tools changed the parameters they ask for check_url, create_monitor
26 Aug a tool changed version
and 1 more, back to 26 August 2026

Watchpup does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add watchpup --transport http https://watchpup.watchpup.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://watchpup.watchpup.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.watchpup]
url = "https://watchpup.watchpup.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "watchpup": {
      "url": "https://watchpup.watchpup.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "watchpup": {
      "type": "http",
      "url": "https://watchpup.watchpup.workers.dev/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

monitor
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), 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.
delete_monitor
Permanently delete a monitor and all its check history, events and rollups. Cannot be undone.
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_url and ping_email.
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 {"status":"paused"}, resume with {"status":"new"}. Empty string clears optional fields.
account
get_account
Who am I: account email, monitor count/limit, plan limits. Good first call to verify the API key works.
ack
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 reminders).
channels
list_channels
Alert delivery channels on the account (email / webhook / Discord / Slack / ntfy / Telegram), their verification state and delivery health.
incident
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.
incidents
list_incidents
Downtime incidents (ongoing and resolved) across all monitors: start, duration, cause, acknowledgement, notes.
monitors
list_monitors
List all monitors on the account: current up/down status, kind, target, interval, last check. Optionally filter by tag.
status
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.
url
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 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.

Endpoints

URLTransportStateLatencyChecked
https://watchpup.watchpup.workers.dev/mcp streamable-http answering 80 ms 0 min ago

Alternatives to Watchpup

same job, measured the same way
Pingwell
by pingwell

Uptime checks, cron heartbeats, status pages and alerts, set up by your agent.

answering
Vantaj
by vantaj

Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.

13 tools answering
Tá Rodando
by com-tarodando

Uptime monitoring and public status page: HTTP monitors, down/up alerts and incidents.

answering
Hyperping
by hyperping

Uptime, API and server monitoring with outages, reporting, on-call and status pages.

69 tools answering
A
Agent Health
by autonet

Free owned-agent uptime monitoring, DNS domain proof, signed alerts and opt-in endpoint checks.

53 tools answering
Fettle
by fettle

Uptime monitoring — monitors, incidents, heartbeats, maintenance windows, status page incidents

1 011 installs/wk 49 tools answering
Oh Dear
by ohdear

Website monitoring: uptime, SSL certificates, broken links, DNS, cron jobs and status pages.

answering
StatusCake MCP by usefulapi
by usefulapi

Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.

21 tools answering

Watchpup — questions

Answers built from our own checks of this server.

What can Watchpup do?
It exposes 12 tools, read directly from the server on our last check. Among them: ack_incident, add_incident_note, check_url, create_monitor, delete_monitor, get_account and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Watchpup working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 80 ms. The bar chart above shows every period we have measured.
The registry lists Watchpup as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Watchpup?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Watchpup need an API key?
No. Watchpup completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.