Agent Commerce Readiness MCP Server

by tama-fit Your server? Claim it

answering

Agent Commerce Readiness is answering right now. Last checked 14 min ago. It exposes 5 tools.

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

Uptime history 51 days of history · worst day 98%

51 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

554 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 October 2026. No other catalogue keeps this.

17 Oct 2 tool descriptions were rewritten prepare_agent_commerce_upgrade, verify_agent_commerce_upgrade

17 Oct 2 tools changed the parameters they ask for prepare_agent_commerce_upgrade, verify_agent_commerce_upgrade

17 Oct a tool changed version

2 Oct 4 tools appeared diagnose_agent_commerce_path, prepare_agent_commerce_upgrade, probe_x402_payment_resource and 1 more

2 Oct a tool changed version

Agent Commerce Readiness missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add agent-commerce-readiness --transport http https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp

~/.codex/config.toml

[mcp_servers.agent-commerce-readiness]
url = "https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit

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.

diagnose

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.

prepare

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.

probe

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.

verify

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.

Endpoints

URL	Transport	State	Latency	Checked
https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp	streamable-http	answering	621 ms	14 min ago

Alternatives to Agent Commerce Readiness

same job, measured the same way

x402 Pay — USDC API Payment Helper

by scriptmasterlabs

Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.

5 tools answering

Reality Graph Verification Tools

by realitygraph

Read-only AI coding tools for change verification, release readiness, capacity, and guidance.

10 tools answering

Scbee MCP

by hmakt99

Score repos for launch and agent readiness, find verified agents, read collaborations. Read-only.

100 installs/wk local only

Ternivo Connect

by homesteadliving

Agent-ready social delivery with preflight, verification, retries, diagnostics, and audit controls.

answering

AuthiChain

by undone0603

Look up AuthiChain product records. x402 paid verification and on-chain anchoring in development.

7 tools answering

Bounty Engineer Agent Commerce

by gatoprd

Remote MCP storefront for agent routing, verification, web extraction and x402-paid tools.

22 tools answering

Wever Labs Agent Products

by codewever

83 production tools for agent work, commerce and verification; Base USDC x402 and shared free tier.

84 tools answering

Turva MCP

by turva

Read-only MCP server for turva.dev, an agent-readiness audit and advisory service.

5 tools answering

Agent Commerce Readiness — questions

Answers built from our own checks of this server.

What can Agent Commerce Readiness do?

It exposes 5 tools, read directly from the server on our last check. Among them: audit_agent_commerce_readiness, diagnose_agent_commerce_path, prepare_agent_commerce_upgrade, probe_x402_payment_resource, verify_agent_commerce_upgrade. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Agent Commerce Readiness working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 554 ms. The bar chart above shows every period we have measured.

How do I connect Agent Commerce Readiness?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Agent Commerce Readiness need an API key?

No. Agent Commerce Readiness completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Agent Commerce Readiness?

It answers our handshake in 554 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.