DocRaptor MCP by usefulapi
REMOTE · DOCRAPTOR.USEFULAPI.IO
Turn HTML or a live URL into polished PDF and Excel files — hosted downloads, async jobs, history.
Available components
Last scanned (2 hours ago)
Scores higher than 4% 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
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 yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's 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.
- 2 Nov 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “create_a_document_as_a_background_job_and_check_it” functional
- New prompt “get_the_ip_addresses_to_allow_on_your_firewall” functional
- New prompt “list_the_documents_generated_recently” functional
- New prompt “make_a_watermarked_test_document_to_check_a_layout” functional
- New prompt “turn_html_or_a_web_page_url_into_a_pdf_or_excel_file” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.32.0 → 1.34.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.2 → 1.31.0 functional
- 30 Oct 26 0
- Server version: 1.30.1 → 1.30.2 functional
- Server version: 1.30.0 → 1.30.1 functional
- 29 Oct 26 0
- Server version: 1.29.0 → 1.30.0 functional
- Server version: 1.28.0 → 1.29.0 functional
- 28 Oct 26 −1
- Tool “docraptor_create_document” rewrote its description, which is the text the model reads security
- Schema quality: 241 → 306 ▼ functional
- Server version: 1.27.0 → 1.28.0 functional
- Server version: 1.25.0 → 1.27.0 functional
- “docraptor_create_document” added an optional parameter “callback_url” cosmetic
- “docraptor_create_document” added an optional parameter “help” cosmetic
- “docraptor_create_document” added an optional parameter “ignore_console_messages” cosmetic
- “docraptor_create_document” added an optional parameter “ignore_resource_errors” cosmetic
- “docraptor_create_document” added an optional parameter “javascript” cosmetic
- “docraptor_create_document” added an optional parameter “referrer” cosmetic
- “docraptor_create_document” added an optional parameter “strict” cosmetic
- “docraptor_create_document” reworded the description of “hosted” cosmetic
- “docraptor_create_document” reworded the description of “test” cosmetic
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 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://docraptor.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 docraptor.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docraptor.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/docraptor/ |
| http (plaintext) | http://docraptor.usefulapi.io/mcp | Inconclusive | 302 | http://docraptor.usefulapi.io/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 →
docraptor_create_document Create a document (PDF/XLS/XLSX) ~697
Generate a PDF or Excel document from HTML (document_content) or a URL (document_url). Exactly one of document_content / document_url is required. By default the document is HOSTED and the tool returns a { download_url } you can fetch — ideal for agents (no large binary in the response). Hosted documents require a paid DocRaptor add-on. Without that add-on, set hosted:false to get the raw document back as base64, or async:true to enqueue a job and poll docraptor_get_document_status. Test mode is enabled by default: PDFs are watermarked and Excel files are limited to 20 rows. Set test:false explicitly to create a real document that consumes account credits (billed). DocRaptor API: POST /docs.
| Name | Type | Req | Description |
|---|---|---|---|
| async | boolean | – | If true, enqueue the job and return a status_id (poll with docraptor_get_document_status). Best for large/slow documents. Default false. |
| callback_url | string | – | URL DocRaptor POSTs after a successful async job (requires async:true). Failed jobs do not trigger callbacks. |
| document_content | string | – | The HTML/XML source to render. Use this OR document_url. |
| document_url | string | – | A URL DocRaptor will fetch and render. Use this OR document_content. |
| help | boolean | – | Enable DocRaptor help mode: emails you and DocRaptor support and retains document contents for review until resolved. Maximum five active help requests. |
| hosted | boolean | – | Default true for synchronous requests, false for async. Requires the paid hosted-documents add-on; each download may be billed. Set false for raw base64 output without the add-on. |
| hosted_download_limit | integer | – | For hosted docs: max number of downloads before the link expires. |
| hosted_expires_at | string | – | For hosted docs: ISO 8601 datetime when the hosted link expires. |
| ignore_console_messages | boolean | – | Ignore JavaScript console messages instead of failing generation. Defaults to false on Pipelines 1–6, true on Pipeline 7+. |
| ignore_resource_errors | boolean | – | Ignore errors downloading CSS/images (DocRaptor default true). Set false to fail generation on resource errors. |
| javascript | boolean | – | Enable DocRaptor's JavaScript engine (default false), recommended for Typekit and Highcharts. Separate from prince_options.javascript; usually enable only one engine. |
| name | string | – | A name for the document (<=200 chars), shown in the DocRaptor dashboard/listing. |
| pipeline | string | – | Rendering pipeline/engine version, e.g. '10'. Omit to use DocRaptor's default. |
| prince_options | object | – | PDF engine (Prince) options. PDF only. |
| referrer | string | – | Explicit referrer for JavaScript requests, e.g. Typekit with document_content. Defaults to document_url. |
| strict | string | – | PDF HTML validation: html fails on invalid HTML; none disables strict HTML validation. |
| tag | string | – | An arbitrary tag string for your own reporting/grouping. |
| test | boolean | – | Default true: generate a FREE test document (watermarked PDF or Excel limited to 20 rows). Set false explicitly for a real, BILLED document. |
| type | string | – | Output format: pdf (default), xls, or xlsx. |
No output schema declared.
No examples provided.
docraptor_get_document_status Get async document status ~88
Check the status of an asynchronous document created with docraptor_create_document({async:true}). Returns status (queued | working | completed | failed), and when completed a download_url / download_id / number_of_pages. DocRaptor API: GET /status/{status_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| status_id | string | yes | The status_id returned by docraptor_create_document when async:true. |
No output schema declared.
No examples provided.
docraptor_list_documents List documents ~99
List metadata for documents created on this account, most recent first (paginated). Note: DocRaptor does not retain the rendered files themselves — this returns metadata such as name, type, test flag, and creation time. DocRaptor API: GET /docs.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Pagination page number. Default 1. |
| per_page | integer | – | Documents per page (max 100). Default 100. |
No output schema declared.
No examples provided.
docraptor_list_ip_addresses List DocRaptor IP addresses ~74
List the IP addresses DocRaptor uses to fetch remote assets / document_url. Useful for allowlisting DocRaptor on a firewall or asset host. (DocRaptor notes these change over time — prefer HTTP Basic auth over IP allowlisting for securing assets.) DocRaptor API: GET /ips.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the DocRaptor MCP by usefulapi server?
DocRaptor MCP by usefulapi is a hosted endpoint at https://docraptor.usefulapi.io/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 · docraptor.usefulapi.io
claude mcp add --transport http io-usefulapi-docraptor 'https://docraptor.usefulapi.io/mcp'
What is the DocRaptor MCP by usefulapi server?
DocRaptor MCP by usefulapi is listed in the public MCP registry as io.usefulapi/docraptor. Turn HTML or a live URL into polished PDF and Excel files, hosted downloads, async jobs, history. This page covers its hosted endpoint (https://docraptor.usefulapi.io/mcp).
Is the DocRaptor MCP by usefulapi server safe to use?
DocRaptor MCP by usefulapi scores 18 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 DocRaptor MCP by usefulapi server expose?
DocRaptor MCP by usefulapi exposes 4 tools: docraptor_create_document, docraptor_get_document_status, docraptor_list_documents, docraptor_list_ip_addresses. Their descriptions and schemas cost roughly 958 tokens of context every time the server is loaded.
Does the DocRaptor MCP by usefulapi server require authentication?
Its publisher declares no required credentials for DocRaptor MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the DocRaptor MCP by usefulapi server still maintained?
DocRaptor MCP by usefulapi 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.
What did VerifyMCP test on the DocRaptor MCP by usefulapi server?
VerifyMCP ran 4 checks on DocRaptor MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about DocRaptor MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.