F
licenseNot graded
qualityA
maintenanceEnables agents to vet merchants, create and verify USDC charges and invoices, assess trust and tokenized-asset authenticity, and manage provable books on Base, all non-custodially.
49 npm
-
four02-commerce-mcp
Officialby 402Protocol
Related Servers
Alternatives to four02-commerce-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceOnchain agent-to-agent commerce protocol using x402 and ERC-8004. Enables AI agents to buy/sell services, manage vendor catalogs, and process payments on Base.MIT
- AlicenseAqualityCmaintenanceEnables MCP agents to create Ink wallets, register ERC-8004 identities, send daily GM messages on gm.ink, and check GM status with dry-run safety and gas gating.612 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to sell MCP tools and Hermes capabilities behind an x402 v2 / USDC payment gate, and to buy other agents' capabilities through a wallet tool. Sellers quote a price, verify the exact transfer and nonce, then execute, while buyers get recipient allowlists, per-call limits, and a persistent cumulative budget.1MIT
- AlicenseNot gradedqualityDmaintenanceAgent network intelligence for trust verification, broker discovery, and capability matching. Ed25519 identity, graph-based trust scoring, USDC payments, and MCP tools for agent registration, search, and trust attestation.812 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to autonomously invoice, receive payments, and settle micro-transactions in USDC via Moove Agentic Payments, using cryptographic hash commitments for zero-custody fair exchange.MIT
TDQS
A4/5.0
Scored across 6 tools
Disambiguation4/5
Invoice tools (create/status/pay) are clearly distinct by lifecycle stage. Reputation tools have slight overlap because reputation_summary already includes reliability and dispute rate, which are also the focus of reputation_reliability; however, the descriptions clarify that summary is broader and reliability is narrowly scored, so confusion is limited.
Naming Consistency5/5
All tools follow the same four02_<resource>_<action> snake_case pattern: invoice_create, invoice_status, invoice_pay, reputation_summary, reputation_reliability, reputation_history. The convention is predictable and consistent throughout.
Tool Count5/5
Six tools are well-scoped for a focused commerce server covering invoice creation, verification, payment planning, and reputation reads. Each tool has a clear role without an excessive or thin surface.
Completeness4/5
The invoice lifecycle is covered from creation through status verification to payment, and reputation read operations are present. Minor gaps exist around listing/searching invoices or writing reputation/dispute events, but the core stated workflows are supported.
Maintenance
ActivityMaintained
ResponsivenessNo issues