Docparser MCP by usefulapi
by FastDrop
Run Docparser parsers: import documents by URL or upload, check status, read parsed results.
Run Docparser parsers: import documents by URL or upload, check status, read parsed results. Official MCP Registry: io.usefulapi/docparser@1.0.0. Remote endpoint: https://docparser.usefulapi.io/mcp
Problem it solves
Discoverable MCP server listed in the official MCP Registry.
How it's different
Remote MCP endpoint ingested from the official registry and probed by FastDrop.
Ingested from the official MCP Registry
FastDrop pulled this entry from the official MCP Registry as io.usefulapi/docparser and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed
and the description is not theirs.
If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.
Claim this listingTools this endpoint exposes
Read directly from the endpoint on 11 Oct 2026. Not supplied by the maker.
docparser_pingCheck that the connected Docparser API key works. Returns {msg: "pong"} when it does. GET /v1/ping.
docparser_list_parsersList 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_modelsList the model layouts of one parser (id and label). GET /v1/parser/models/{parser_id}.
docparser_get_document_statusProcessing 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
docparser_get_document_resultsThe 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/{pa
docparser_list_document_resultsParsed 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
docparser_fetch_document_from_urlWRITE: 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
docparser_upload_documentWRITE: 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 automati
Is this tool yours?
Claim this listing and we’ll verify ownership before handing it over.
Sign in to claim this listingSimilar launches
Matched on shared tags and the tools their MCP servers actually expose.
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Reviews
Sign in to leave a review.
No reviews yet.
Comments
Sign in to join the discussion.
No comments yet - start the discussion.