Parsedoc is answering right now. Last checked 6 min ago.
Agent-native document parsing: PDF, scans and FR/EU invoices to structured JSON or Markdown.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
claude mcp add parsedoc --transport http https://parsedoc.custom-digital-services.fr/api/mcp
{
"mcpServers": {
"parsedoc": {
"url": "https://parsedoc.custom-digital-services.fr/api/mcp"
}
}
}
[mcp_servers.parsedoc]
url = "https://parsedoc.custom-digital-services.fr/api/mcp"
{
"mcpServers": {
"parsedoc": {
"url": "https://parsedoc.custom-digital-services.fr/api/mcp"
}
}
}
{
"mcpServers": {
"parsedoc": {
"url": "https://parsedoc.custom-digital-services.fr/api/mcp"
}
}
}
This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://parsedoc.custom-digital-services.fr/api/mcp | streamable-http | needs key | 196 ms | 6 min ago |
Turn any PDF into structured JSON via AI + OCR: invoices, bank statements, contracts.
Generate invoice, receipt, and report PDFs from structured JSON via a single API call.
Parse receipts & invoices into structured JSON. Pay per call in USDC (x402 on Base), no API key.
PolyDoc MCP server: HTML/URL to PDF, screenshots, and EU e-invoice generation for MCP clients.
Stripe-native marketplace where AI agents discover and pay per call for API services.
Documents in, reconciled double-entry books out. Statements, invoices, receipts, matched and posted.
Japanese document AI for agents — invoice/meishi extraction, OCR, classification (hosted API).
Turn messy text into strict JSON schemas agents can trust (invoice, receipt, contact, resume).
Answers built from our own checks of this server.