Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://watchpup.watchpup.workers.dev/mcp12 tools · 142mscheck_urlCheck 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" f…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" f…
url: Links to undeclared domains: example.com, mcp.deepwiki.com| Parameter | Type | Description |
|---|---|---|
| url* | string | 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 |
| kind | string | What to speak: plain HTTP (default) or an MCP initialize handshake |
list_monitorsList all monitors on the account: current up/down status, kind, target, interval, last check. Optionally filter by tag.List all monitors on the account: current up/down status, kind, target, interval, last check. Optionally filter by tag.
| Parameter | Type | Description |
|---|---|---|
| tag | string | Only monitors carrying ALL these tags (comma-separated), e.g. "prod" or "prod,eu" |
get_monitorFull 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.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.
| Parameter | Type | Description |
|---|---|---|
| id* | string | Monitor id (from list_monitors) |
create_monitorCreate 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 i…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 i…
| Parameter | Type | Description |
|---|---|---|
| kind | string | Monitor kind (default http; "mcp" monitors an MCP server via JSON-RPC initialize) |
| url | string | For kind=http: the URL to check |
| target | string | For tcp/tls/domain/dns: host[:port] or domain name |
| name | string | Display name (required for heartbeat, defaults to the target host otherwise) |
| interval | integer | Check interval in seconds, min 60 (heartbeat: expected ping interval) |
update_monitorPATCH 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.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.
| Parameter | Type | Description |
|---|---|---|
| id* | string | Monitor id |
| status | string | "paused" stops checking; "new" resumes |
delete_monitorprivilegedPermanently delete a monitor and all its check history, events and rollups. Cannot be undone.Permanently delete a monitor and all its check history, events and rollups. Cannot be undone.
| Parameter | Type | Description |
|---|---|---|
| id* | string | Monitor id |
list_incidentsDowntime incidents (ongoing and resolved) across all monitors: start, duration, cause, acknowledgement, notes.Downtime incidents (ongoing and resolved) across all monitors: start, duration, cause, acknowledgement, notes.
| Parameter | Type | Description |
|---|---|---|
| days | integer | Lookback window in days, 1-90 (default 30) |
ack_incidentMark 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).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).
| Parameter | Type | Description |
|---|---|---|
| id* | integer | Incident id (from list_incidents) |
| un | boolean | true = remove an existing acknowledgement |
add_incident_noteAttach/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.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.
| Parameter | Type | Description |
|---|---|---|
| id* | integer | Incident id (from list_incidents) |
| note* | string | The note text ("" clears) |
list_channelsAlert delivery channels on the account (email / webhook / Discord / Slack / ntfy / Telegram), their verification state and delivery health.Alert delivery channels on the account (email / webhook / Discord / Slack / ntfy / Telegram), their verification state and delivery health.
No input schema was published for this tool.
get_status_pageMachine-readable state of any public Watchpup status page by slug: per-monitor status, uptime, incidents last 30d. No API key needed.Machine-readable state of any public Watchpup status page by slug: per-monitor status, uptime, incidents last 30d. No API key needed.
| Parameter | Type | Description |
|---|---|---|
| slug* | string | Status page slug (the part after /s/) |
get_accountWho am I: account email, monitor count/limit, plan limits. Good first call to verify the API key works.Who am I: account email, monitor count/limit, plan limits. Good first call to verify the API key works.
No input schema was published for this tool.
12 of 12 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.