Remote MCP · Endpoint
com.ainetcafe/netcafe-translate MCP server
No. com.ainetcafe/netcafe-translate answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ainetcafe.com/mcp/translate?s=registry
The last check completed an MCP handshake.
- Registry name
- com.ainetcafe/netcafe-translate
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 435 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 50.0% from 18 checks
- Described by its publisher as
- Translation that never breaks structure: .srt timings, i18n key trees, PDF layout.
- Repository
- https://github.com/mario03690/ai-netcafe
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 435 ms |
| 1 day ago | Handshake completed | 490 ms |
| 2 days ago | Handshake completed | 468 ms |
| 3 days ago | Handshake completed | 515 ms |
| 4 days ago | Failed - the request timed out | — |
| 5 days ago | Failed - the request timed out | — |
| 6 days ago | Handshake completed | 928 ms |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 16 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 25 days ago | Handshake completed | 318 ms |
| 26 days ago | Handshake completed | 358 ms |
| 28 days ago | Handshake completed | 324 ms |
| 29 days ago | Handshake completed | 916 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 20 responding of 29.
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 com.ainetcafe/netcafe-translate and makes no claim about it beyond what these checks measured.