doc.page PDF Extraction
REMOTE · DOC.PAGE
Extract PDFs to Markdown, RAG chunks and cited tables; publish tracked Doc Links with read stats.
Available components
Last scanned (11 minutes ago)
Scores higher than 66% 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 Security57
- 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 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 844 tokens (~120/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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "create_doc_link" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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
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.
- 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
- 25 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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 5 Nov 2026 · Probed https://doc.page/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=doc.page | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 69bf72e2794ee7d0131f61cee9ca571a |
| SANs: doc.page | ||||||
| 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 doc.page. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| page. | present | 64712 | 8 | Verified |
| doc.page. | 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://doc.page/api/mcp | Verified | 200 | |
| http (plaintext) | http://doc.page/api/mcp | HTTPS enforced | 301 | https://doc.page/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_doc_link ~184
Publish a PDF as a tracked doc.page Doc Link and get back a shareable URL. The link belongs to the API key's account and also appears in its doc.page library. Requires an API key. Free plan: up to 3 active links; custom vanity slugs are premium-only. Optional expiry and open-notification toggle.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string | – | ISO 8601 date-time after which the link stops working. Omit for no expiry. |
| name | string | – | Display name in the library. Defaults to the filename. |
| notifyOnOpen | boolean | – | Email the account owner on the first open. Default true. |
| slug | string | – | Custom vanity slug (premium plans only). Lowercase letters, digits and hyphens. |
| url | string | yes | http(s) URL of the PDF to publish (max 25 MB). |
No output schema declared.
No examples provided.
extract_pdf ~153
Extract a PDF into clean Markdown and structured elements (headings, paragraphs). Returns the canonical ExtractedDocument object. mode "hybrid" runs a heavier semantic engine that also reconstructs tables and bounding boxes; the default "fast" engine is prose-only (low confidence.tables).
| Name | Type | Req | Description |
|---|---|---|---|
| chunkTokens | integer | – | Target chunk size in tokens (when chunks are requested). Default 512. |
| mode | string | – | fast = prose engine. hybrid = semantic engine with tables + bounding boxes when deployed; falls back to fast with a warning otherwise. |
| outputs | array | – | Subset of outputs to include. Default: markdown and elements. |
| url | string | yes | http(s) URL of the PDF to extract. |
No output schema declared.
No examples provided.
get_chunks ~76
Split a PDF into semantic chunks ready for embeddings (RAG). Each chunk carries its text, estimated tokens, starting page, section heading and the source element ids for citation.
| Name | Type | Req | Description |
|---|---|---|---|
| maxTokens | integer | – | Target chunk size in tokens. Default 512. |
| url | string | yes | http(s) URL of the PDF to chunk. |
No output schema declared.
No examples provided.
get_doc_link_stats ~139
Reading analytics for one Doc Link of the API key's account, by id or slug. Always returns the summary (total views, unique visitors, last visit). Premium plans additionally get countries, visitor companies (as_org) and per-page views + average dwell time; pass include:["visits"] for the recent visit rows. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Doc Link item id (from create_doc_link or list_doc_links). |
| include | array | – | Extra sections. "visits" adds the recent visit rows (enriched on premium plans). |
| slug | string | – | Doc Link slug — alternative to id. |
No output schema declared.
No examples provided.
list_doc_links ~57
List the Doc Links of the API key's account (id, slug, URL, name, disabled/expiry state, total views, last view). Use this to recover links created in earlier sessions before querying stats. Requires an API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tables ~57
Return every table in a PDF as structured JSON (reconstructed rows and columns) with page and bounding box for verifiable citations. Uses the semantic (hybrid) engine.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | http(s) URL of the PDF. |
No output schema declared.
No examples provided.
revoke_doc_link ~83
Disable a Doc Link of the API key's account (by id or slug) so the public URL stops serving. The item and its stats remain in the library; on the free plan this frees an active-link slot. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Doc Link item id. |
| slug | string | – | Doc Link slug — alternative to id. |
No output schema declared.
No examples provided.
How do I install the doc.page PDF Extraction MCP server?
doc.page PDF Extraction is a hosted endpoint at https://doc.page/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 · doc.page
claude mcp add --transport http page-doc-pdf-extract 'https://doc.page/api/mcp'
What is the doc.page PDF Extraction MCP server?
doc.page PDF Extraction is an MCP server listed in the public MCP registry as page.doc/pdf-extract. Extract PDFs to Markdown, RAG chunks and cited tables; publish tracked Doc Links with read stats. This page covers its hosted endpoint (https://doc.page/api/mcp).
Is the doc.page PDF Extraction MCP server safe to use?
doc.page PDF Extraction 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 doc.page PDF Extraction MCP server expose?
doc.page PDF Extraction exposes 7 tools: extract_pdf, get_chunks, list_tables, create_doc_link, list_doc_links, and 2 more. Their descriptions and schemas cost roughly 749 tokens of context every time the server is loaded.
Does the doc.page PDF Extraction MCP server require authentication?
No. We connected to doc.page PDF Extraction without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the doc.page PDF Extraction MCP server still maintained?
doc.page PDF Extraction 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.