Remote MCP · Endpoint

PulseWatch Vendor Status MCP server

No. PulseWatch Vendor Status answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.pulsewatch.us/mcp

The last check completed an MCP handshake.

Registry name
us.pulsewatch.api/status
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
225 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Is this vendor down? Pay-per-call status for 1,700+ SaaS/cloud vendors from PulseWatch (x402 USDC).
Listing
From the official MCP registry (active).
Recent checks of PulseWatch Vendor Status
CheckedResultHandshake
1 hour agoHandshake completed225 ms
1 day agoHandshake completed202 ms
2 days agoHandshake completed360 ms
3 days agoHandshake completed152 ms
4 days agoHandshake completed253 ms
5 days agoHandshake completed96 ms
7 days agoHandshake completed236 ms
10 days agoHandshake completed421 ms
12 days agoHandshake completed235 ms
14 days agoHandshake completed392 ms
17 days agoHandshake completed206 ms
19 days agoHandshake completed203 ms
21 days agoHandshake completed203 ms
23 days agoHandshake completed215 ms
25 days agoHandshake completed435 ms

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

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 PulseWatch Vendor Status and makes no claim about it beyond what these checks measured.