com.ainetcafe/netcafe-translate
https://ainetcafe.com/mcp/translate?s=registry
● healthy
Translation that never breaks structure: .srt timings, i18n key trees, PDF layout.
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-06-18
negotiated, not declared
MCP readiness
C · 72/100
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 94.1/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (435 ms). |
| Protocol revision | 6/10 | Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 7/15 | 14/30 probes succeeded over 30 days (47%). |
| Tool declaration | 10/10 | Lists 7 tool(s) with descriptions. |
| Verified identity | 7/10 | Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time). |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive
(435 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.
Compared with peers
Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.
- Readiness
- Higher than 34% of peers
- This listing 72 · peer median 81
- Latency
- Faster than 44% of peers
- This listing 378 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Uptime (30 days) −8
— Stay reachable in our daily probes.
Now: 14/30 probes succeeded over 30 days (47%).
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
Adoption signals
Public signals from outside this directory, shown for context. They do not change search order or grades.
Listed in
Directories this entry was found in.
How to connect
MCP endpoint (streamable-http)
https://ainetcafe.com/mcp/translate?s=registryJSON-RPC initialize probe
curl -X POST https://ainetcafe.com/mcp/translate?s=registry \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'Homepage
https://ainetcafe.com/mcp.html
Source code
https://github.com/mario03690/ai-netcafe