ap2-agentic-payments vs MUJ428 Trust Layer — Bind Approved Intent to Verified Effect
ap2-agentic-payments is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑11.
ap2-agentic-payments is a plugin bundle for AI coding tools published by Rohit Bajaj, Julekha Khatun. No marketplace we read lists it any more. MUJ428 Trust Layer — Bind Approved Intent to Verified Effect is an MCP server published by wmujahid428-web. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  MUJ428 Trust Layer — Bind Approved Intent to Verified Effect | |
|---|---|---|
| Community marketplace orcaqubits/agentic-commerce-claude-plugins | Removed on 2026-11-11 Version: 1.0.0 Forks (GitHub): 17 Stars (GitHub): 40 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.6.4 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
| Fact | ap2-agentic-paymentsno longer listed · | MUJ428 Trust Layer — Bind Approved Intent to Verified Effect |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 40 | No figure on GitHub |
| Forks (GitHub) (differs) | 17 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (agents.muj428.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| 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) | 21 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/orcaqubits/agentic-commerce-claude-plugins | github.com/wmujahid428-web/muj428-a2a-revenue-engine |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 19 h ago |
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 ap2-agentic-payments
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.
-
agent-commerce-protocol-mcp io.github.CSOAI-ORG/agent-commerce-protocol-mcp
Agent Commerce Protocol MCP — bridges Stripe ACP + Google AP2 + Coinbase x402 for agent payments
-
agentpay io.github.kar69-96/agentpay
AI agent payments with human approval. Local-first, encrypted credentials, budget controls.
-
Boundra — Payment Approval Gateway for AI Agents
Policy decision point for agent payments — allow, ask, or veto before signing
-
vantic ai.vanticlabs/vantic
Verify an AI agent's payment authority: signed mandates, allowlists, and tamper-proof receipts.
-
payclaw io.github.payclaw/payclaw
Virtual Visa cards for AI agents. JIT card issuance, human-approved, MCP-native.
What each says it does
ap2-agentic-payments
AP2 (Agent Payments Protocol) — Google agentic payment mandates, VDCs, and cryptographic signing
MUJ428 Trust Layer — Bind Approved Intent to Verified Effect
Payment-rail-independent intent-to-effect integrity for consequential agent actions.
How to run each
ap2-agentic-payments
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
MUJ428 Trust Layer — Bind Approved Intent to Verified Effect As a remote MCP server
claude mcp add --transport http muj428-trust-layer https://agents.muj428.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only MUJ428 Trust Layer — Bind Approved Intent to Verified Effect 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: ap2-agentic-payments · What it can do: MUJ428 Trust Layer — Bind Approved Intent to Verified Effect · 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.