mcpbeat

Document to JSON – PDF Invoice/Statement/Contract Parser MCP Server

io.github.fashionmascherine-svg/document-to-json-mcp
answering

Document to JSON – PDF Invoice/Statement/Contract Parser is answering right now. Last checked 8 min ago. Last commit 25 Jun 2026.

Turn any PDF into structured JSON via AI + OCR: invoices, bank statements, contracts.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
430 ms
Response time
average over 24h
8
Stars
last commit 25 Jun 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add document-to-json-mcp --transport http https://mcp.apify.com/?actors=opportunity-biz/document-to-json-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "document-to-json-mcp": {
      "url": "https://mcp.apify.com/?actors=opportunity-biz/document-to-json-mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.document-to-json-mcp]
url = "https://mcp.apify.com/?actors=opportunity-biz/document-to-json-mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "document-to-json-mcp": {
      "url": "https://mcp.apify.com/?actors=opportunity-biz/document-to-json-mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "document-to-json-mcp": {
      "url": "https://mcp.apify.com/?actors=opportunity-biz/document-to-json-mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.apify.com/?actors=opportunity-biz/document-to-json-mcp streamable-http needs key 454 ms 8 min ago

Document to JSON – PDF Invoice/Statement/Contract Parser — questions

Answers built from our own checks of this server.

Why is there no tool list for Document to JSON – PDF Invoice/Statement/Contract Parser?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Document to JSON – PDF Invoice/Statement/Contract Parser working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 430 ms. The bar chart above shows every period we have measured.
How do I connect Document to JSON – PDF Invoice/Statement/Contract Parser?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Document to JSON – PDF Invoice/Statement/Contract Parser need an API key?
Yes. Every time we knock, Document to JSON – PDF Invoice/Statement/Contract Parser answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Document to JSON – PDF Invoice/Statement/Contract Parser?
It answers our handshake in 430 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Document to JSON – PDF Invoice/Statement/Contract Parser open source?
Yes — it is published under the MIT licence, written in Python and 8 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.