Remote MCP · Endpoint

Proxylang website translation MCP server

No. Proxylang website translation answered an MCP handshake 4 hours ago.

UpLast checked 4 hours 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
323 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
4 hours agoHandshake completed323 ms
2 days agoHandshake completed422 ms
4 days agoHandshake completed480 ms
6 days agoHandshake completed555 ms
8 days agoHandshake completed359 ms
10 days agoHandshake completed255 ms
13 days agoHandshake completed189 ms
14 days agoHandshake completed146 ms
16 days agoHandshake completed205 ms
17 days agoHandshake completed512 ms
18 days agoHandshake completed150 ms
21 days agoHandshake completed281 ms
22 days agoHandshake completed439 ms
24 days agoCredentials required—

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