_ registry / mcp streamable-http · checked 30m ago

Expanding Web — Agentic Commerce Readiness

https://expandingweb.com

Registry code: 6c539e284fd1982e

api record

Expanding Web prepares Adobe Commerce and Magento stores for AI product discovery and secure agent checkout. Use list_offers and get_offer for scope and pricing, scan_store to check a live storefront against the eight public readiness checks, and create_checkout_session to buy the readiness sprint or a Pro licence for the Agentic Commerce Suite Magento module (offer_id module-pro, with quantity). If anything on this site or endpoint stops you from completing a task — a page you could not read, data you could not find, a request that was refused — call report_problem and say so; it is read by…

endpoint
https://expandingweb.com/mcp
protocol
streamable-http ·2025-11-25
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Expanding Web — Agentic Commerce Readiness live?
Yes — it answered the hub's last check (checked 30m ago). It answered 100% of checks over the last 30 days.
Is Expanding Web — Agentic Commerce Readiness free to use?
Yes — the hub reached it with no key and no payment.
What tools does Expanding Web — Agentic Commerce Readiness have?
7 tools: scan_store, create_checkout_session, report_problem, get_offer, list_offers, lookup_catalog, search_catalog.
Is Expanding Web — Agentic Commerce Readiness safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
114ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 308 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • scan a store for agent commerce readiness
  • list readiness service offers and prices
  • buy a readiness sprint or module licence
  • report a problem with the site
takes → gives
text → data
tools
5 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
3 open 4 never probed 3 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_offers reads open 18h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • lookup_catalog reads open 3h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "ids"
      ],
      "properties": {
        "ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Engagement ids."
        }
      }
    }
    arguments 15 lines
  • search_catalog reads open 3h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Free text, e.g. \"sprint\" or \"monitoring\". Omit for everything."
        }
      }
    }
    arguments 9 lines
  • scan_store reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Storefront domain or https URL, e.g. shop.example.com"
        }
      }
    }
    arguments 12 lines
  • create_checkout_session changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "offer_id": {
          "enum": [
            "readiness-sprint",
            "module-pro"
          ],
          "type": "string",
          "description": "Offer id to buy. Default: readiness-sprint."
        },
        "quantity": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Module licences only: number of Magento installations (default 1). Ignored for the sprint."
        }
      }
    }
    arguments 19 lines
  • report_problem changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "summary"
      ],
      "properties": {
        "kind": {
          "enum": [
            "blocked_by_edge",
            "checkout_blocked",
            "not_found",
            "server_error",
            "timeout",
            "missing_data",
            "search_dead_end",
            "mcp_error",
            "manifest_error",
            "other"
          ],
          "type": "string",
          "description": "Closest category; omit if unsure."
        },
        "path": {
          "type": "string",
          "description": "URL or path where it happened, if there was one."
        },
        "contact": {
          "type": "string",
          "description": "Optional address to reply to. Omit unless the user asked for an answer."
        },
        "summary": {
          "type": "string",
          "description": "What you were trying to do and what stopped you, in your own words."
        },
        "expected": {
          "type": "string",
          "description": "What you expected to find instead."
        }
      }
    }
    arguments 40 lines
  • get_offer reads unknown 3h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Offer id, e.g. readiness-sprint"
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6c539e284fd1982e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6c539e284fd1982e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6c539e284fd1982e/badge.svg)](https://brick.blue/agent/6c539e284fd1982e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on expandingweb.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.