Dev tools · Official remote MCP server

The Watchpup MCP server,
connected in one click.

Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts. Connect the official Watchpup MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.

Free to start · No credit card · No hosting needed

Use this server

Add Watchpup to your AI in one minute

Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.

claude mcp add --transport http watchpup https://watchpup.watchpup.workers.dev/mcp

Run in your terminal, then restart Claude Code.

Watchpup · https://watchpup.watchpup.workers.dev/mcp

What you can do

What your AI can do with Watchpup

Real prompts you can type the moment it's connected — no setup, no docs to read.

Use “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 h.

Use “list_monitors”: List all monitors on the account: current up/down status, kind, target, interval, last check. Optionally filter by tag.

Use “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.

Use “create_monitor”: Create a monitor. kind=http (needs url), tcp (target "host:port"), tls (target host[:port] — cert-expiry watch), domain (target — registrati.

Security check

How secure is the Watchpup MCP server?

Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Watchpup holds up.

Verified directory serverWatchpup · workers.dev

Official endpoint

Operated by Watchpup (workers.dev) at its documented MCP endpoint — not a third-party mirror or community re-host.

No sign-in needed

This server only exposes public data — no account and no credentials are involved when you connect.

Scanned before it goes live

gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.

Watched for drift

If Watchpup adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.

How it works

Connected in three steps

01

Connect your gate

Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.

02

Pick Watchpup

Choose Watchpup in the gate directory. No sign-in needed.

03

Use it anywhere

Watchpup's tools are live in every AI client you've connected — with rules and logging built in.

Connect Watchpup free

Free to start · No credit card · No hosting needed

Straight from the server

The actual tools Watchpup exposes

Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.

check_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 h

list_monitorsList all monitors on the account: current up/down status, kind, target, interval, last check. Optionally filter by tag.

get_monitorFull detail for one monitor: status, config, 24h latency percentiles and trend (http/tcp), SLA budget if a target is set. Heartbeat monitors

create_monitorCreate a monitor. kind=http (needs url), tcp (target "host:port"), tls (target host[:port] — cert-expiry watch), domain (target — registrati

update_monitorPATCH any monitor field: name, url, target, interval, expect, keyword, slow_ms, grace, cron, tags, sla_target, renotify, channels (alert rou

delete_monitorPermanently delete a monitor and all its check history, events and rollups. Cannot be undone.

list_incidentsDowntime incidents (ongoing and resolved) across all monitors: start, duration, cause, acknowledgement, notes.

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-acknow

+ 4 more tools once connected

Server facts

The Watchpup MCP server at a glance

Endpointhttps://watchpup.watchpup.workers.dev/mcp
Operated byWatchpup (workers.dev)
CategoryDev tools
Sign-inNone — public data only
Available in gateYes — one-click connect
Works withClaude, ChatGPT, Cursor & any MCP client
FAQ

Questions, answered

Is there an official Watchpup MCP server?

Yes — Watchpup operates its own remote MCP server at watchpup.watchpup.workers.dev. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.

How do I connect Watchpup to Claude or ChatGPT?

Add gate's gateway URL to your AI client once, then pick Watchpup in the directory. No account or sign-in is needed. From then on, Watchpup's tools are available in every client you've connected to gate.

Do I need to host anything?

No. Watchpup runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.

Is the Watchpup MCP server safe to connect?

It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.

Is it free?

Yes — you can get started with gate for free and connect Watchpup in minutes. No credit card required.

More servers

Connect more than just Watchpup

Every server below works through the same gateway URL — connect once, add tools anytime.

Set up Watchpup in: Claude · Claude Code · ChatGPT · Cursor · VS Code

Give your AI Watchpup — safely.

One URL. All MCPs. Full control. Free to start.

Get started free