Remote MCP · Endpoint

Speak MCP server

No. Speak answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://speak.kaneky.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.kaneky/speak
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
549 ms
Tools exposed
1 tool
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Text to natural speech as MP3: 38 voices, 7 languages, 1,000 chars per call. Paid per call, x402.
Listing
From the official MCP registry (active).
Recent checks of Speak
CheckedResultHandshake
9 hours agoHandshake completed549 ms
4 days agoHandshake completed453 ms
14 days agoHandshake completed421 ms
15 days agoHandshake completed514 ms
15 days agoHandshake completed428 ms
17 days agoHandshake completed419 ms
18 days agoHandshake completed419 ms
19 days agoHandshake completed408 ms
20 days agoHandshake completed410 ms
21 days agoHandshake completed296 ms
23 days agoFailed - the request timed out—
26 days agoHandshake completed443 ms
28 days agoHandshake completed417 ms

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

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