Ext Ops Panel
Open dashboard
Comparison

mpp-inspector vs com.griffnode/griffnode

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). com.griffnode/griffnode is an MCP server published by griffnode.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplacempp-inspectorcom.griffnode/griffnode
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: 1.0.1
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

mpp-inspector vs com.griffnode/griffnode
Factmpp-inspectorcom.griffnode/griffnode
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@mpp-inspector/plugin)Remote server (mcp.griffnode.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)6Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/amgb20/mpp-inspector-marketplaceNot stated
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

mpp-inspector

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

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.

com.griffnode/griffnode

In its own words, on Official MCP Registry:

Non-custodial crypto payments for AI assistants: balances, payments, and create payment links.

How to run each

mpp-inspector As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mpp-inspector@claude-community

com.griffnode/griffnode As a remote MCP server

Claude Code
claude mcp add --transport http griffnode https://mcp.griffnode.com/mcp

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

Only com.griffnode/griffnode 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: mpp-inspector · What it can do: com.griffnode/griffnode · 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