Ext Ops Panel
Open dashboard
Comparison

mail-muncher vs io.github.pavel-tashev/rss-feed-reader

mail-muncher is an MCP server published by craigjmidwinter. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.pavel-tashev/rss-feed-reader is an MCP server published by pavel-tashev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
Marketplacemail-muncherio.github.pavel-tashev/rss-feed-reader
Official MCP Registry Listed
Version: 0.4.0
Forks (GitHub): 0
Stars (GitHub): 3
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

mail-muncher vs io.github.pavel-tashev/rss-feed-reader
Factmail-muncherio.github.pavel-tashev/rss-feed-reader
Marketplaces that list it11
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/craigjmidwinter/mail-muncher:0.4.0)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/craigjmidwinter/mail-muncherNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 45 h ago returned HTTP 401

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

mail-muncher

In its own words, on Official MCP Registry:

Filtered, read-only IMAP and Gmail archived to disk as .eml + markdown, served over MCP.

io.github.pavel-tashev/rss-feed-reader

In its own words, on Official MCP Registry:

Read RSS, Atom and JSON feeds, or find the feed of any website, with filters and only-new mode

How to run each

mail-muncher As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio mail-muncher -- docker run -i --rm ghcr.io/craigjmidwinter/mail-muncher:0.4.0 mcp

io.github.pavel-tashev/rss-feed-reader

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Only io.github.pavel-tashev/rss-feed-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

Neither one's marketplaces publish the settings it asks for.

What it can do: mail-muncher · What it can do: io.github.pavel-tashev/rss-feed-reader · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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