ARC: agent checkout reachability
REMOTE · WWW.ARCREPORT.AI
Free, no sign-in MCP: can AI agents reach checkout at a store? Try: Use ARC to check allbirds.com
Available components
Last scanned (5 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 18 Oct 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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3057 tokens (~160/item across 19 items; 19 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 0
- Tool “can_agent_checkout” rewrote its description, which is the text the model reads security
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “can_agent_checkout” rewrote its description, which is the text the model reads security
- Tool “check_agent_readiness” rewrote its description, which is the text the model reads security
- Tool “get_readiness_result” rewrote its description, which is the text the model reads security
- Tool “list_monitors” rewrote its description, which is the text the model reads security
- 15 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “can_agent_checkout” rewrote its description, which is the text the model reads security
- Tool “check_store” rewrote its description, which is the text the model reads security
- Tool “find_stores” rewrote its description, which is the text the model reads security
- 14 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “report_checkout” rewrote its description, which is the text the model reads security
- 13 Oct 26 −1
- Authorization: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_agents_about_brand” rewrote its description, which is the text the model reads security
- Tool “bulk_create_monitors” rewrote its description, which is the text the model reads security
- Tool “can_agent_checkout” rewrote its description, which is the text the model reads security
- Tool “check_agent_readiness” rewrote its description, which is the text the model reads security
- Tool “check_store” rewrote its description, which is the text the model reads security
- Tool “find_stores” rewrote its description, which is the text the model reads security
- Tool “get_fixes” rewrote its description, which is the text the model reads security
- Tool “get_readiness_result” rewrote its description, which is the text the model reads security
- Tool “get_store_hub” rewrote its description, which is the text the model reads security
- Tool “google_checkout_readiness” rewrote its description, which is the text the model reads security
- Tool “list_monitors” rewrote its description, which is the text the model reads security
- Tool “list_readiness_checks” rewrote its description, which is the text the model reads security
- Tool “monitor_summary” rewrote its description, which is the text the model reads security
- Tool “pause_monitor” rewrote its description, which is the text the model reads security
- Tool “resume_monitor” rewrote its description, which is the text the model reads security
- Tool “run_monitor_now” rewrote its description, which is the text the model reads security
- Tool “update_monitor” rewrote its description, which is the text the model reads security
- Schema quality: 139 → 155 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- New tool “report_checkout” functional
- 12 Oct 26 77
First indexed and scored.
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 18 Oct 2026 · Probed https://www.arcreport.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.arcreport.ai | CN=YR2,O=Let's Encrypt,C=US | 31 Aug 2026 | 29 Nov 2026 | RSA 2048 | SHA256-RSA | 5189ac14bfa47b2499632875b7b7c670b4d |
| SANs: www.arcreport.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 www.arcreport.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| arcreport.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://arcreport.ai/.well-known/oauth-protected-resource", error="invalid_token", error_description="Sign in to ARC"
Bearer resource_metadata="https://arcreport.ai/.well-known/oauth-protected-resource", error="invalid_token", error_description="Sign in to ARC"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Protected resource metadata
| Document | https://arcreport.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | No |
| Problem | metadata_http_error |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.arcreport.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.arcreport.ai/api/mcp | HTTPS enforced | 308 | https://www.arcreport.ai/api/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 →
ask_agents_about_brand ~283
[Requires sign-in] Ask benchmark personal-agent personas what they think of a brand and whether they would recommend it for a category. Personas: Muse-style, Instinct-style, Grok Bot-style, OpenAI dots-style, and OpenClaw-style. This tool uses benchmark personas, including the Grok Bot-style persona; these are not live consumer-product sessions. It is not the real Grok read-back on a scan and it is not the agent-rails HTTP check. What Grok tells shoppers on a scan is a real model call via API, checked against the store's pages, not the consumer Grok app. All five cart attempts, Grok included, are ARC browser cart tests. Returns, per persona: mentioned, recommended, which competitors were recommended instead, sentiment, and short quotes, plus next steps. Limited to 8 runs per workspace per day and 12 per network. Free workspaces also share a site-wide daily cap so unpaid runs cannot drain the model budget.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name, e.g. Allbirds. |
| category | string | yes | Product category a shopper would ask about, e.g. running shoes. |
| competitors | array | – | Optional competitor brand names to watch for in the answers. |
| store_url | string | yes | Public store URL, e.g. https://www.allbirds.com |
No output schema declared.
No examples provided.
bulk_create_monitors ~263
[Requires sign-in] Set up scheduled monitoring for one or more store URLs (the 'set up monitoring' flow). Validates each URL and rejects invalid/private/internal ones. GUIDED FLOW: first ask the user for the URLs (paste a list or a CSV), then the frequency (daily/weekly/monthly, default weekly). Every plan runs the core panel of personal shopping agents — no picking needed. Call once without confirmed=true to preview the exact setup and scan-credit estimate, read that summary to the user, and only after the user explicitly says yes call again with confirmed=true to create the monitors. Each scheduled run uses one scan credit. Every run emails who reached the cart, who stopped or started, the stuck step, and the fix. Weekly is what the plans include; daily only fits when the plan's scan allowance covers it.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | Must be true only after the user has confirmed the summarized setup. If missing or false, ARC returns a preview and creates nothing. |
| depth | string | – | How far each scan goes. Default: cart. |
| frequency | string | – | How often to re-test. Default: weekly. |
| urls | array | yes | Store/product URLs to monitor (a list or pasted CSV lines). |
No output schema declared.
No examples provided.
can_agent_checkout ~130
[Requires sign-in] Call when you need a saved checkout-link check for any public store URL, not only Index brands. Saved HTTP checkout check for a public homepage or product URL: catalog, product, checkout link, UCP profile, blocks, and one fix. No model call, payment, or browser scan. Uses ARC's last check (cached up to 24 hours). A missing result is unknown, not a no. A checkout link means reach checkout, not a completed order. Results are advisory. ARC stops before payment.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public store homepage or product URL |
No output schema declared.
No examples provided.
check_agent_readiness ~157
[Requires sign-in] Check whether personal AI agents can reach a product URL, understand it, and reach checkout. Runs ARC's readiness check: crawler access, whether an agent can answer a shopper's questions from the page, and personal shopping agents trying to add to cart or reach checkout. Returns a check id — poll get_readiness_result (about 30–60 seconds). This does not ask what agents think of the brand; use ask_agents_about_brand for that.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | – | Optional goal, e.g. 'add to cart' (default) or 'reach checkout'. |
| url | string | yes | The product or store URL to test, e.g. https://store.com/products/best-seller |
No output schema declared.
No examples provided.
check_store ~106
Check if an AI agent can reach checkout on a store before trying. Call this with a store domain, such as allbirds.com. Returns the saved checkout evidence, or not checked yet when ARC has no saved check. Free, no login, no new scan, and no fetch of the store. A missing field says "not recorded" and is not a zero. Results are advisory. ARC stops before payment.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Store domain, such as allbirds.com. |
No output schema declared.
No examples provided.
find_stores ~165
Find stores where a saved check shows an AI agent can reach checkout. Filter by platform, protocol, or category. With no filters, returns the most recently checked of those stores and labels the result default: no filters given. A missing result is not counted against a store. No login and no new scan. Results are advisory. ARC stops before payment.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category or shopper words, such as footwear or running shoes. |
| limit | integer | – | How many stores to return. Default 10. Maximum 25. |
| platform | string | – | Commerce platform id, such as shopify or woocommerce. |
| protocol | string | – | ucp, webmcp, or mcp. ACP, PAP, and payments are not recorded per store. |
No output schema declared.
No examples provided.
get_fixes ~177
[Requires sign-in] Concrete next steps to get recommended by personal agents and to become reachable, understandable, and buyable. Pass a readiness check id and/or the brand, category, store URL, and competitors that were recommended instead. Uses the check's evidence when an id is given. Does not start a new check.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Brand name, if you want recommendation steps. |
| category | string | – | Product category, e.g. running shoes. |
| competitors_recommended | array | – | Competitors personal agents recommended instead. |
| mentioned | boolean | – | Whether any benchmark persona mentioned the brand. |
| recommended | boolean | – | Whether any benchmark persona recommended the brand for the category. |
| scan_id | string | – | Optional readiness check id from check_agent_readiness. |
| store_url | string | – | Store URL. |
No output schema declared.
No examples provided.
get_readiness_result ~116
[Requires sign-in] Get a readiness check by id. While running, reports progress. When complete, reports whether personal agents could reach the page, understand it, and reach checkout, plus the wall, concrete next steps, a directional score, a per-agent breakdown, and screenshots. Calling this again with the same id redisplays the result and does not start a new check. Never re-run check_agent_readiness just to see the screenshots again.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The check id returned by check_agent_readiness. |
No output schema declared.
No examples provided.
get_store_hub ~55
[Requires sign-in] Look up a free ARC store card by host. Includes saved measurements and brand_claim ownership metadata. Brand statements are not measured by ARC; claims never change measured scores.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
No output schema declared.
No examples provided.
google_checkout_readiness ~64
[Requires sign-in] Read saved public Google agentic checkout readiness checks for a store. Free; no new scan or paid calls. Merchant Center feed eligibility cannot be checked from outside. Not Google approval or certification.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Store host or URL |
No output schema declared.
No examples provided.
list_monitors ~56
[Requires sign-in] List the workspace's monitors — each store re-checked on a schedule for whether personal agents can still reach it and its checkout. Includes cadence, status, last score, next run, and the monitor id.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_readiness_checks ~52
[Requires sign-in] List this workspace's recent readiness checks (newest first) — each store, its score, status, and id. Use an id with get_readiness_result to reopen a check.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
monitor_summary ~41
[Requires sign-in] Overview of whether monitored stores are still buyable by personal agents: latest score, trend, status, next run, and recent regression alerts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause_monitor ~50
[Requires sign-in] Pause a monitor so it stops running on schedule (its history is kept). Use the monitor id from list_monitors.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id from list_monitors. |
No output schema declared.
No examples provided.
product_data_check ~62
Free latest saved product data and return/shipping policy check from the store's pages and structured data. Reads history only; no store fetch or model call. A missing result is not a zero.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
report_checkout ~250
Report how far one agent got at one store. Free, no login. Omit contributor_key and ARC issues one. Emails, phones, street addresses, card numbers, IP addresses, and private hosts are rejected. The report stays private until 3 independent contributors with a day-old key, or enough reputation, agree within 14 days. A blocked outcome also waits for ARC's free HTTP recheck. Same as POST /api/outcomes.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_family | string | yes | Agent family, such as browser or a model family. No personal name. |
| agent_name | string | yes | Name of the agent that tried the checkout. No personal name. |
| blocker | string | yes | What stopped the agent, or none. |
| contributor_key | string | – | Optional. Omit it and ARC returns a free key. Send that key on later reports. |
| furthest_step | string | yes | Furthest step the agent reached. |
| store_domain | string | yes | Store hostname, such as allbirds.com. |
| store_error_text | string | – | Optional store error text. Personal data is stripped. |
| timestamp | string | yes | ISO 8601 time of the attempt, within the last 14 days. |
No output schema declared.
No examples provided.
resume_monitor ~31
[Requires sign-in] Resume a paused monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id from list_monitors. |
No output schema declared.
No examples provided.
run_monitor_now ~71
[Requires sign-in] Run a monitor's scan immediately (off-schedule) to establish or refresh its baseline. Consumes one scan credit — only call when the user explicitly asks to run now. Use the monitor id from list_monitors.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id from list_monitors. |
No output schema declared.
No examples provided.
update_monitor ~64
[Requires sign-in] Change a monitor's cadence (daily/weekly/monthly) or label. Use the monitor id from list_monitors.
| Name | Type | Req | Description |
|---|---|---|---|
| frequency | string | – | – |
| id | string | yes | Monitor id from list_monitors. |
| label | string | – | – |
No output schema declared.
No examples provided.
How do I install the ARC: agent checkout reachability MCP server?
ARC: agent checkout reachability is a hosted endpoint at https://www.arcreport.ai/api/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 · www.arcreport.ai
claude mcp add --transport http ai-arcreport-mcp 'https://www.arcreport.ai/api/mcp'
What is the ARC: agent checkout reachability MCP server?
ARC: agent checkout reachability is an MCP server listed in the public MCP registry as ai.arcreport/mcp. Free, no sign-in MCP: can AI agents reach checkout at a store? Try: Use ARC to check allbirds.com. This page covers its hosted endpoint (https://www.arcreport.ai/api/mcp).
Is the ARC: agent checkout reachability MCP server safe to use?
ARC: agent checkout reachability scores 78 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 ARC: agent checkout reachability MCP server expose?
ARC: agent checkout reachability exposes 19 tools: check_store, find_stores, report_checkout, get_store_hub, google_checkout_readiness, and 14 more. Their descriptions and schemas cost roughly 2,193 tokens of context every time the server is loaded.
Does the ARC: agent checkout reachability MCP server require authentication?
Yes. ARC: agent checkout reachability asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the ARC: agent checkout reachability MCP server still maintained?
ARC: agent checkout reachability is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.