mpp-inspector vs ZERO MCP
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). ZERO MCP is an MCP server published by zero-intel. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  mpp-inspector |  ZERO MCP |
|---|---|---|
| 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.1.5 Downloads/month (PyPI): 85 Downloads/week (PyPI): 41 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 | ZERO MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@mpp-inspector/plugin) | On your machine (zero-engine) |
| 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 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/amgb20/mpp-inspector-marketplace | github.com/zero-intel/zero |
| 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.
ZERO MCP
Read-only MCP inspection for ZERO paper autonomous onchain operations.
How to run each
mpp-inspector As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mpp-inspector@claude-communityZERO MCP As a local MCP server: PyPI package
claude mcp add --transport stdio zero -- uvx zero-engineCommands 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: ZERO MCP · 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.