cheap.doc/mcp
REMOTE · MCP.DOC.CHEAP · 3 COMPONENTS
Passport, ID and MRZ recognition via doc.cheap – Free: 100 documents every month, then $0.01 each
Available components
Last scanned (13 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Documents and Files
Recent critical change
Authorization (29 Sept 2026). See the changelog before you install this server.
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_scan). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 4544 tokens (~59/item across 77 items; 6 tools + 71 resources), lean.Pass
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- 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
- 4 Nov 26 0
- Tool “delete_scan” rewrote its description, which is the text the model reads security
- Tool “get_scan” rewrote its description, which is the text the model reads security
- Tool “list_scans” rewrote its description, which is the text the model reads security
- Tool “scan_document” rewrote its description, which is the text the model reads security
- Server version: 0.3.10 → 0.3.11 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 12 Oct 26 0
- Tool “scan_document” rewrote its description, which is the text the model reads security
- Server version: 0.3.9 → 0.3.10 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 22 Nov 2026 · Probed https://mcp.doc.cheap/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=doc.cheap | CN=WE1,O=Google Trust Services,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 1875474c60b53ac70e23780a25341beb |
| SANs: doc.cheap, *.doc.cheap | ||||||
| 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 secure
Validation of mcp.doc.cheap. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cheap. | DS published | 29881 | 8 | Verified |
| doc.cheap. | DS published | 2371 | 13 | Verified |
| mcp.doc.cheap. | Verified address RRset verified with the apex keys |
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=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.doc.cheap/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.doc.cheap/mcp | HTTPS enforced | 301 | https://mcp.doc.cheap/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 →
check_balance Check remaining credits ~175
Return how many credits are left on the account and what the current period has used: the balance, split into this month's free credits (100 every month, drawn first) and the paid credits, the credits spent, and the scan counters broken down by status (recognized, unreadable, no document found, unsupported document, rejected). Takes no arguments and calls GET /v1/usage; under the public sandbox key it answers without calling anything. One recognised document draws one credit, at $0.01; scans that recognised nothing are counted and never charged. Needs a real API key – under the public sandbox key there is no account behind the call, and the answer says so instead of reporting zeros that read like a balance. Use it before working through a batch of documents, or when a scan is refused for lack of credit.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| balance_credits | – | yes | Credits currently available to the account: this month's free credits plus the paid credits; null for a key with no account (the public sandbox key). |
| credits_spent | integer | yes | Credits charged within the period. |
| credits_spent_by_kind | object | yes | Credits charged within the period, by the kind that paid. |
| free_allowance | – | yes | This month's free credits, drawn before paid credits; null when the account may not draw free credits (its email address is not confirmed, or its free credits were withdrawn) and for a key with no ac… |
| paid_balance_credits | – | yes | Paid credits: bought or granted to the account, drawn once this month's free credits are used up, and never reset; null only for a key with no account (the public sandbox key). |
| period | object | yes | Bounds of the current usage period (UTC calendar month). |
| scans | object | yes | – |
No examples provided.
delete_scan Delete a stored scan ~345
Permanently delete one stored scan now, before its retention window would end. This cannot be undone: the stored result, its history row and its thumbnail are removed, and the scan can no longer be listed, fetched or replayed through its idempotency_key. The credit it drew is not refunded, and this period's usage counters still count it. Input: scan_id – meta.id of a scan_document result, or id of a list_scans row. Output: { id, deleted: true }. Calls DELETE /v1/scans/{id}. Only scans made with a live key under a non-zero retention window are stored for the account, and only until that window ends (retain_hours on the scan, or the account's history-retention setting, one year by default); a scan made with retain_hours 0 was never stored. A key reaches its own account's scans and no other account's. Under a sandbox key nothing can be read back: an account's own sk_sandbox_ key stores nothing, and the public key keeps every scan for one year, with a reduced thumbnail and the address it came from, where that key cannot read, list or delete it. Errors: an id that is unknown, belongs to another account, has passed its window or was already deleted is refused as not_found, and nothing is deleted. Use it when someone asks for a document's data to be removed; confirm the id with list_scans or get_scan first, because the deletion is final.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | The scan's id: meta.id of the scan_document result, or id of a list_scans row (a lower-case UUID). |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | Always true: the stored result is gone and cannot be read back. |
| id | – | yes | – |
No examples provided.
get_scan Fetch a stored scan ~343
Fetch the full result of one stored scan by its id, as it was returned when the document was recognised. Input: scan_id – meta.id of a scan_document result, or id of a list_scans row. Output: the same Scan object scan_document returns (meta, document, holder, fields, mrz and the rest) plus a one-line summary, with two differences: the image crops are never stored, so every images slot is null, and quality reads not_checked. Calls GET /v1/scans/{id}; it never re-runs recognition and never charges a credit. Only scans made with a live key under a non-zero retention window are stored for the account, and only until that window ends (retain_hours on the scan, or the account's history-retention setting, one year by default); a scan made with retain_hours 0 was never stored. A key reaches its own account's scans and no other account's. Under a sandbox key nothing can be read back: an account's own sk_sandbox_ key stores nothing, and the public key keeps every scan for one year, with a reduced thumbnail and the address it came from, where that key cannot read, list or delete it. Errors: an id that is unknown, belongs to another account, was made with retain_hours 0 or has passed its window is refused as not_found – the cases are not told apart. Use it to read back a document recognised earlier instead of scanning the image again.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | The scan's id: meta.id of the scan_document result, or id of a list_scans row (a lower-case UUID). |
| Name | Type | Req | Description |
|---|---|---|---|
| authenticity | – | yes | – |
| document | – | yes | – |
| fields | array | yes | Every field the engine extracted off the printed document, re-keyed to our vocabulary – the open set. Always present; empty when nothing was extracted. A field read in more than one language appears… |
| holder | – | yes | – |
| images | – | yes | – |
| meta | – | yes | – |
| mrz | – | yes | – |
| quality | – | yes | – |
No examples provided.
list_scans List stored scans ~384
List the account's stored scans, most recent first, one page at a time. Inputs: the optional limit (1 to 100 rows, default 20) and cursor (the next_cursor of the previous page; omit it for the first page). Output: scans – one row per scan with id, status (recognized, unreadable, no_document_found, unsupported_document or rejected), billed, duration_ms, reference (your own string from the scan) and created_at – and next_cursor, which is null on the last page. A row holds no extracted data; call get_scan with its id for the full result. Calls GET /v1/scans; it never charges a credit. Only scans made with a live key under a non-zero retention window are stored for the account, and only until that window ends (retain_hours on the scan, or the account's history-retention setting, one year by default); a scan made with retain_hours 0 was never stored. A key reaches its own account's scans and no other account's. Under a sandbox key nothing can be read back: an account's own sk_sandbox_ key stores nothing, and the public key keeps every scan for one year, with a reduced thumbnail and the address it came from, where that key cannot read, list or delete it. Under the public sandbox key the answer is an empty list, given without calling the API. Errors: a cursor this API did not issue is refused (validation_failed); a key the API does not know is refused (unauthorized). Use it to find a scan made earlier – by its reference or its time – before reading or deleting it.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous page; omit it for the first page. |
| limit | integer | – | Rows per page, 1 to 100 (default 20). |
| Name | Type | Req | Description |
|---|---|---|---|
| next_cursor | string|null | yes | Opaque cursor for the next page: send it back as `cursor` to continue after the last row of this one. Null on the last page. |
| scans | array | yes | The account's scans, most recent first. |
No examples provided.
scan_document Recognise a passport or ID document ~567
Recognise a passport, national ID card or driver's licence from a photo or scan and return what is printed on it as structured JSON. Inputs: the image as image_base64 or image_url (https, on a public address); plus the optional expect_country, return_portrait, retain_hours, reference and idempotency_key. Output: a Scan object – meta (id, status, billed, confidence, timing), document (kind, issuing country, number, series, date of issue, date of expiry, whether it has expired and how many days are left), holder (given names, surname, date of birth, sex, nationality) – country codes are the document's own three-letter ICAO codes, each with a *_detail object giving the code as written, its ISO 3166-1 alpha-3 and alpha-2 and its category, fields (every field read off the printed page, each with its own confidence), mrz (whether the machine-readable zone checks out, why not when it does not, and its lines exactly as read), images, quality and authenticity – plus a one-line summary of the same result. Calls POST /v1/scans. Cost: it bills one credit ($0.01) only when a document is recognised; an unreadable image, an empty frame or an unsupported type costs nothing, and meta.billed says which happened. Without a key, the public sandbox key is used. It gives 10 free recognised documents per address in all, and at most 10 requests per address an hour, whatever their answer. Registering gives 100 free documents every month. Use test images only, never a real document. Use it whenever someone hands over an identity document and wants it read, transcribed, or checked against what they claim – a name, a document number, a date of birth or an expiry date.
| Name | Type | Req | Description |
|---|---|---|---|
| expect_country | string | – | ISO 3166-1 alpha-3 country you expect, or omit for any. |
| idempotency_key | string | – | Makes a retried scan return the first result instead of charging again. |
| image_base64 | string | – | The document image as base64 (a data: URL is also accepted). |
| image_url | string | – | https: URL of an image on a public internet address, which the server fetches (25 MB maximum). |
| reference | string | – | Your own correlation string, echoed back in the result. |
| retain_hours | integer | – | Hours the result stays readable via GET /v1/scans/{id} (0 = store nothing). Omit it to use the account's own history-retention setting. |
| return_portrait | boolean | – | Whether to include the holder photograph crop, images.main_photo (default true). |
| Name | Type | Req | Description |
|---|---|---|---|
| authenticity | – | yes | – |
| document | – | yes | – |
| fields | array | yes | Every field the engine extracted off the printed document, re-keyed to our vocabulary – the open set. Always present; empty when nothing was extracted. A field read in more than one language appears… |
| holder | – | yes | – |
| images | – | yes | – |
| meta | – | yes | – |
| mrz | – | yes | – |
| quality | – | yes | – |
No examples provided.
search_docs Search the doc.cheap API documentation ~164
Full-text search over the doc.cheap API documentation – endpoints, request options, every response field, the error codes and what to do about each, MRZ rules, retention and pricing. Takes a query and an optional limit (1 to 20, default 5), and answers with the matching sections: title, a snippet, and a link to the page. It reads a copy of the documentation shipped beside this server, so it makes no network call and works offline. Use it before guessing at a field name, an error code or a scan option – what it returns is the published contract rather than a recollection of it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (default 5). |
| query | string | yes | What to search the documentation for. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Matching sections, best first; empty when nothing matched. |
No examples provided.
How do I install the cheap.doc/mcp server?
cheap.doc/mcp is a hosted endpoint at https://mcp.doc.cheap/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 · mcp.doc.cheap
claude mcp add --transport http cheap-doc-mcp 'https://mcp.doc.cheap/mcp'
What is the cheap.doc/mcp server?
cheap.doc/mcp is listed in the public MCP registry as cheap.doc/mcp. Passport, ID and MRZ recognition via doc.cheap – Free: 100 documents every month, then $0.01 each. This page covers its hosted endpoint (https://mcp.doc.cheap/mcp).
Is the cheap.doc/mcp server safe to use?
cheap.doc/mcp scores 84 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 cheap.doc/mcp server expose?
cheap.doc/mcp exposes 6 tools: scan_document, check_balance, search_docs, list_scans, get_scan, delete_scan. Their descriptions and schemas cost roughly 1,978 tokens of context every time the server is loaded.
Does the cheap.doc/mcp server require authentication?
No. We connected to cheap.doc/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the cheap.doc/mcp server still maintained?
cheap.doc/mcp is still listed as active in the MCP registry. We last reached this channel on 22 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 cheap.doc/mcp server?
VerifyMCP ran 13 checks on cheap.doc/mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.