Agent Commerce Readiness
REMOTE · AGENT-COMMERCE-READINESS-TLXJVCRIKA-AN.A.RUN.APP
Read-only agent-commerce audit, upgrade verification, diagnosis and x402 probing.
Available components
Last scanned (18 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 4 Nov 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 674 tokens (~134/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 −2
- Tool “prepare_agent_commerce_upgrade” rewrote its description, which is the text the model reads security
- Tool “verify_agent_commerce_upgrade” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 0.3.0 → 0.4.0 functional
- “prepare_agent_commerce_upgrade” added an optional parameter “merchantProfile” cosmetic
- “verify_agent_commerce_upgrade” added an optional parameter “expectedMerchantPack” cosmetic
- 13 Oct 26 +1
- Stability: 0.97 → pass security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 97. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 77 to 90. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 77. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 165 → 115 ▲ functional
- Server version: 0.2.0 → 0.3.0 functional
- New tool “diagnose_agent_commerce_path” functional
- New tool “prepare_agent_commerce_upgrade” functional
- New tool “probe_x402_payment_resource” functional
- New tool “verify_agent_commerce_upgrade” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 7 Oct 2026 | 30 Dec 2026 | ECDSA 256 | SHA256-RSA | 53da11951e5eb49012fb872c3cb3e54d |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-commerce-readiness-tlxjvcrika-an.a.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp | HTTPS enforced | 302 | https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_agent_commerce_readiness Audit Agent Commerce Readiness ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentResourceUrl | string | – | Optional explicit paid resource URL to probe for x402 v2. Omit unless a concrete payment-gated resource is known. |
| url | string | yes | Public HTTP(S) website or storefront to audit. |
| Name | Type | Req | Description |
|---|---|---|---|
| agentCommerce | object | yes | – |
| protocols | object | yes | – |
| remediation | object | yes | – |
| scores | object | yes | – |
No examples provided.
diagnose_agent_commerce_path Diagnose Agent Commerce Path ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | Specific agent-commerce outcome to test. |
| paymentResourceUrl | string | – | Exact paid machine resource; required for a meaningful machine_payment_readiness diagnosis. |
| url | string | yes | Public HTTP(S) website or storefront to diagnose. |
| Name | Type | Req | Description |
|---|---|---|---|
| blockers | array | yes | – |
| goal | string | yes | – |
| kind | string | yes | – |
| ready | boolean | yes | – |
| requirements | array | yes | – |
No examples provided.
prepare_agent_commerce_upgrade Prepare Agent Commerce Upgrade ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| merchantProfile | object | – | Optional {merchant:{name,type,siteUrl,description,bookingUrl,address,services},ownerConfirmedFacts:true,crawlerPolicy:"preserve"|"allow_search"|"allow_search_block_training"}. Requires confirmed merc… |
| paymentResourceUrl | string | – | Optional exact paid machine resource when x402 readiness is part of the upgrade. |
| url | string | yes | Public HTTP(S) website or storefront to prepare for agent commerce. |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | yes | – |
| implementation | object | yes | – |
| kind | string | yes | – |
No examples provided.
probe_x402_payment_resource Probe x402 Payment Resource ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| resourceUrl | string | yes | Exact public HTTP(S) paid resource to probe. |
| Name | Type | Req | Description |
|---|---|---|---|
| diagnosis | object | yes | – |
| kind | string | yes | – |
| protocols | object | yes | – |
| resourceUrl | string | yes | – |
| safety | object | yes | – |
No examples provided.
verify_agent_commerce_upgrade Verify Agent Commerce Upgrade ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedMerchantPack | object | – | Optional merchantDeployment object returned by prepare tool. Enables read-only comparison with actual deployed JSON-LD and site discovery files. |
| paymentResourceUrl | string | – | Optional exact paid machine resource to re-probe. |
| previous | object | yes | Prior ACR remediation object or compact object containing unresolvedTaskIds. |
| url | string | yes | Public HTTP(S) website or storefront after changes. |
| Name | Type | Req | Description |
|---|---|---|---|
| currentAudit | object | yes | – |
| introducedTaskIds | array | yes | – |
| kind | string | yes | – |
| resolvedTaskIds | array | yes | – |
| stillOpenTaskIds | array | yes | – |
No examples provided.
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.
remote · agent-commerce-readiness-tlxjvcrika-an.a.run.app
claude mcp add --transport http tama-fit-agent-commerce-readiness 'https://agent-commerce-readiness-tlxjvcrika-an.a.run.app/mcp'
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, upgrade verification, diagnosis and x402 probing. 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 85 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 5 tools: audit_agent_commerce_readiness, prepare_agent_commerce_upgrade, verify_agent_commerce_upgrade, probe_x402_payment_resource, diagnose_agent_commerce_path. Their descriptions and schemas cost roughly 618 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.