checkout-flow vs io.github.codespar/mcp-ucp
checkout-flow is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
checkout-flow is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. io.github.codespar/mcp-ucp is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.codespar/mcp-ucp | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.4 Downloads/month (npm): 330 Downloads/week (npm): 14 Forks (GitHub): 52 Stars (GitHub): 274 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 | checkout-flowno longer listed · | io.github.codespar/mcp-ucp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 274 |
| Forks (GitHub) (differs) | 0 | 52 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (@codespar/mcp-ucp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/codespar/mcp-dev-latam |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of checkout-flow
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Shopify checkout upsells, post-purchase offers, discounts, bundles, validations and gift cards.
-
Payment gateway integration with Stripe, PayPal, checkout flow implementation, subscription billing, and PCI compliance
-
Payment gateway integration with Stripe, PayPal, checkout flow implementation, subscription billing, and PCI compliance
-
Build bundles and cart drawers for your Shopify store with Section Store.
-
Universal Commerce Protocol (UCP) — Google/Shopify agentic commerce across REST, MCP, A2A, and Embedded bindings
-
Mercado Pago full-product integration toolkit. Expert agent routes to 13 product skills. Hybrid architecture: skills provide integration intelligence, MCP provides live API data.
What each says it does
checkout-flow
Generate checkout flow with cart management
io.github.codespar/mcp-ucp
Google UCP — agentic shopping, cart, checkout, orders, delivery
How to run each
checkout-flow
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.codespar/mcp-ucp As a local MCP server: npm package
claude mcp add --env "UCP_API_KEY=<YOUR_UCP_API_KEY>" --transport stdio mcp-ucp -- npx -y @codespar/mcp-ucpRequires: UCP_API_KEY (secret)
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
The marketplaces of checkout-flow publish no settings it asks for, so we do not compare settings.
What it can do: checkout-flow · What it can do: io.github.codespar/mcp-ucp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.