doc2json
REMOTE · DOC2JSON.MANOONLABS.COM
Turn PDFs and photos into typed JSON with your own schema. Missing values come back null.
Available components
Last scanned (22 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 4 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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. 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 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 Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1206 tokens (~201/item across 6 items; 6 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 Management17
- Stability observed for 5 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 6 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Tool “parse_document” rewrote its description, which is the text the model reads security
- “parse_document” added an optional parameter “citations” cosmetic
- 31 Oct 26 0
- Tool “parse_document” rewrote its description, which is the text the model reads security
- Schema quality: 159 → 183 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “parse_document” added an optional parameter “file_base64” cosmetic
- “parse_document” added an optional parameter “text” cosmetic
- “parse_document” dropped the optional parameter “document” cosmetic
- 30 Oct 26 74
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 4 Nov 2026 · Probed https://doc2json.manoonlabs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=doc2json.manoonlabs.com | CN=YE1,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5516b0bd048bbba304e9c54292bdbce9062 |
| SANs: doc2json.manoonlabs.com | ||||||
| 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 doc2json.manoonlabs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| manoonlabs.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="doc2json", error_description="Get a key at https://doc2json.manoonlabs.com"
Bearer realm="doc2json", error_description="Get a key at https://doc2json.manoonlabs.com"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | upgrade-insecure-requests |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://doc2json.manoonlabs.com/mcp | Verified | 200 | |
| http (plaintext) | http://doc2json.manoonlabs.com/mcp | HTTPS enforced | 301 | https://doc2json.manoonlabs.com/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_schema ~293
Save a named extraction schema in this workspace. A schema is {"type":"object","properties":{...}}. Each property is {"type":T} where T is one of any, null, boolean, string, number, date, array, object. An optional description, at most 400 characters, tells the model how to read that field. An optional required array lists the keys that must be present. A date is a string yyyy-mm-dd. An array adds "items" (one node). An object adds "properties" and may add "required". At most 4 levels below the root, 100 keys, and 16384 bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Lowercase letters, digits, underscores, and hyphens. No spaces. |
| schema | object | yes | A schema is {"type":"object","properties":{...}}. Each property is {"type":T} where T is one of any, null, boolean, string, number, date, array, object. An optional description, at most 400 character… |
No output schema declared.
No examples provided.
get_schema ~38
Read one saved extraction schema by name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Lowercase letters, digits, underscores, and hyphens. No spaces. |
No output schema declared.
No examples provided.
list_schemas ~18
List the extraction schemas saved in this workspace.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
parse_document ~525
Extract invoice fields from a PDF, PNG, JPEG, or text file sent as base64 in file_base64, or from plain text sent in text (10 MB and 10 pages on Free, 25 MB and 50 pages on paid). 1 credit per page; an image is 1 page; text is 1 credit per 3,000 characters. Nothing is stored. Send exactly one of file_base64 or text. The result has status and values. Set citations to true to also get, for each value, the page, the printed text, and a box where it was read.
| Name | Type | Req | Description |
|---|---|---|---|
| citations | boolean | – | When true, the result also has citations: for each value's path, the page, the printed text it was read from, a box [x0, y0, x1, y1] on the page (0 to 1 from the top left), and a status saying whethe… |
| file_base64 | string | – | Base64-encoded PDF, PNG, JPEG, or UTF-8 text file (.txt, .md, .csv, .eml). At most 10 MB and 10 pages on Free, 25 MB and 50 pages on paid plans. Each page costs 1 credit; an image is 1 page; text is… |
| schema | – | – | The name of a schema saved in this workspace, or a literal schema object. A schema is {"type":"object","properties":{...}}. Each property is {"type":T} where T is one of any, null, boolean, string, n… |
| text | string | – | The document as plain text, for example a pasted invoice or email. 1 credit per 3,000 characters (started), at least 1. At most 30,000 characters on Free and 150,000 on paid plans. The text is not st… |
No output schema declared.
No examples provided.
update_schema ~307
Rename a saved schema, replace its definition, or both. A schema is {"type":"object","properties":{...}}. Each property is {"type":T} where T is one of any, null, boolean, string, number, date, array, object. An optional description, at most 400 characters, tells the model how to read that field. An optional required array lists the keys that must be present. A date is a string yyyy-mm-dd. An array adds "items" (one node). An object adds "properties" and may add "required". At most 4 levels below the root, 100 keys, and 16384 bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The current name. |
| newName | string | – | Lowercase letters, digits, underscores, and hyphens. No spaces. |
| schema | object | – | A schema is {"type":"object","properties":{...}}. Each property is {"type":T} where T is one of any, null, boolean, string, number, date, array, object. An optional description, at most 400 character… |
No output schema declared.
No examples provided.
whoami ~25
Return the workspace and token for the bearer credential, and the credits left this month.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the doc2json MCP server?
doc2json is a hosted endpoint at https://doc2json.manoonlabs.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 · doc2json.manoonlabs.com
claude mcp add --transport http com-manoonlabs-doc2json 'https://doc2json.manoonlabs.com/mcp'
What is the doc2json MCP server?
doc2json is an MCP server listed in the public MCP registry as com.manoonlabs/doc2json. Turn PDFs and photos into typed JSON with your own schema. Missing values come back null. This page covers its hosted endpoint (https://doc2json.manoonlabs.com/mcp).
Is the doc2json MCP server safe to use?
doc2json scores 76 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 doc2json MCP server expose?
doc2json exposes 6 tools: whoami, parse_document, list_schemas, get_schema, create_schema, update_schema. Their descriptions and schemas cost roughly 1,206 tokens of context every time the server is loaded.
Does the doc2json MCP server require authentication?
Yes. doc2json asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the doc2json MCP server still maintained?
doc2json is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.