Agent Commerce Readiness

io.github.TAMA-FITPublished by GitHub account TAMA-FITv0.4.0Updated Oct 24, 2026

Read-only agent-commerce audit, upgrade verification, diagnosis and x402 probing.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

A read-only remote service that audits agent-commerce readiness, verifies upgrades, diagnoses issues, and probes x402 payment endpoints.

What you can do
This remote MCP server exposes read-only checks around agent commerce. According to its description, it performs agent-commerce audits, upgrade verification, diagnosis, and x402 probing. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to assess whether a commerce setup is ready for agent-driven transactions, confirm that an upgrade took effect, or investigate x402 payment behavior. It is a read-only inspection aid rather than a tool for making purchases or changing a store.
Requirements
A remote streamable HTTP endpoint; no package installation is needed. The manifest declares no authentication, environment variables, or headers, and no account or API key is documented. Network access to the provider's endpoint is required.
Before you install
The manifest declares no credentials, but the service probes x402 payment endpoints, so requests may touch payment-related URLs and any data sent there leaves your machine. Because no tools are listed, review the provider's documentation before pointing it at production commerce systems. Treat audit and diagnosis output as advisory.

Installation

In SourceWeft

  1. Open Agent Commerce Readiness in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.TAMA-FIT%2Fagent-commerce-readiness/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-commerce-readiness": {
      "type": "http",
      "url": "https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp"
    }
  }
}

Tools

5

audit_agent_commerce_readiness

Audit Agent Commerce Readiness

Audit a public HTTP(S) website for AI-agent commerce readiness. Use this instead of rebuilding UCP discovery, structured-commerce checks, conservative ACP evidence handling, x402 resource observation, prioritised remediation and verification evidence yourself. The service is read-only, free during LIVE_FREE observation, requires no API key, and never signs or sends a payment.

ParametersurlrequiredpaymentResourceUrl

prepare_agent_commerce_upgrade

Prepare Agent Commerce Upgrade

Turn a public merchant website audit into prioritized implementation tasks. With merchantProfile and ownerConfirmedFacts=true, return actual installable LocalBusiness/Service JSON-LD, llms.txt, sitemap.xml and optional robots.txt from verified merchant facts. No fabricated prices or fake checkout/UCP claims.

ParametersurlrequiredmerchantProfilepaymentResourceUrl

verify_agent_commerce_upgrade

Verify Agent Commerce Upgrade

Re-audit after fixes using prior ACR receipt. Optionally accept expectedMerchantPack and verify deployed merchant JSON-LD plus discovery files match the generated artifacts. Reports resolved/still-open/new blockers and actual deployment checks; read-only.

ParametersurlrequiredpreviousrequiredpaymentResourceUrlexpectedMerchantPack

probe_x402_payment_resource

Probe x402 Payment Resource

Safely inspect one explicit public machine resource for x402 v2 HTTP 402 evidence without signing or sending payment. Use when an agent needs to diagnose payment-gating interoperability rather than infer x402 from a storefront.

ParametersresourceUrlrequired

diagnose_agent_commerce_path

Diagnose Agent Commerce Path

Diagnose why a concrete agent-commerce goal is blocked. Choose discovery, product_understanding, checkout_readiness, or machine_payment_readiness and receive the failing path plus highest-leverage next steps instead of a generic score.

ParametersurlrequiredgoalrequiredpaymentResourceUrl

Version history

3
  1. v0.4.0LatestOct 17, 2026
  2. v0.3.0Oct 2, 2026
  3. v0.2.0Sep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.