Ext Ops Panel
Open dashboard
Comparison

deepread vs Docs-to-JSON

deepread is a plugin bundle for AI coding tools published by deepread-tech. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Docs-to-JSON is an MCP server published by Alex-Dev-Web-C-DE. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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

Where each is published
MarketplacedeepreadDocs-to-JSON
Claude Code: claude-plugins-community Listed
Version: 3.0.0
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

deepread vs Docs-to-JSON
FactdeepreadDocs-to-JSON
Marketplaces that list it11
Stars (GitHub) (differs)4No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (document-to-json-mcp.mcpize.run/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/deepread-tech/skillsgithub.com/alex-dev-web-c-de/document-to-json-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

deepread

In its own words, on Claude Code: claude-plugins-community:

AI-native document processing API for AI agents. Extract text and structured data from PDFs and images with 97%+ accuracy using multi-model consensus. Includes OCR extraction, PDF form filling, PII redaction (14 types, HIPAA/GDPR ready), and Bring Your Own Key (BYOK) for zero LLM costs. Free 2,000 pages/month.

Docs-to-JSON

In its own words, on Official MCP Registry:

Convert documents to structured JSON (invoices, receipts, contracts) in 2 seconds

How to run each

deepread As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install deepread@claude-community

Docs-to-JSON As a remote MCP server

Claude Code
claude mcp add --transport http document-to-json-mcp https://document-to-json-mcp.mcpize.run/mcp

Commands 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: deepread · What it can do: Docs-to-JSON · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built