# com.expandingweb/agentic-commerce-readiness (remote · expandingweb.com)

Score a Magento or Adobe Commerce store on eight AI agent-readiness checks.

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

## Components

- remote · `expandingweb.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-expandingweb-agentic-commerce-readiness/expandingweb.md), [page](https://verifymcp.io/servers/com-expandingweb-agentic-commerce-readiness/expandingweb)

## Channel facts

- Endpoint: `https://expandingweb.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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 711 tokens (~101/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.expandingweb/agentic-commerce-readiness MCP server?

com.expandingweb/agentic-commerce-readiness is a hosted endpoint at https://expandingweb.com/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 com-expandingweb-agentic-commerce-readiness 'https://expandingweb.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-expandingweb-agentic-commerce-readiness": {
      "url": "https://expandingweb.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-expandingweb-agentic-commerce-readiness": {
      "type": "http",
      "url": "https://expandingweb.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-expandingweb-agentic-commerce-readiness]
url = "https://expandingweb.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-expandingweb-agentic-commerce-readiness": {
      "type": "remote",
      "url": "https://expandingweb.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-expandingweb-agentic-commerce-readiness --url 'https://expandingweb.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-expandingweb-agentic-commerce-readiness:
    url: "https://expandingweb.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-expandingweb-agentic-commerce-readiness": {
      "Transport": "http",
      "Url": "https://expandingweb.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-expandingweb-agentic-commerce-readiness -t streamable-http -u 'https://expandingweb.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-expandingweb-agentic-commerce-readiness": {
      "type": "http",
      "url": "https://expandingweb.com/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-18 (score 76, +1)

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

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

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

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

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

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

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

### 2026-09-10 (score 72, +1)

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

### 2026-09-08 (score 71, +1)

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

### 2026-09-06 (score 70, +1)

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

### 2026-09-03 (score 69, +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.

## MCP tools (7)

### `search_catalog` (~68 tokens)

UCP 2026-04-08 catalog search over the engagement tiers. Returns UCP product objects in structuredContent. Call with no query for the whole catalog.

Input parameters:

- `query` (string): Free text, e.g. "sprint" or "monitoring". Omit for everything.

### `lookup_catalog` (~46 tokens)

UCP 2026-04-08 catalog lookup: resolve engagement ids (e.g. readiness-sprint) to UCP product objects.

Input parameters:

- `ids` (array, required): Engagement ids.

### `list_offers` (~27 tokens)

List every Expanding Web engagement tier with id, price, currency and what it includes.

### `get_offer` (~43 tokens)

Full record for one engagement tier: price, turnaround, deliverables, pricing policy and limits.

Input parameters:

- `id` (string, required): Offer id, e.g. readiness-sprint

### `scan_store` (~72 tokens)

Run the free eight-check agent-readiness scan against a live storefront and return the verdicts. Read-only, at most three pages, 15-second budget, robots.txt honoured. Limited to 5 scans per hour.

Input parameters:

- `domain` (string, required): Storefront domain or https URL, e.g. shop.example.com

### `create_checkout_session` (~147 tokens)

Create a Stripe Checkout Session and return its URL — for the Agentic Commerce Readiness Sprint (readiness-sprint) or for Pro licences of the Agentic Commerce Suite Magento module (module-pro, one licence per Magento installation, volume discount from 3). Payment is completed by the buyer at that URL; this tool never charges a card and takes no payment credentials. For the module, the licence key is minted on payment and shown on the success page and by email.

Input parameters:

- `offer_id` (string): Offer id to buy. Default: readiness-sprint.
- `quantity` (integer): Module licences only: number of Magento installations (default 1). Ignored for the sprint.

### `report_problem` (~157 tokens)

Report something on this site or endpoint that stopped you from completing a task: a page you could not read, data you could not find, a request that was refused. Read by a human. Use this instead of giving up silently — it is the only way we learn that an agent failed here.

Input parameters:

- `contact` (string): Optional address to reply to. Omit unless the user asked for an answer.
- `expected` (string): What you expected to find instead.
- `kind` (string): Closest category; omit if unsure.
- `path` (string): URL or path where it happened, if there was one.
- `summary` (string, required): What you were trying to do and what stopped you, in your own words.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-expandingweb-agentic-commerce-readiness/expandingweb#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 69
- 2026-09-04: 69
- 2026-09-03: 69
- 2026-09-02: 68
- 2026-09-01: 68

## Common questions

### What is the com.expandingweb/agentic-commerce-readiness MCP server?

com.expandingweb/agentic-commerce-readiness is an MCP server listed in the public MCP registry as com.expandingweb/agentic-commerce-readiness. Score a Magento or Adobe Commerce store on eight AI agent-readiness checks. This page covers its hosted endpoint (https://expandingweb.com/mcp).

### Is the com.expandingweb/agentic-commerce-readiness MCP server safe to use?

com.expandingweb/agentic-commerce-readiness scores 76 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 com.expandingweb/agentic-commerce-readiness MCP server expose?

com.expandingweb/agentic-commerce-readiness exposes 7 tools: search_catalog, lookup_catalog, list_offers, get_offer, scan_store, and 2 more. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

### Does the com.expandingweb/agentic-commerce-readiness MCP server require authentication?

No. We connected to com.expandingweb/agentic-commerce-readiness without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.expandingweb/agentic-commerce-readiness MCP server still maintained?

com.expandingweb/agentic-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://expandingweb.com/mcp
- Repository: https://github.com/Expanding-Web/magento-agent-readiness
- Website: https://expandingweb.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-expandingweb-agentic-commerce-readiness/expandingweb.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-expandingweb-agentic-commerce-readiness/expandingweb.json
- HTML version of this page: https://verifymcp.io/servers/com-expandingweb-agentic-commerce-readiness/expandingweb