Remote MCP · Endpoint

PulseWatch public knowledge MCP server

No. PulseWatch public knowledge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pulsewatch.top/mcp/

The last check completed an MCP handshake.

Registry name
top.pulsewatch/public-knowledge
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
294 ms
Tools exposed
Not measured yet
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Public PulseWatch offers and monitoring guides. No private customer data or monitor controls.
Website
https://pulsewatch.top/
Listing
From the official MCP registry (active).
Recent checks of PulseWatch public knowledge
CheckedResultHandshake
1 hour agoHandshake completed294 ms
1 day agoHandshake completed292 ms
2 days agoHandshake completed299 ms
3 days agoHandshake completed291 ms
4 days agoHandshake completed294 ms
5 days agoHandshake completed289 ms
6 days agoHandshake completed315 ms
8 days agoHandshake completed475 ms
11 days agoHandshake completed289 ms
13 days agoHandshake completed330 ms
15 days agoHandshake completed294 ms
18 days agoHandshake completed290 ms
20 days agoHandshake completed463 ms
22 days agoHandshake completed299 ms
24 days agoHandshake completed303 ms
26 days agoHandshake completed287 ms
27 days agoHandshake completed314 ms
29 days agoHandshake completed291 ms
29 days agoHandshake completed277 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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