Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.ainetcafe/netcafe-translate

REMOTE · AINETCAFE.COM

Translation that never breaks structure: .srt timings, i18n key trees, PDF layout.

Available components

−56 this week 23 Trust /100

Last scanned (16 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Nov 26 −57
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.60 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 −7
    • Stability: pass → 0.47 functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://ainetcafe.com/mcp/translate?s=registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ainetcafe.com CN=WE1,O=Google Trust Services,C=US 26 Sept 2026 25 Dec 2026 ECDSA 256 ECDSA-SHA256 5d17da71fa17d5231307fc9550536f42
SANs: ainetcafe.com, *.ainetcafe.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ainetcafe.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
ainetcafe.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 502
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ainetcafe.com/mcp/translate?s=registry HTTP error 502
http (plaintext) http://ainetcafe.com/mcp/translate?s=registry HTTPS enforced 301 https://ainetcafe.com/mcp/translate?s=registry
MCP tools · 7 exposed · ~921 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_grammar ~109

Check text for grammar, spelling and style issues in 30+ languages (self-hosted LanguageTool). Returns each issue with a suggested replacement — apply them to produce corrected text. Example — GET https://ainetcafe.com/t/check_grammar?text=Their+going+to+the+park

NameTypeReqDescription
languagestring–Language code like "en-US", "zh-CN"; default "auto".
textstringyesThe text to check (≤10000 chars).

Structured output declared, but exposes no named fields.

No examples provided.

check_job ~108

Get the status or result of a job started by deep_research, translate_pdf, or make_slides. Poll every 15-30 seconds until status is "done" or "error". While work is pending, follow retry_after_seconds and next_action; when complete, prefer structured_result when present. Example — GET https://ainetcafe.com/t/check_job?job_id=<id-from-a-job-tool>

NameTypeReqDescription
job_idstringyesThe job_id returned when the task was started.
NameTypeReqDescription
errorstring––
is_terminalboolean––
job_idstringyes–
kindstring––
next_actionobject|null––
result–––
retry_after_secondsinteger––
statusstringyes–
structured_result–––

No examples provided.

translate_i18n_json ~119

Translate an i18n JSON locale file, keeping the key structure identical and placeholders ({name}, {{count}}, %s, HTML tags) intact. Pass existing_json to translate only the keys that are missing from it — the incremental sync people usually hand-roll a script for.

NameTypeReqDescription
existing_jsonstring–Existing target locale; only missing keys get translated.
jsonstring–Source locale file content (JSON).
tostring–Target language.
urlstring–Or a link to the source JSON.

Structured output declared, but exposes no named fields.

No examples provided.

translate_pdf ~197

Translate a PDF from a URL while preserving the original layout — formulas, figures and two-column academic typesetting stay intact, unlike ordinary translators that flatten the document. Returns a job_id; poll check_job for the download links (translated-only and bilingual side-by-side). Typically 20-60 seconds for a few pages. Powered by PDFMathTranslate (36k stars) hosted at AI NetCafé. Example — tools/call translate_pdf {"url":"<pdf-url>","target":"zh"} → poll check_job

NameTypeReqDescription
lang_tostring–Target language, e.g. "Simplified Chinese", "Japanese". Default Simplified Chinese.
pagesstring–How much to translate. first = 1 page, first5 = first 5 pages (default), all = whole document (slow and expensive).
urlstringyesDirect URL to the PDF (e.g. an arXiv PDF link).
NameTypeReqDescription
job_idstringyes–
poll_interval_secondsinteger––
statusstringyes–

No examples provided.

translate_srt ~113

Translate an .srt subtitle file into another language while keeping every timestamp and cue number byte-identical. Cues are anchored by index and refilled in code, so the timeline cannot drift — the usual failure mode when you hand a whole .srt to a model.

NameTypeReqDescription
srtstring–The .srt file content.
tostring–Target language, e.g. "English", "日本語".
urlstring–Or a link to the .srt file.

Structured output declared, but exposes no named fields.

No examples provided.

translate_text ~116

Translate text between languages using a self-hosted LibreTranslate engine (fully offline, no big-tech API). For whole PDFs with layout preserved, use translate_pdf instead. Example — GET https://ainetcafe.com/t/translate_text?text=hello+world&to=zh

NameTypeReqDescription
sourcestring–Source language code; default "auto".
targetstringyesTarget language code, e.g. "zh", "en", "ja".
textstringyesText to translate (≤5000 chars).

Structured output declared, but exposes no named fields.

No examples provided.

what_can_you_do ~159

Describe a task in plain language (any language) and get back exactly which tools on this server do it, with ready-to-run example calls — instead of reading the whole catalogue and guessing. Also returns multi-step recipes when a task needs several tools chained (invoices to a ledger, a bank statement reconciled, a messy CSV turned into a deliverable). Deterministic and free: it calls no model, costs nothing, and never runs out of quota. Call this FIRST when you are not sure what this server offers.

NameTypeReqDescription
taskstringyesWhat you are trying to do, e.g. "reconcile a bank statement against my books" or "把一堆发票整理成能入账的表格"

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the com.ainetcafe/netcafe-translate MCP server?

com.ainetcafe/netcafe-translate is a hosted endpoint at https://ainetcafe.com/mcp/translate?s=registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ainetcafe.com

# add to Claude Code
claude mcp add --transport http com-ainetcafe-netcafe-translate 'https://ainetcafe.com/mcp/translate?s=registry'
Common questions

What is the com.ainetcafe/netcafe-translate MCP server?

com.ainetcafe/netcafe-translate is an MCP server listed in the public MCP registry as com.ainetcafe/netcafe-translate. Translation that never breaks structure: .srt timings, i18n key trees, PDF layout. This page covers its hosted endpoint (https://ainetcafe.com/mcp/translate?s=registry).

Is the com.ainetcafe/netcafe-translate MCP server safe to use?

com.ainetcafe/netcafe-translate scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.ainetcafe/netcafe-translate MCP server expose?

com.ainetcafe/netcafe-translate exposes 7 tools: what_can_you_do, translate_text, translate_srt, translate_i18n_json, check_grammar, and 2 more. Their descriptions and schemas cost roughly 921 tokens of context every time the server is loaded.

Does the com.ainetcafe/netcafe-translate MCP server require authentication?

Its publisher declares no required credentials for com.ainetcafe/netcafe-translate. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the com.ainetcafe/netcafe-translate MCP server still maintained?

com.ainetcafe/netcafe-translate is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.ainetcafe/netcafe-translate MCP server?

VerifyMCP ran 5 checks on com.ainetcafe/netcafe-translate, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about com.ainetcafe/netcafe-translate: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.