Remote MCP · Endpoint

Proxylang website translation MCP server

No. Proxylang website translation answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://proxylang.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.proxylang/translate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
261 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Translate a website into other languages from one script tag. Free trial, no signup.
Listing
From the official MCP registry (active).
Recent checks of Proxylang website translation
CheckedResultHandshake
53 minutes agoHandshake completed261 ms
3 days agoHandshake completed628 ms
12 days agoHandshake completed600 ms
13 days agoHandshake completed235 ms
15 days agoHandshake completed555 ms
15 days agoHandshake completed208 ms
17 days agoHandshake completed233 ms
18 days agoHandshake completed423 ms
18 days agoHandshake completed295 ms
20 days agoHandshake completed403 ms
22 days agoHandshake completed204 ms
25 days agoHandshake completed323 ms
27 days agoHandshake completed422 ms
29 days agoHandshake completed480 ms

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

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