Ext Ops Panel
Open dashboard
Comparison

BugEzy vs BugCatcher

BugEzy is an MCP server published by bugezy.dev. Marketplaces we read that list it: 1 (Official MCP Registry). BugCatcher is an MCP server published by fDiosc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
MarketplaceBugEzyBugCatcher
Official MCP Registry Listed
Version: 1.1.3
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
Downloads/month (npm): 93
Downloads/week (npm): 27
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

BugEzy vs BugCatcher
FactBugEzyBugCatcher
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (bugezy.dev/mcp)On your machine (bugcatcher-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/fox100039-design/bugezygithub.com/fdiosc/bugcatcher
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 32 h ago returned HTTP 406no 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

BugEzy

In its own words, on Official MCP Registry:

Voice-powered bug reporting with 13 MCP tools. Record bugs by talking; let AI find and fix them.

BugCatcher

In its own words, on Official MCP Registry:

Bug reports, AI diagnosis, and status management for Cursor, Claude, Windsurf.

How to run each

BugEzy As a remote MCP server

Claude Code
claude mcp add --transport http bugezy https://bugezy.dev/mcp

BugCatcher As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio bugcatcher-mcp -- npx -y bugcatcher-mcp

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

Only BugEzy 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: BugEzy · What it can do: BugCatcher · 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.

Where the data comes from: how the catalog is built