# Agent Commerce Readiness (remote · agent-commerce-readiness-tlxjvcrika-an.a.run.app)

Read-only agent-commerce audit for UCP, x402, remediation and verification evidence.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `agent-commerce-readiness-tlxjvcrika-an.a.run.app`: 75/100 (this document), [markdown](https://verifymcp.io/servers/tama-fit-agent-commerce-readiness/agent-commerce-readiness-tlxjvcrika-an.md), [page](https://verifymcp.io/servers/tama-fit-agent-commerce-readiness/agent-commerce-readiness-tlxjvcrika-an)

## Channel facts

- Endpoint: `https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 165 tokens (~165/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Agent Commerce Readiness MCP server?

Agent Commerce Readiness is a hosted endpoint at https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http tama-fit-agent-commerce-readiness 'https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tama-fit-agent-commerce-readiness": {
      "type": "remote",
      "url": "https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tama-fit-agent-commerce-readiness --url 'https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tama-fit-agent-commerce-readiness:
    url: "https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tama-fit-agent-commerce-readiness": {
      "Transport": "http",
      "Url": "https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tama-fit-agent-commerce-readiness -t streamable-http -u 'https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-13 (score 72)

First indexed and scored.

## MCP tools (1)

### `audit_agent_commerce_readiness` (~130 tokens)

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.

Input parameters:

- `paymentResourceUrl` (string): Optional explicit paid resource URL to probe for x402 v2. Omit unless a concrete payment-gated resource is known.
- `url` (string, required): Public HTTP(S) website or storefront to audit.

Output parameters:

- `agentCommerce` (object)
- `protocols` (object)
- `remediation` (object)
- `scores` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tama-fit-agent-commerce-readiness/agent-commerce-readiness-tlxjvcrika-an#diagnostics

## Score history

- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 72

## Common questions

### What is the Agent Commerce Readiness MCP server?

Agent Commerce Readiness is an MCP server listed in the public MCP registry as io.github.TAMA-FIT/agent-commerce-readiness. Read-only agent-commerce audit for UCP, x402, remediation and verification evidence. This page covers its hosted endpoint (https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp).

### Is the Agent Commerce Readiness MCP server safe to use?

Agent Commerce Readiness scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Agent Commerce Readiness MCP server expose?

Agent Commerce Readiness exposes 1 tool: audit_agent_commerce_readiness. Their descriptions and schemas cost roughly 130 tokens of context every time the server is loaded.

### Does the Agent Commerce Readiness MCP server require authentication?

No. We connected to Agent Commerce Readiness without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agent Commerce Readiness MCP server still maintained?

Agent Commerce Readiness is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp
- Website: https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/docs
- Changelog RSS feed: https://verifymcp.io/servers/tama-fit-agent-commerce-readiness/agent-commerce-readiness-tlxjvcrika-an.xml
- Changelog JSON feed: https://verifymcp.io/servers/tama-fit-agent-commerce-readiness/agent-commerce-readiness-tlxjvcrika-an.json
- HTML version of this page: https://verifymcp.io/servers/tama-fit-agent-commerce-readiness/agent-commerce-readiness-tlxjvcrika-an