Universalcartmerchantgate MCP

What universalcartmerchantgate-mcp does

The universalcartmerchantgate-mcp MCP server provides a hosted interface for Universal Cart merchant readiness workflows. It is intended for commerce teams, merchant operations teams, marketplace owners, and reviewers assessing agentic checkout behavior.

The server focuses on five operations: checking overall Universal Cart readiness, classifying checkout blockers, explaining gaps in an offer, issuing an agentic commerce receipt, and exporting a readiness log. Its outputs are structured for tool-call consumers, and its evidence model is oriented around receipts and audit-style records.

How it works

Clients connect to the remote MCP endpoint at https://universalcartmerchantgate.clauxel.com/mcp. The repository identifies the service as a Streamable HTTP MCP endpoint rather than a local process. A public server card and registry metadata are also available for discovery and setup.

Production calls use bearer-token access. After a client connects and authenticates, an agent can invoke the listed tools as part of a merchant-readiness or checkout-review workflow. The documentation describes the service boundary and public links, but does not provide the production implementation or internal processing details.

Tools and capabilities

The universalcartmerchantgate-mcp MCP server exposes these tools:

• check_universal_cart_readiness for merchant readiness checks.
• classify_checkout_blocker for categorizing a checkout blocker.
• explain_offer_gap for explaining a gap in an offer.
• issue_agentic_commerce_receipt for producing an agentic commerce receipt.
• export_readiness_log for exporting a readiness log.

The service also provides structured tool-call output, receipt-oriented evidence export, a public server card, and registry metadata. These capabilities make it suitable for workflows that need a record of readiness findings or checkout-review evidence rather than only an unstructured response.

Setup and configuration

Configure an MCP client to use the remote endpoint:

https://universalcartmerchantgate.clauxel.com/mcp

Production access requires a bearer token. The supplied documentation does not specify the token's environment-variable name, provisioning process, request headers beyond bearer authentication, or client-specific configuration examples. The public server card is available at https://universalcartmerchantgate.clauxel.com/server-card.json, and the registry name is com.clauxel.universalcartmerchantgate/universalcartmerchantgate-mcp.

The project links to a website, pricing page, checkout page, and support address for service-related information. Those links are separate from the MCP endpoint and should not be treated as additional MCP tools.

Limitations and notes

The repository is a documentation project, not the production source. It does not include credentials, payment configuration, Cloudflare configuration, customer records, private analytics, or local machine paths. The provided material also does not document input schemas, output schemas, token acquisition, retention behavior, rate limits, or supported commerce platforms beyond Universal Cart.

The universalcartmerchantgate-mcp MCP server should therefore be evaluated against the available public documentation and endpoint behavior before being used in a production workflow. Its documented scope is merchant readiness, checkout blockers, offer gaps, receipts, and readiness logs.