com.mcparmory/pdfco vs com.pdfintact/pdfintact
com.mcparmory/pdfco is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). com.pdfintact/pdfintact is an MCP server published by pdfintact.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  com.mcparmory/pdfco |  com.pdfintact/pdfintact |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (PyPI): 818 Downloads/week (PyPI): 148 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 1.0.0 No figure published 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 | com.mcparmory/pdfco | com.pdfintact/pdfintact |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 32 | No figure on GitHub |
| Forks (GitHub) (differs) | 4 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcparmory-pdfco) | Remote server (mcp.pdfintact.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mcparmory/registry | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 h ago, requires authentication |
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
com.mcparmory/pdfco
Extract data, edit, convert, and parse PDF documents with OCR and AI
com.pdfintact/pdfintact
Extract tables, text and formulas from PDFs, including scanned pages and broken text layers.
How to run each
com.mcparmory/pdfco As a local MCP server: PyPI package
claude mcp add --transport stdio pdfco -- uvx mcparmory-pdfcocom.pdfintact/pdfintact As a remote MCP server
claude mcp add --transport http pdfintact https://mcp.pdfintact.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.pdfintact/pdfintact 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
Neither one's marketplaces publish the settings it asks for.
What it can do: com.mcparmory/pdfco · What it can do: com.pdfintact/pdfintact · 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.