# Agent Commerce Readiness

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

- name: io.github.TAMA-FIT/agent-commerce-readiness
- version: 0.4.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 84/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.TAMA-FIT%2Fagent-commerce-readiness
- tools: https://api.protogrid.dev/v1/servers/io.github.TAMA-FIT%2Fagent-commerce-readiness/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 45
- drivers: +website +reachable +uptime-100% +updated-2d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 84/100 (good)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 3600000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,096 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 6 tool changes in 30 days
- fail `stability.rug_pull`: 2 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 1,096 tokens to load them all
- tool set hash: 9abab71cf3dcb1aa4bdb3e70391f7939
- tools last changed: 2026-10-17T06:32:56.054Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.TAMA-FIT/agent-commerce-readiness.svg)](https://protogrid.dev/servers/io.github.TAMA-FIT/agent-commerce-readiness)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-17 `verify_agent_commerce_upgrade` changed (description, inputSchema) **meaning changed**
  - before: Re-audit a storefront after changes and compare it with a prior ACR remediation receipt. Returns resolved, still-open, and newly introduced blockers plus a fresh verification receipt. Use in audit-fix-rerun coding loops.
  - after: 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.
- 2026-10-17 `prepare_agent_commerce_upgrade` changed (description, inputSchema) **meaning changed**
  - before: Turn a public storefront URL into an implementation-ready agent-commerce upgrade plan: fresh audit evidence, ordered remediation tasks, deterministic acceptance assertions, artifact targets, and a verification handoff. Use when a coding agent needs to fix the site rather than merely score it.
  - after: 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.
- 2026-10-02 `diagnose_agent_commerce_path` added
  - 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.
- 2026-10-02 `probe_x402_payment_resource` added
  - 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.
- 2026-10-02 `verify_agent_commerce_upgrade` added
  - Re-audit a storefront after changes and compare it with a prior ACR remediation receipt. Returns resolved, still-open, and newly introduced blockers plus a fresh verification receipt. Use in audit-fix-rerun coding loops.
- 2026-10-02 `prepare_agent_commerce_upgrade` added
  - Turn a public storefront URL into an implementation-ready agent-commerce upgrade plan: fresh audit evidence, ordered remediation tasks, deterministic acceptance assertions, artifact targets, and a verification handoff. Use when a coding agent needs to fix the site rather than merely score it.

Full history: https://api.protogrid.dev/v1/servers/io.github.TAMA-FIT%2Fagent-commerce-readiness/changes

## Remotes

- https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (5)

- `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_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_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_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_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.