Ext Ops Panel
Open dashboard
Comparison

bug-fixing-autoreport vs Shipbook

bug-fixing-autoreport is a plugin bundle for AI coding tools published by maxirodr. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Shipbook is an MCP server published by shipbook.io. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-28. 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
Marketplacebug-fixing-autoreportShipbook
Claude Code: claude-plugins-community Listed
Version: fd42774
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 1
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

bug-fixing-autoreport vs Shipbook
Factbug-fixing-autoreportShipbook
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.shipbook.io/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)26
Licence (differs)Not statedMIT
Repository (differs)github.com/maxirodr/bug-fixing-autoreportgithub.com/shipbook/shipbook-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 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

bug-fixing-autoreport

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

Adds structured error logging, a secure /api/errors endpoint, and a /bug-report command to any Laravel or Node/Express project. Enables Claude to fetch production errors, analyze root causes, and propose fixes.

Shipbook

In its own words, on Official MCP Registry:

Debug production issues using Shipbook logs and Loglytics error insights.

How to run each

bug-fixing-autoreport As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install bug-fixing-autoreport@claude-community

Shipbook As a remote MCP server

Claude Code
claude mcp add --transport http shipbook https://api.shipbook.io/mcp

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

Only Shipbook 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: bug-fixing-autoreport · What it can do: Shipbook · 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