Remote MCP · Endpoint

Datoka Hooks MCP server

No. Datoka Hooks answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://datoka-hooks-test.bhazarstudio.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.bhazarstudio.datoka-hooks-test/datoka-hooks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
372 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public webhook relay with signed observations, retries and verified receivers. Self-service beta.
Listing
From the official MCP registry (active).
Recent checks of Datoka Hooks
CheckedResultHandshake
2 hours agoHandshake completed372 ms
2 days agoHandshake completed620 ms
4 days agoHandshake completed270 ms
6 days agoHandshake completed244 ms
8 days agoHandshake completed313 ms
10 days agoHandshake completed408 ms
12 days agoHandshake completed446 ms
14 days agoHandshake completed259 ms
15 days agoHandshake completed78 ms
16 days agoHandshake completed259 ms
17 days agoHandshake completed307 ms
20 days agoHandshake completed175 ms
22 days agoHandshake completed167 ms
23 days agoHandshake completed256 ms

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

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