Remote MCP · Endpoint

FreeTTS MCP server

No. FreeTTS answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.freetts.org/mcp

The last check completed an MCP handshake.

Registry name
org.freetts/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
347 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Text to speech in 149 languages: MP3 links from any assistant. Free without an account.
Listing
From the official MCP registry (active).
Recent checks of FreeTTS
CheckedResultHandshake
1 hour agoHandshake completed347 ms
2 days agoHandshake completed359 ms
4 days agoHandshake completed364 ms
6 days agoHandshake completed334 ms
8 days agoHandshake completed371 ms
10 days agoHandshake completed355 ms
12 days agoHandshake completed333 ms
14 days agoHandshake completed346 ms
16 days agoHandshake completed358 ms
17 days agoHandshake completed352 ms
18 days agoHandshake completed357 ms
21 days agoHandshake completed369 ms
22 days agoHandshake completed341 ms
24 days agoHandshake completed338 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 FreeTTS and makes no claim about it beyond what these checks measured.