Docparser MCP by usefulapi
REMOTE · DOCPARSER.USEFULAPI.IO
Run Docparser parsers: import documents by URL or upload, check status, read parsed results.
Available components
Last scanned (9 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability82
- 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
- Context-footprint check failed: tool/resource definitions use about 1443 tokens (~160/item across 9 items; 9 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 Management20
- Stability observed for 6 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.
- 17 Oct 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.
- 15 Oct 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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
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 18 Oct 2026 · Probed https://docparser.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 docparser.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://docparser.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://docparser.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://docparser.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://docparser.usefulapi.io/mcp |
| Authorisation server | https://docparser.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docparser.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/docparser/ |
| http (plaintext) | http://docparser.usefulapi.io/mcp | Inconclusive | 302 | http://docparser.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 →
docparser_fetch_document_from_url Import a document from a URL ~208
WRITE: ask Docparser to download a document from a publicly reachable URL and parse it with the given parser. Uses page credits of the account's plan (documents queue when credits run out). Docparser may buy extra credits by itself only if the account owner turned on automatic credit replenishment, or the account is on an annual plan that renews early when credits run out - check the Docparser billing settings first. This server never buys credits or changes the plan. Returns the new document_id: poll docparser_get_document_status, then read docparser_get_document_results. POST /v2/document/fetch/{parser_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| parser_id | string | yes | Docparser parser id (from docparser_list_parsers). |
| remote_id | string | – | Your own reference for the document (stored by Docparser; usable as a filter later). |
| url | string | yes | Public http(s) URL of the file (PDF, image, Word, Excel, CSV, ...). |
No output schema declared.
No examples provided.
docparser_get_document_results Get parsed data of one document ~151
The parsed data of one document (the fields and tables the parser extracted, plus file name, page count and upload/processing times). Docparser allows 60 of these calls per minute. GET /v1/results/{parser_id}/{document_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | Docparser document id (the `id` / `document_id` of an uploaded document). |
| format | string | – | `object` (default): nested data. `flat`: simple key/value pairs. |
| include_children | boolean | – | Also return data of child documents created during preprocessing (for example split documents). |
| parser_id | string | yes | Docparser parser id (from docparser_list_parsers). |
No output schema declared.
No examples provided.
docparser_get_document_status Get document status ~143
Processing status of one document: importing/processing flags, page count, timestamps (uploaded, imported, processed), webhook dispatch and failed jobs. Poll this after a fetch/upload: the document is done when importing_in_progress and processing_in_progress are false, processed_at is set and failed_jobs is empty (a non-empty failed_jobs means it failed); then read the results. GET /v2/document/status/{parser_id}/{document_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | Docparser document id (the `id` / `document_id` of an uploaded document). |
| parser_id | string | yes | Docparser parser id (from docparser_list_parsers). |
No output schema declared.
No examples provided.
docparser_list_document_results List parsed data of many documents ~288
Parsed data of several documents of one parser: the last uploaded ones (default), or those uploaded/processed after a date. Returns up to 100 documents per call; page with offset (next_offset is null on the last page). Docparser allows 30 of these calls per minute. GET /v1/results/{parser_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | ISO 8601 date-time (e.g. 2026-10-01T00:00:00Z) or a Unix timestamp. Required with list=uploaded_after or processed_after. |
| format | string | – | `object` (default): nested data. `flat`: simple key/value pairs. |
| include_processing_queue | boolean | – | Also include documents that are not fully processed yet. |
| limit | integer | – | Documents per call, 1-100 (default 10). |
| list | string | – | Which documents (default last_uploaded). uploaded_after and processed_after need `date`. |
| offset | integer | – | Skip this many documents (default 0). Pass the previous reply's next_offset. |
| parser_id | string | yes | Docparser parser id (from docparser_list_parsers). |
| remote_id | string | – | Only documents uploaded with this remote_id. |
| sort_by | string | – | Sort field (default: upload order). |
| sort_order | string | – | Default DESC. |
No output schema declared.
No examples provided.
docparser_list_parser_models List parser model layouts ~52
List the model layouts of one parser (id and label). GET /v1/parser/models/{parser_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| parser_id | string | yes | Docparser parser id (from docparser_list_parsers). |
No output schema declared.
No examples provided.
docparser_list_parsers List parsers ~44
List all Document Parsers on the account (id and label). Start here: the parser id is needed by every other tool. GET /v1/parsers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
docparser_ping Check API key ~37
Check that the connected Docparser API key works. Returns {msg: "pong"} when it does. GET /v1/ping.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
docparser_reparse_documents Re-parse documents ~105
WRITE: run the parser again over already imported documents (for example after changing parsing rules). Replaces their parsed data. Re-parsing documents already in the account does not use additional credits. 1-50 document ids per call. POST /v1/document/reparse/{parser_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| document_ids | array | yes | Ids of the documents to re-parse. |
| parser_id | string | yes | Docparser parser id (from docparser_list_parsers). |
No output schema declared.
No examples provided.
docparser_upload_document Upload a document (base64) ~207
WRITE: upload one small file as base64 content to a parser and parse it. Uses page credits of the account's plan. Docparser may buy extra credits by itself only if the account owner turned on automatic credit replenishment, or the account is on an annual plan that renews early when credits run out - check the Docparser billing settings first. This server never buys credits or changes the plan. Prefer docparser_fetch_document_from_url for large files. Returns the new document id and the remaining quota. POST /v1/document/upload/{parser_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| file_content | string | yes | The file, base64 encoded. |
| file_name | string | – | File name with extension (e.g. invoice.pdf); a time-based name is used if omitted. |
| parser_id | string | yes | Docparser parser id (from docparser_list_parsers). |
| remote_id | string | – | Your own reference for the document (stored by Docparser; usable as a filter later). |
No output schema declared.
No examples provided.
How do I install the Docparser MCP by usefulapi server?
Docparser MCP by usefulapi is a hosted endpoint at https://docparser.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 · docparser.usefulapi.io
claude mcp add --transport http io-usefulapi-docparser 'https://docparser.usefulapi.io/mcp'
What is the Docparser MCP by usefulapi server?
Docparser MCP by usefulapi is listed in the public MCP registry as io.usefulapi/docparser. Run Docparser parsers: import documents by URL or upload, check status, read parsed results. This page covers its hosted endpoint (https://docparser.usefulapi.io/mcp).
Is the Docparser MCP by usefulapi server safe to use?
Docparser MCP by usefulapi scores 65 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 Docparser MCP by usefulapi server expose?
Docparser MCP by usefulapi exposes 9 tools: docparser_ping, docparser_list_parsers, docparser_list_parser_models, docparser_get_document_status, docparser_get_document_results, and 4 more. Their descriptions and schemas cost roughly 1,235 tokens of context every time the server is loaded.
Does the Docparser MCP by usefulapi server require authentication?
Yes. Docparser MCP by usefulapi 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 Docparser MCP by usefulapi server still maintained?
Docparser MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.