mpp-inspector vs BLEA
mpp-inspector is a plugin bundle for AI coding tools published by amgb20. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). BLEA is an MCP server published by Nitmi. Marketplaces we read that list it: 2 (Official MCP Registry, Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-25. 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
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.0 Downloads/month (PyPI): 423 Downloads/week (PyPI): 55 Forks (GitHub): 0 Stars (GitHub): 12 Not marked · First seen |
| Copilot CLI: github/awesome-copilot | Not listed | Listed Version: 0.6.1 Forks (GitHub): 0 Stars (GitHub): 12 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
| Fact | mpp-inspector | BLEA |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 12 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@mpp-inspector/plugin) | On your machine (blea) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 6 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/amgb20/mpp-inspector-marketplace | github.com/nitmi/blea |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
mpp-inspector
Inspect, debug, and test Machine Payments Protocol (HTTP 402) endpoints directly from Claude Code. Parses spec-compliant WWW-Authenticate challenges, discovers MPP endpoints on any domain, compares pricing across services, validates receipts, and dry-runs payment flows. Supports Tempo, Stripe, Lightning, Solana, and Card payment methods. Includes 4 slash commands (/mpp-inspect, /mpp-scan, /mpp-flow, /mpp-protocol) and 5 MCP tools for programmatic access.
BLEA
Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents.
How to run each
mpp-inspector As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mpp-inspector@claude-community
BLEA As a local MCP server: PyPI package
claude mcp add --transport stdio blea -- uvx blea 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: mpp-inspector · What it can do: BLEA · 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. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.