Remote MCP · Endpoint
net.hookpulse/hookpulse MCP server
No. net.hookpulse/hookpulse answered an MCP handshake 4 hours ago.
UpLast checked 4 hours ago
Server URL
https://hookpulse.net/mcp
The last check completed an MCP handshake.
- Registry name
- net.hookpulse/hookpulse
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 363 ms
- Tools exposed
- 41 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.
- Website
- https://hookpulse.net/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 4 hours ago | Handshake completed | 363 ms |
| 14 hours ago | Handshake completed | 361 ms |
| 1 day ago | Handshake completed | 365 ms |
| 2 days ago | Handshake completed | 33 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 net.hookpulse/hookpulse and makes no claim about it beyond what these checks measured.