Ext Ops Panel
Open dashboard
Comparison

waza-read vs Jina Reader

waza-read is a plugin bundle for AI coding tools published by tw93. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Jina Reader is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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
Marketplacewaza-readJina Reader
Community marketplace tw93/waza Listed
Version: 3.42.0
Forks (GitHub): 436
Stars (GitHub): 7 578
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
Downloads/month (npm): 870
Downloads/week (npm): 128
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

waza-read vs Jina Reader
Factwaza-readJina Reader
Marketplaces that list it11
Stars (GitHub) (differs)7 578 (better)0 (worse)
Forks (GitHub) (differs)436 (better)0 (worse)
Last release (differs)2026-11-11 (better)2026-11-02 (worse)
Where it runs (differs)Installs as a plugin bundleRemote server (gateway.pipeworx.io/jina-reader/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/tw93/wazagithub.com/pipeworx-io/mcp-jina-reader
Changes in the last 7 days (differs)30
First seen (differs)2026-11-092026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (13 h ago)

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

waza-read

In its own words, on Community GitHub marketplaces:

Fetches URLs and PDFs, then summarizes or returns clean Markdown; can also search the web through DeepSeek when built-in search is thin. Use when asked to read, fetch, quote, cite, convert, or save a URL or PDF. Not for local text files already in the repo.

Jina Reader

In its own words, on Official MCP Registry:

Jina AI Reader/Search MCP — turn any URL into clean LLM-ready markdown, plus web search.

How to run each

waza-read As a Claude Code plugin

Claude Code
/plugin marketplace add tw93/waza
/plugin install waza-read@waza

Jina Reader As a remote MCP server

Claude Code
claude mcp add --transport http jina-reader https://gateway.pipeworx.io/jina-reader/mcp

Requires: PIPEWORX_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Jina Reader 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 waza-read publish no settings it asks for, so we do not compare settings.

What it can do: waza-read · What it can do: Jina Reader · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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