Remote MCP · Endpoint

EasyVoice text to speech MCP server

No. EasyVoice text to speech answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://easyvoice.ae/api/mcp

The last check completed an MCP handshake.

Registry name
ae.easyvoice/tts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
331 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Hosted text-to-speech MCP server: 66 voices in 9 languages, long-form narration, podcasts.
Listing
From the official MCP registry (active).
Recent checks of EasyVoice text to speech
CheckedResultHandshake
1 hour agoHandshake completed331 ms
1 day agoHandshake completed339 ms
2 days agoHandshake completed362 ms
3 days agoHandshake completed357 ms
4 days agoHandshake completed339 ms
5 days agoHandshake completed337 ms
6 days agoHandshake completed342 ms
9 days agoHandshake completed551 ms
11 days agoHandshake completed367 ms
14 days agoHandshake completed334 ms
16 days agoHandshake completed347 ms
18 days agoHandshake completed334 ms
20 days agoHandshake completed332 ms
22 days agoHandshake completed336 ms
24 days agoHandshake completed447 ms

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

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