Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.expandingweb/agentic-commerce-readiness

REMOTE · EXPANDINGWEB.COM

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

Available components

0 this week 82 Trust /100

Last scanned (5 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 711 tokens (~101/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 1 Oct 26 82
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 1 Sept 26 0

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://expandingweb.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=expandingweb.com CN=YR1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 RSA 4096 SHA256-RSA 633880655d900b1e4f95b204269614c0ec8
SANs: expandingweb.com, www.expandingweb.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of expandingweb.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
expandingweb.com. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://expandingweb.com/mcp Verified 200
http (plaintext) http://expandingweb.com/mcp HTTPS enforced 301 https://expandingweb.com/mcp
MCP tools · 7 exposed · ~560 tokens

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 →

Tool Tokens
create_checkout_session ~147

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.

NameTypeReqDescription
offer_idstring–Offer id to buy. Default: readiness-sprint.
quantityinteger–Module licences only: number of Magento installations (default 1). Ignored for the sprint.

No output schema declared.

No examples provided.

get_offer ~43

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

NameTypeReqDescription
idstringyesOffer id, e.g. readiness-sprint

No output schema declared.

No examples provided.

list_offers ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_catalog ~46

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

NameTypeReqDescription
idsarrayyesEngagement ids.

No output schema declared.

No examples provided.

report_problem ~157

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.

NameTypeReqDescription
contactstring–Optional address to reply to. Omit unless the user asked for an answer.
expectedstring–What you expected to find instead.
kindstring–Closest category; omit if unsure.
pathstring–URL or path where it happened, if there was one.
summarystringyesWhat you were trying to do and what stopped you, in your own words.

No output schema declared.

No examples provided.

scan_store ~72

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.

NameTypeReqDescription
domainstringyesStorefront domain or https URL, e.g. shop.example.com

No output schema declared.

No examples provided.

search_catalog ~68

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

NameTypeReqDescription
querystring–Free text, e.g. "sprint" or "monitoring". Omit for everything.

No output schema declared.

No examples provided.

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.

remote · expandingweb.com

# add to Claude Code
claude mcp add --transport http com-expandingweb-agentic-commerce-readiness 'https://expandingweb.com/mcp'
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 82 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.