_ registry / mcp streamable-http · checked 1h ago

docparser-mcp

https://docparser.usefulapi.io

Registry code: 13c2a2f6b096c1c7

api record

Tools for Docparser, hosted by usefulapi.io. Read-only tools never change data; ask the user before a tool that creates, changes or deletes Docparser data. Free plan: 100 tool calls per month. Run docparser_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run docparser_request_feature to record the request. Pro (unlimited calls, $9/month or $90/year): when the user wants more calls or reaches the limit, run docparser_upgrade; it returns a Stripe Checkout link for the user to open.…

endpoint
https://docparser.usefulapi.io/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is docparser-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is docparser-mcp free to use?
No — it asks for a key or a login before it will serve.
What tools does docparser-mcp have?
9 tools: docparser_ping, docparser_list_parsers, docparser_list_parser_models, docparser_get_document_status, docparser_list_document_results, docparser_fetch_document_from_url, docparser_upload_document, docparser_reparse_documents, ….
Is docparser-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
303ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
9 auth-required 9 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • docparser_ping auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • docparser_list_parsers auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • docparser_list_parser_models auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "parser_id"
  ],
  "properties": {
    "parser_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "Docparser parser id (from docparser_list_parsers)."
    }
  }
}
    arguments 14 lines
  • docparser_get_document_status auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "parser_id",
    "document_id"
  ],
  "properties": {
    "parser_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "Docparser parser id (from docparser_list_parsers)."
    },
    "document_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "Docparser document id (the `id` / `document_id` of an uploaded document)."
    }
  }
}
    arguments 20 lines
  • docparser_list_document_results auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "parser_id"
  ],
  "properties": {
    "date": {
      "type": "string",
      "maxLength": 40,
      "minLength": 8,
      "description": "ISO 8601 date-time (e.g. 2026-10-01T00:00:00Z) or a Unix timestamp. Required with list=uploaded_after or processed_after."
    },
    "list": {
      "enum": [
        "last_uploaded",
        "uploaded_after",
        "processed_after"
      ],
      "type": "string",
      "description": "Which documents (default last_uploaded). uploaded_after and processed_after need `date`."
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Documents per call, 1-100 (default 10)."
    },
    "format": {
      "enum": [
        "object",
        "flat"
      ],
      "type": "string",
      "description": "`object` (default): nested data. `flat`: simple key/value pairs."
    },
    "offset": {
      "type": "integer",
      "maximum": 100000,
      "minimum": 0,
      "description": "Skip this many documents (default 0). Pass the previous reply's next_offset."
    },
    "sort_by": {
      "enum": [
        "parsed_at",
        "processed_at",
        "uploaded_at",
        "first_processed_at",
        "imported_at",
        "integrated_at",
        "dispatched_webhook_at",
        "preprocessed_at"
      ],
      "type": "string",
      "description": "Sort field (default: upload order)."
    },
    "parser_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "Docparser parser id (from docparser_list_parsers)."
    },
    "remote_id": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Only documents uploaded with this remote_id."
    },
    "sort_order": {
      "enum": [
        "ASC",
        "DESC"
      ],
      "type": "string",
      "description": "Default DESC."
    },
    "include_processing_queue": {
      "type": "boolean",
      "description": "Also include documents that are not fully processed yet."
    }
  }
}
    arguments 81 lines
  • docparser_fetch_document_from_url auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "parser_id",
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 8,
      "description": "Public http(s) URL of the file (PDF, image, Word, Excel, CSV, ...)."
    },
    "parser_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "Docparser parser id (from docparser_list_parsers)."
    },
    "remote_id": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Your own reference for the document (stored by Docparser; usable as a filter later)."
    }
  }
}
    arguments 27 lines
  • docparser_upload_document auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "parser_id",
    "file_content"
  ],
  "properties": {
    "file_name": {
      "type": "string",
      "maxLength": 255,
      "minLength": 1,
      "description": "File name with extension (e.g. invoice.pdf); a time-based name is used if omitted."
    },
    "parser_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "Docparser parser id (from docparser_list_parsers)."
    },
    "remote_id": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Your own reference for the document (stored by Docparser; usable as a filter later)."
    },
    "file_content": {
      "type": "string",
      "pattern": "^[A-Za-z0-9+/=_-]+$",
      "maxLength": 8388608,
      "minLength": 4,
      "description": "The file, base64 encoded."
    }
  }
}
    arguments 34 lines
  • docparser_reparse_documents auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "parser_id",
    "document_ids"
  ],
  "properties": {
    "parser_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "Docparser parser id (from docparser_list_parsers)."
    },
    "document_ids": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]{1,64}$",
        "description": "Docparser document id (the `id` / `document_id` of an uploaded document)."
      },
      "maxItems": 50,
      "minItems": 1,
      "description": "Ids of the documents to re-parse."
    }
  }
}
    arguments 26 lines
  • docparser_get_document_results auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "parser_id",
    "document_id"
  ],
  "properties": {
    "format": {
      "enum": [
        "object",
        "flat"
      ],
      "type": "string",
      "description": "`object` (default): nested data. `flat`: simple key/value pairs."
    },
    "parser_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "Docparser parser id (from docparser_list_parsers)."
    },
    "document_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "Docparser document id (the `id` / `document_id` of an uploaded document)."
    },
    "include_children": {
      "type": "boolean",
      "description": "Also return data of child documents created during preprocessing (for example split documents)."
    }
  }
}
    arguments 32 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 13c2a2f6b096c1c7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/13c2a2f6b096c1c7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/13c2a2f6b096c1c7/badge.svg)](https://brick.blue/agent/13c2a2f6b096c1c7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on usefulapi.io 131 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

123 more sit on this domain. All of them.