PdfParse vs io.github.thestarboy9696/doc-extract-api
PdfParse is an MCP server published by PabloG6. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.thestarboy9696/doc-extract-api is an MCP server published by thestarboy9696. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.0 Downloads/month (npm): 145 Downloads/week (npm): 22 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | PdfParse | io.github.thestarboy9696/doc-extract-api |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.pdfparse.net/mcp) | On your machine (doc-extract-api) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/pablog6/pdfparse-integrations | github.com/thestarboy9696/doc-extract-api |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
PdfParse
Extract PDFs into structured tables, query records, and configure document inbox workflows.
io.github.thestarboy9696/doc-extract-api
SchemaLock — paid extraction: JSON from docs via your schema, x402/USDC.
How to run each
PdfParse As a remote MCP server
claude mcp add --transport http pdfparse https://mcp.pdfparse.net/mcp
io.github.thestarboy9696/doc-extract-api As a local MCP server: npm package
claude mcp add --env "WALLET_PRIVATE_KEY=<YOUR_WALLET_PRIVATE_KEY>" --transport stdio doc-extract-api -- npx -y doc-extract-api
Requires: WALLET_PRIVATE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only PdfParse has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of PdfParse publish no settings it asks for, so we do not compare settings.
What it can do: PdfParse · What it can do: io.github.thestarboy9696/doc-extract-api · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.