com.auto-reader/ocr
REMOTE · API.AUTO-READER.COM
Arabic-first OCR, translation and document extraction. First call mints a free trial key.
Available components
Last scanned (20 hours ago)
Scores higher than 56% 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1556 tokens (~222/item across 7 items; 7 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
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 fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 15 Nov 26 0
- Tool “translate_text” rewrote its description, which is the text the model reads security
- 14 Nov 26 0
- Tool “extract_document” rewrote its description, which is the text the model reads security
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://api.auto-reader.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=auto-reader.com | CN=WE1,O=Google Trust Services,C=US | 5 Nov 2026 | 3 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 7303d984bc5043f13f4c213e1ef6e06 |
| SANs: auto-reader.com, api.auto-reader.com, *.api.auto-reader.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 api.auto-reader.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| auto-reader.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.auto-reader.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.auto-reader.com/mcp | Inconclusive | 405 |
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_api_key ~88
Provision a new Auto-Reader OCR API key instantly, with no human steps. Pass an optional email to unlock the larger free tier (about 100 credits/day, vs about 50/day for an email-less trial key). Store the returned key and pass it as api_key on future calls.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Optional email to attach for the larger free tier and a verification link. |
No output schema declared.
No examples provided.
extract_document ~250
Extract STRUCTURED FIELDS from a document image: invoices, receipts, ID cards — or any custom JSON schema you supply. Every field returns {value, confidence, box} where the confidence and box come from the OCR geometry (never model guesswork); absent fields are null. preset="zatca" additionally decodes the Saudi ZATCA e-invoice QR (TLV) and cross-validates it against the printed fields — use it for Saudi tax invoices. Arabic-first accuracy. 2 credits/page (zatca 4).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional Auto-Reader OCR key (nsk_live_...). If omitted, a free trial key is auto-provisioned and returned to you in the result. |
| image_base64 | string | yes | The document image as base64 (data: URI prefix accepted). |
| lang | string | – | Language hint; default auto. |
| preset | string | – | Built-in schema. Use zatca for Saudi e-invoices (adds QR validation). |
| schema | object | – | Custom extraction schema instead of a preset: an object whose keys are the fields you want, values describing them, e.g. {"policy_number": "string|null"}. |
No output schema declared.
No examples provided.
get_usage ~67
Check your Auto-Reader OCR key: tier, remaining daily free credits, prepaid credit balance, subscription allowance, and per-minute rate limit. Use it to throttle yourself before hitting a limit.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional key (nsk_live_...). Auto-provisioned if omitted. |
No output schema declared.
No examples provided.
ocr_and_translate ~150
One call: OCR an image, then translate every line into target_lang. Arabic-first OCR and manga-aware Japanese with right-to-left-aware layout, followed by LLM translation. Automatic source-language detection. Provide the image as base64. Ideal for reading foreign documents, signs, manga, or receipts end-to-end in a single step.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional key (nsk_live_...). Auto-provisioned if omitted. |
| image_base64 | string | yes | The image encoded as base64 (a data: URI prefix is accepted and stripped). |
| target_lang | string | yes | Language to translate into, as a name or code (e.g. English, ar, ja). |
No output schema declared.
No examples provided.
ocr_image ~377
Extract text from an image with GPU OCR. Best-in-class Arabic (plus Persian/Urdu) accuracy, manga-aware vertical Japanese, and strong English, French, Spanish, German, Chinese, Korean, Russian, Italian and Portuguese — 13+ languages. Automatic language and script detection with lang="auto". Returns reading-order layout text (right-to-left aware, paragraph-gapped) that is ready to feed an LLM or show a human, plus the detected language, the engine used, and the number of text blocks found. Provide the image as base64. Use the mode hint (document | receipt | manga | scene) to tune detection.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional Auto-Reader OCR key (nsk_live_...). If omitted, a free trial key is auto-provisioned and returned to you in the result. |
| image_base64 | string | yes | The image encoded as base64 (a data: URI prefix is accepted and stripped). |
| lang | string | – | Language/script hint. Default "auto" detects it. Codes: ar, fa, ur, en, fr, es, de, ja, zh, ko, ru, it, pt. |
| mode | string | – | Content hint that tunes detection and prompts. Default "document". |
| quality | string | – | "standard" (default) lets a confidence gate decide whether the vision model re-reads the page. "high" always re-reads it — use when accuracy matters more than cost or latency (costs 2 extra credits a… |
No output schema declared.
No examples provided.
read_manga ~237
OCR a comic/manga page, routed by LANGUAGE (not the blanket "manga = Japanese" assumption). Japanese goes to the manga specialist reader that reads vertical, hand-lettered speech bubbles in right-to-left order; Korean manhwa, Chinese manhua and other scripts use their own OCR pack; low-confidence pages escalate to the vision model. Returns text blocks in reading order plus the detected language, the engine used, and whether the page is vertical. Provide the image as base64. Pass lang explicitly (ko/zh/...) for the best non-Japanese result; default "auto" detects it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional Auto-Reader OCR key (nsk_live_...). If omitted, a free trial key is auto-provisioned and returned to you in the result. |
| image_base64 | string | yes | The manga/comic page as base64 (a data: URI prefix is accepted and stripped). |
| lang | string | – | Language hint. Default "auto". Codes: ja (manga specialist), ko, zh, ar, en, fr, es, de, ru, it, pt. |
No output schema declared.
No examples provided.
translate_text ~229
Translate text between 13+ languages with an LLM. Arabic-first quality, with formality control (formal/informal) and optional context to disambiguate meaning. Handles both short dictionary-style word lookups and full documents. Returns the translation and, when available, alternative phrasings. For a WHOLE book (EPUB/DOCX/TXT/PDF), use the REST API instead: upload with POST /v1/illustrate/book/analyse, then POST /v1/text-book {analysis_id, mode: translate|rewrite|extract} (1 credit per 3,000 chars; see /llms.txt).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional key (nsk_live_...). Auto-provisioned if omitted. |
| context | string | – | Optional background text that improves accuracy (it is not translated). |
| formality | string | – | Optional register for the output. |
| target_lang | string | yes | Target language, as a name or code (e.g. English, Arabic, ar, ja, fr). |
| text | string | yes | The text to translate. |
No output schema declared.
No examples provided.
How do I install the com.auto-reader/ocr MCP server?
com.auto-reader/ocr is a hosted endpoint at https://api.auto-reader.com/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 · api.auto-reader.com
claude mcp add --transport http com-auto-reader-ocr 'https://api.auto-reader.com/mcp'
What is the com.auto-reader/ocr MCP server?
com.auto-reader/ocr is an MCP server listed in the public MCP registry as com.auto-reader/ocr. Arabic-first OCR, translation and document extraction. First call mints a free trial key. This page covers its hosted endpoint (https://api.auto-reader.com/mcp).
Is the com.auto-reader/ocr MCP server safe to use?
com.auto-reader/ocr scores 71 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.auto-reader/ocr MCP server expose?
com.auto-reader/ocr exposes 7 tools: extract_document, ocr_image, read_manga, translate_text, ocr_and_translate, and 2 more. Their descriptions and schemas cost roughly 1,398 tokens of context every time the server is loaded.
Does the com.auto-reader/ocr MCP server require authentication?
No. We connected to com.auto-reader/ocr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.auto-reader/ocr MCP server still maintained?
com.auto-reader/ocr 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.auto-reader/ocr MCP server?
VerifyMCP ran 11 checks on com.auto-reader/ocr, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about com.auto-reader/ocr: Authorization and HTTPS. 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.