Samedoc: Translate PDF & PDF to Word
REMOTE · SAMEDOC.APP
Translate PDFs and scans into another language in the same layout, every number kept. PDF to Word.
Available components
Last scanned (15 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 867 tokens (~144/item across 6 items; 4 tools + 2 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 Management53
- Stability observed for 16 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 4 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- 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 →
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.
- 21 Nov 26 0
- Resource “Translated document” now points somewhere else: ui://widget/samedoc-result-v2.html → ui://widget/samedoc-result-app-v2.html security
- 20 Nov 26 +1
- Resource “Translated document” now points somewhere else: ui://widget/samedoc-result-v2.html → ui://widget/samedoc-result-app-v2.html security
- 19 Nov 26 0
- Resource “Translated document” now points somewhere else: ui://widget/samedoc-result-v2.html → ui://widget/samedoc-result-app-v2.html security
- 18 Nov 26 +1
- Resource “Translated document” now points somewhere else: ui://widget/samedoc-result-v2.html → ui://widget/samedoc-result-app-v2.html security
- 17 Nov 26 0
- Resource “Translated document” now points somewhere else: ui://widget/samedoc-result-v2.html → ui://widget/samedoc-result-app-v2.html security
- 16 Nov 26 +1
- Resource “Translated document” now points somewhere else: ui://widget/samedoc-result-v2.html → ui://widget/samedoc-result-app-v2.html security
- 15 Nov 26 0
- Resource “Translated document” now points somewhere else: ui://widget/samedoc-result-v2.html → ui://widget/samedoc-result-app-v2.html security
- 14 Nov 26 +1
- Resource “Translated document” now points somewhere else: ui://widget/samedoc-result-v2.html → ui://widget/samedoc-result-app-v2.html security
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://samedoc.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=samedoc.app | CN=YE1,O=Let's Encrypt,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6172626d0231994d06a95e5b58c8a3dafcf |
| SANs: samedoc.app | ||||||
| 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 samedoc.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| samedoc.app. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://samedoc.app/mcp | Verified | 200 | |
| http (plaintext) | http://samedoc.app/mcp | HTTPS enforced | 308 | https://samedoc.app/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 →
convert_to_word Convert a PDF or scan to an editable Word file ~219
Turns a PDF or a scanned document / photo of one into an editable Word file (.docx) that looks like the original page: every line of text is editable in place, over the original design (tables, lines, logos, stamps and signatures kept exactly). Same language, no translation. Reads scans and broken PDF text, and keeps Hebrew and Arabic right-to-left. Use when the user says 'convert this PDF to Word / docx', 'make this PDF editable', 'I need to edit this form / scan', or when a Word file made in chat lost the logo, tables or layout. Give the document as `file` (a file the user attached) or `file_url` (an https link). Up to 3 pages per document. Takes 20-90 seconds; if it takes longer, returns an id for get_translation.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | The document the user attached (ChatGPT file). |
| file_url | string | – | https link to the PDF or image, when no file is attached. |
No output schema declared.
No examples provided.
get_translation Get a translation or Word file ~40
Returns the status and download link of a job started with translate_document or convert_to_word (use its id).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The translation id. |
No output schema declared.
No examples provided.
get_upload_link Get a link to upload a document ~44
For users whose document can't be handed to translate_document here (no attachment support, no https link): a page where they upload it and get the translated document or Word file.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
translate_document Translate a document and keep its layout ~333
Translates a PDF or a scanned document / photo of one into another language and returns the same document as a PDF: layout, tables, logos and every number kept and checked. For payslips, bank statements, official and government letters, birth and marriage certificates, diplomas, school reports, contracts, leases and forms, e.g. for a visa, immigration, a bank or a school. Strong on right-to-left sources (Hebrew, Arabic), which it can also mirror into a left-to-right layout. Use when the user says 'translate this PDF / document / scan', 'keep the formatting / layout', 'give me back the PDF', or when a translation in chat lost the tables or layout. Give the document as `file` (a file the user attached) or `file_url` (an https link). Up to 3 pages per document. Takes 30-90 seconds; if it takes longer, returns an id for get_translation.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | The document the user attached (ChatGPT file). |
| file_url | string | – | https link to the PDF or image, when no file is attached. |
| from | string | – | Source language. Leave out to detect it. |
| keep_logos | boolean | – | true = don't translate logos and wordmarks. |
| layout | string | – | keep = same layout as the original (default); ltr = mirror a right-to-left page (Hebrew, Arabic) into a left-to-right layout. |
| to | string | – | Target language, e.g. English, Spanish, German. Defaults to English. |
No output schema declared.
No examples provided.
How do I install the Samedoc: Translate PDF & PDF to Word MCP server?
Samedoc: Translate PDF & PDF to Word is a hosted endpoint at https://samedoc.app/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 · samedoc.app
claude mcp add --transport http app-samedoc-samedoc 'https://samedoc.app/mcp'
What is the Samedoc: Translate PDF & PDF to Word MCP server?
Samedoc: Translate PDF & PDF to Word is an MCP server listed in the public MCP registry as app.samedoc/samedoc. Translate PDFs and scans into another language in the same layout, every number kept. PDF to Word. This page covers its hosted endpoint (https://samedoc.app/mcp).
Is the Samedoc: Translate PDF & PDF to Word MCP server safe to use?
Samedoc: Translate PDF & PDF to Word scores 82 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 Samedoc: Translate PDF & PDF to Word MCP server expose?
Samedoc: Translate PDF & PDF to Word exposes 4 tools: translate_document, convert_to_word, get_translation, get_upload_link. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.
Does the Samedoc: Translate PDF & PDF to Word MCP server require authentication?
No. We connected to Samedoc: Translate PDF & PDF to Word without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Samedoc: Translate PDF & PDF to Word MCP server still maintained?
Samedoc: Translate PDF & PDF to Word 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 Samedoc: Translate PDF & PDF to Word MCP server?
VerifyMCP ran 14 checks on Samedoc: Translate PDF & PDF to Word, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. 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.