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

storefront-readiness-grader

https://grader-al6bxcngia-ue.a.run.app

Registry code: de445604bc3946d4

api record

Audit an ecommerce storefront for AI-agent shopping readiness. Fetches the store server-side and runs 20 weighted checks, returning an A–F grade with prioritized fixes. Pay-per-call: $1.00 USDC per call via x402 on Base mainnet. No subscription, no account.

from a public catalogue that lists it, not from the operator

endpoint
https://grader-al6bxcngia-ue.a.run.app/mcp
protocol
streamable-http ·2025-06-18
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 storefront-readiness-grader live?
Yes — it answered the hub's last check (checked 25m ago). It answered 98% of checks over the last 30 days.
Is storefront-readiness-grader free to use?
No — it charges per call, from 1 USDC, quoted in its own 402 answers.
What tools does storefront-readiness-grader have?
1 tool: grade_storefront.
Is storefront-readiness-grader 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
98.3%

90 days 99%· all time 99%

latency
560ms

last good check

priced tools
1

of 1 tools

_ answered our checks, 90 days 299 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • grade a storefront for ai shopping readiness
  • get prioritized fixes for an online store
takes → gives
web pages, text → data
tools
1 reads
_ 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 1 tools
1 paid 1 of 1 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.

  • grade_storefront reads 1 USDC paid 26m ago

    Audit an ecommerce storefront for AI-agent shopping readiness. Fetches the store server-side and runs 20 weighted checks across product intelligence (schema.org Product/Offer price, availability, variants, GTIN/MPN), AI discovery (robots.txt, llms.txt, agents.md, sitemap.xml, UCP manifest, MCP endpoint), conversation readiness (contact info, FAQ/returns, site search), transaction readiness (HTTPS, checkout signals, tax/shipping as values), and trust (business identity, policies). Returns a machine-readable JSON report: 0-100 score, A-F grade, per-check pass/partial/fail/unknown with evidence, and the top 3 prioritized fixes. Cost: $1.00 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this to decide whether a store is ready for AI shopping agents, or to generate the audit behind a readiness report for a merchant.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Storefront URL to grade, e.g. https://example-store.com"
    }
  }
}
    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 de445604bc3946d4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/de445604bc3946d4/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/de445604bc3946d4/badge.svg)](https://brick.blue/agent/de445604bc3946d4?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
50%

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.