Remote MCP · Endpoint

Watchtower MCP server

No. Watchtower answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://watchtower.lat/mcp?ref=registry

The last check completed an MCP handshake.

Registry name
lat.watchtower/watchtower
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
219 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Job alerts for AI agents: describe a role once, get only new postings from 1,500+ tech job boards.
Listing
From the official MCP registry (active).
Recent checks of Watchtower
CheckedResultHandshake
6 hours agoHandshake completed219 ms
2 days agoHandshake completed258 ms
5 days agoHandshake completed105 ms
7 days agoHandshake completed127 ms
9 days agoHandshake completed649 ms
11 days agoHandshake completed261 ms
13 days agoHandshake completed98 ms
15 days agoHandshake completed107 ms
17 days agoHandshake completed188 ms
18 days agoHandshake completed99 ms
20 days agoHandshake completed152 ms
21 days agoHandshake completed109 ms
23 days agoHandshake completed100 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Watchtower and makes no claim about it beyond what these checks measured.