Remote MCP · Endpoint

Faceabot Translate MCP server

No. Faceabot Translate answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://faceabot.com/tools-mcp/translate

The last check completed an MCP handshake.

Registry name
com.faceabot/translate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
741 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Translate text or a document into about 100 languages. Free, no key.
Website
https://faceabot.com/tools/com.faceabot/translate
Listing
From the official MCP registry (active).
Recent checks of Faceabot Translate
CheckedResultHandshake
19 minutes agoHandshake completed741 ms
9 days agoHandshake completed732 ms
9 days agoHandshake completed171 ms
11 days agoHandshake completed703 ms
12 days agoHandshake completed60 ms
13 days agoHandshake completed701 ms
14 days agoHandshake completed48 ms
15 days agoHandshake completed164 ms
16 days agoHandshake completed772 ms
19 days agoHandshake completed823 ms
21 days agoHandshake completed1.03 s
24 days agoHandshake completed1.38 s

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Faceabot Translate and makes no claim about it beyond what these checks measured.