Translation by park13
REMOTE · TRANSLATE.PARK13.DIGITAL
English→Japanese document translation with a certificate. No API key, free quote, fixed ¥980–5,980
Available components
Last scanned (6 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 804 tokens (~160/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_service_info” rewrote its description, which is the text the model reads security
- Schema quality: 123 → 160 ▼ functional
- Server version: 1.0.0 → 1.0.1 functional
- “quote_document” added an optional parameter “locale” cosmetic
- “create_order” reworded the description of “files” cosmetic
- “create_order” reworded the description of “locale” cosmetic
- “quote_document” reworded the description of “files” cosmetic
- 30 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 71
First indexed and scored.
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 5 Nov 2026 · Probed https://translate.park13.digital/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=translate.park13.digital | CN=YE1,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 607aede1e27e5e6b9cc384df70b064cf736 |
| SANs: translate.park13.digital | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of translate.park13.digital. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| digital. | present | 43807 | 8 | Verified |
| park13.digital. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://translate.park13.digital/api/mcp | Verified | 200 | |
| http (plaintext) | http://translate.park13.digital/api/mcp | HTTPS enforced | 301 | https://translate.park13.digital/api/mcp |
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 →
create_order Prepare an order ~212
Prepares an order for your user to approve and pay. Returns approvalUrl (give it to the user: they review the terms, consent and pay there; you cannot) and a private token for get_order_status. Nothing is charged until the user pays, and only when the certificate is issued.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | One PDF, or up to 5 JPEG/PNG images of one document in page order. Max 10 MB in total before encoding (base64 in JSON makes it about a third larger; the REST API takes up to 20 MB as a multipart uplo… |
| locale | string | – | Language of the user's pages and emails (Japanese if omitted), and of this tool's messages (English if omitted) |
| names | array | – | Optional, up to 10 people named in the document: added to the translation as a customer-supplied note (names in the translation stay as written) |
| receiving_procedure | string | – | Where the translation will be submitted, if known |
No output schema declared.
No examples provided.
get_order_status Order status ~68
An order's status and the next step (e.g. waiting for the user's approval or for them to confirm a scan), the certificate number, and download links once completed.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | orderId from create_order |
| token | string | yes | token from create_order |
No output schema declared.
No examples provided.
get_service_info Service information ~48
What the service translates, what files it accepts, limits (file size, pages, words, requests per hour), prices (yen, tax included), delivery times and how ordering and payment work.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_procedure_guides Procedure guides ~52
Guides to Japanese procedures that need translated English documents (e.g. tax deductions for family abroad, marriage registration, registering a birth abroad): what is required and what the translation must show, with government sources.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_document Quote a document ~122
Free price check: screens the file (format, pages, words, scanned pages) and returns the price, or why it can't be processed. Nothing is stored and nothing is charged.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | One PDF, or up to 5 JPEG/PNG images of one document in page order. Max 10 MB in total before encoding (base64 in JSON makes it about a third larger; the REST API takes up to 20 MB as a multipart uplo… |
| locale | string | – | Language of the error message and notes (English if omitted) |
No output schema declared.
No examples provided.
How do I install the Translation by park13 MCP server?
Translation by park13 is a hosted endpoint at https://translate.park13.digital/api/mcp, 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 · translate.park13.digital
claude mcp add --transport http digital-park13-translate 'https://translate.park13.digital/api/mcp'
What is the Translation by park13 MCP server?
Translation by park13 is an MCP server listed in the public MCP registry as digital.park13/translate. English→Japanese document translation with a certificate. No API key, free quote, fixed ¥980–5,980. This page covers its hosted endpoint (https://translate.park13.digital/api/mcp).
Is the Translation by park13 MCP server safe to use?
Translation by park13 scores 73 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 Translation by park13 MCP server expose?
Translation by park13 exposes 5 tools: get_service_info, list_procedure_guides, quote_document, create_order, get_order_status. Their descriptions and schemas cost roughly 502 tokens of context every time the server is loaded.
Does the Translation by park13 MCP server require authentication?
No. We connected to Translation by park13 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Translation by park13 MCP server still maintained?
Translation by park13 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.