Remote MCP · Endpoint

Hook Detector MCP server

No. Hook Detector answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://api.hookdetector.com/mcp

The last check completed an MCP handshake.

Registry name
com.hookdetector/hookdetector
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
39 ms
Tools exposed
154 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Real TikTok and Instagram hooks that already work, in any language, with why each travelled.
Listing
From the official MCP registry (active).
Recent checks of Hook Detector
CheckedResultHandshake
56 minutes agoHandshake completed39 ms
3 days agoHandshake completed37 ms
12 days agoHandshake completed31 ms
13 days agoHandshake completed28 ms
15 days agoHandshake completed30 ms
15 days agoHandshake completed64 ms
17 days agoHandshake completed23 ms
18 days agoHandshake completed23 ms
18 days agoHandshake completed23 ms
20 days agoHandshake completed28 ms
22 days agoHandshake completed23 ms
25 days agoHandshake completed23 ms
27 days agoHandshake completed22 ms
29 days agoHandshake completed27 ms

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

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