# Docparser MCP by usefulapi (remote · docparser.usefulapi.io)

Run Docparser parsers: import documents by URL or upload, check status, read parsed results.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `docparser.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-docparser/docparser.md), [page](https://verifymcp.io/servers/io-usefulapi-docparser/docparser)

## Channel facts

- Endpoint: `https://docparser.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-docparser 'https://docparser.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-docparser": {
      "url": "https://docparser.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-docparser": {
      "type": "http",
      "url": "https://docparser.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-docparser]
url = "https://docparser.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-docparser": {
      "type": "remote",
      "url": "https://docparser.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-docparser --url 'https://docparser.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-docparser:
    url: "https://docparser.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-docparser": {
      "Transport": "http",
      "Url": "https://docparser.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-docparser -t streamable-http -u 'https://docparser.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-docparser": {
      "type": "http",
      "url": "https://docparser.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 65, +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.

### 2026-10-15 (score 64, +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.

### 2026-10-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] 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

### 2026-10-13 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 61)

First indexed and scored.

## MCP tools (9)

### `docparser_ping` (~37 tokens)

Check API key

Check that the connected Docparser API key works. Returns {msg: "pong"} when it does. GET /v1/ping.

### `docparser_list_parsers` (~44 tokens)

List parsers

List all Document Parsers on the account (id and label). Start here: the parser id is needed by every other tool. GET /v1/parsers.

### `docparser_list_parser_models` (~52 tokens)

List parser model layouts

List the model layouts of one parser (id and label). GET /v1/parser/models/{parser_id}.

Input parameters:

- `parser_id` (string, required): Docparser parser id (from docparser_list_parsers).

### `docparser_get_document_status` (~143 tokens)

Get document status

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}.

Input parameters:

- `document_id` (string, required): Docparser document id (the `id` / `document_id` of an uploaded document).
- `parser_id` (string, required): Docparser parser id (from docparser_list_parsers).

### `docparser_get_document_results` (~151 tokens)

Get parsed data of one document

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}.

Input parameters:

- `document_id` (string, required): 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, required): Docparser parser id (from docparser_list_parsers).

### `docparser_list_document_results` (~288 tokens)

List parsed data of many documents

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}.

Input parameters:

- `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, required): 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.

### `docparser_fetch_document_from_url` (~208 tokens)

Import a document from a URL

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}.

Input parameters:

- `parser_id` (string, required): 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, required): Public http(s) URL of the file (PDF, image, Word, Excel, CSV, ...).

### `docparser_upload_document` (~207 tokens)

Upload a document (base64)

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}.

Input parameters:

- `file_content` (string, required): 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, required): Docparser parser id (from docparser_list_parsers).
- `remote_id` (string): Your own reference for the document (stored by Docparser; usable as a filter later).

### `docparser_reparse_documents` (~105 tokens)

Re-parse documents

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}.

Input parameters:

- `document_ids` (array, required): Ids of the documents to re-parse.
- `parser_id` (string, required): Docparser parser id (from docparser_list_parsers).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-docparser/docparser#diagnostics

## Score history

- 2026-10-18: 65
- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://docparser.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/docparser/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-docparser/docparser.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-docparser/docparser.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-docparser/docparser