CoreNexis API vs PDF4me
CoreNexis API is an MCP server published by corenexis.com. Marketplaces we read that list it: 1 (Official MCP Registry). PDF4me is an MCP server published by pdf4me. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |   CoreNexis API |  PDF4me |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (PyPI): 89 Downloads/week (PyPI): 24 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 | CoreNexis API | PDF4me |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-21 | Not published |
| Where it runs (differs) | Remote server (api.corenexis.com/mcp/server) | Remote server (mcp.pdf4me.com/mcp) |
| Transport | Streamable HTTP | 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/core-nexis/corenexis-api | github.com/pdf4me/pdf4me-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | Responded 2 days ago, requires a key |
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
CoreNexis API
PDF from HTML or Markdown, OCR, email validation, image conversion and hosting, QR and barcodes.
PDF4me
PDF & document automation via the PDF4me API — convert, OCR, extract, edit, secure.
How to run each
CoreNexis API As a remote MCP server
claude mcp add --transport http corenexis-api https://api.corenexis.com/mcp/server --header "x-api-key: <YOUR_X_API_KEY>"Requires: x-api-key header
PDF4me As a remote MCP server
claude mcp add --transport http pdf4me-mcp https://mcp.pdf4me.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily 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: CoreNexis API · What it can do: PDF4me · 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.