Home / MCP registry index / io.usefulapi/docparser
Docparser MCP by usefulapi
io.usefulapi/docparser in the official MCP registry.
Endpoint https://docparser.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Run Docparser parsers: import documents by URL or upload, check status, read parsed results.
We read its 9 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
docparser_ping docparser_list_parsers docparser_list_parser_models docparser_get_document_status docparser_get_document_results docparser_list_document_results docparser_fetch_document_from_url docparser_upload_document docparser_reparse_documents
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-docparser)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.