com.pdfintact/pdfintact vs io.github.Libres-coder/parseflow
com.pdfintact/pdfintact is an MCP server published by pdfintact.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Libres-coder/parseflow is an MCP server published by Libres-coder. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 2 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.pdfintact/pdfintact | io.github.Libres-coder/parseflow |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 2 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.pdfintact.com/mcp) | On your machine (parseflow-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/libres-coder/parseflow |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | 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
com.pdfintact/pdfintact
Extract tables, text and formulas from PDFs, including scanned pages and broken text layers.
io.github.Libres-coder/parseflow
PDF parsing server with text extraction, metadata, search, images, and TOC via MCP
How to run each
com.pdfintact/pdfintact As a remote MCP server
claude mcp add --transport http pdfintact https://mcp.pdfintact.com/mcpio.github.Libres-coder/parseflow As a local MCP server: npm package
claude mcp add --transport stdio parseflow -- npx -y parseflow-mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
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.pdfintact/pdfintact · What it can do: io.github.Libres-coder/parseflow · 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.