Remote MCP · Endpoint

voicehook MCP server

No. voicehook answered an MCP handshake 15 minutes ago.

UpLast checked 15 minutes ago

Server URL

https://voicehook.ai/mcp?utm_source=mcpregistry&utm_campaign=d11-registry

The last check completed an MCP handshake.

Registry name
io.github.voicehook-ai/voicehook
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
329 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Talk with your agents. A voice call in the browser that your agent can start or join.
Listing
From the official MCP registry (active).
Recent checks of voicehook
CheckedResultHandshake
15 minutes agoHandshake completed329 ms
9 days agoHandshake completed309 ms
9 days agoHandshake completed307 ms
11 days agoHandshake completed295 ms
12 days agoHandshake completed327 ms
13 days agoHandshake completed305 ms
14 days agoHandshake completed498 ms
14 days agoHandshake completed467 ms
16 days agoHandshake completed308 ms
19 days agoHandshake completed308 ms
21 days agoHandshake completed301 ms
24 days agoHandshake completed297 ms
26 days agoHandshake completed309 ms
28 days agoHandshake completed329 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 voicehook and makes no claim about it beyond what these checks measured.