AgentReady Woo
REMOTE · APP.UTILITYHOUSE.XYZ
Check WooCommerce agent readiness and run owner-authorized release gates.
Available components
Last scanned (4 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 739 tokens (~147/item across 5 items; 5 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 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 10 Oct 26 +14
- Stability: fail → 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
- 11 Sept 26 0
- DNSSEC: fail → pass ▲ security
- 10 Sept 26 0
- Schema quality: pass → fail ▼ functional
- Tool coverage: 18% → 100% ▲ functional
- Schema quality: good → excellent functional
- “claim_woo_release_result” reworded the description of “run_id” cosmetic
- “get_woo_release_verification” reworded the description of “run_id” cosmetic
- “preflight_woo_store” reworded the description of “requested_families” cosmetic
- “preflight_woo_store” reworded the description of “store_origin” cosmetic
- “start_woo_release_verification” reworded the description of “baseline_run_id” cosmetic
- “start_woo_release_verification” reworded the description of “idempotency_key” cosmetic
- “start_woo_release_verification” reworded the description of “mode” cosmetic
- “start_woo_release_verification” reworded the description of “requested_families” cosmetic
- “start_woo_release_verification” reworded the description of “store_id” cosmetic
- 9 Sept 26 0
- Tool “scan_woo_store_readiness” rewrote its description, which is the text the model reads security
- Tool “preflight_woo_store” rewrote its description, which is the text the model reads security
- Schema quality: 71 → 95 ▼ functional
- Schema quality: 71 → 83 ▼ functional
- Tool coverage: 80% → 100% ▲ functional
- Tool “preflight_woo_store” now declares an output schema ▲ functional
- Server version: 1.1.0 → 1.2.0 functional
- 7 Sept 26 0
- Stability: 0.13 → fail ▼ security
- Tool “agentready_woo_agentic_commerce_readiness_toolkit_for_self_h” was removed ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 43% → 18% ▼ functional
- Schema quality: fail → pass ▲ functional
- First check of Tool coverage: 80 functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “claim_woo_release_result” functional
- New tool “get_woo_release_verification” functional
- New tool “preflight_woo_store” functional
- New tool “scan_woo_store_readiness” functional
- New tool “start_woo_release_verification” functional
- 4 Sept 26 0
- HSTS header: fail → pass ▲ security
- The server changed its declared name: early-3426536d88daa242 → agentready-woo security
- Tool “agentready_woo_agentic_commerce_readiness_toolkit_for_self_h” rewrote its description, which is the text the model reads security
- Schema quality: 287 → 320 ▼ functional
- Tool coverage: 0% → 43% ▲ functional
- Schema quality: fair → good functional
- “agentready_woo_agentic_commerce_readiness_toolkit_for_self_h” added an optional parameter “cart_url” cosmetic
- “agentready_woo_agentic_commerce_readiness_toolkit_for_self_h” added an optional parameter “page” cosmetic
- “agentready_woo_agentic_commerce_readiness_toolkit_for_self_h” added an optional parameter “per_page” cosmetic
- “agentready_woo_agentic_commerce_readiness_toolkit_for_self_h” added an optional parameter “product_id” cosmetic
- “agentready_woo_agentic_commerce_readiness_toolkit_for_self_h” added an optional parameter “quantity” cosmetic
- “agentready_woo_agentic_commerce_readiness_toolkit_for_self_h” added an optional parameter “query” cosmetic
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://app.utilityhouse.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=utilityhouse.xyz | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b7d08bfaebce2f4813240d053bb014f9 |
| SANs: utilityhouse.xyz, app.utilityhouse.xyz, *.app.utilityhouse.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of app.utilityhouse.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| utilityhouse.xyz. | present | 2371 | 13 | Verified |
| app.utilityhouse.xyz. | Verified address RRset verified with the apex keys |
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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://cdn.paddle.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https:; media-src 'self'; connect-src 'self' https://cdn.paddle.com https://checkout.paddle.com; frame-src https://checkout.paddle.com https://buy.paddle.com; form-action 'self' https://accounts.google.com; frame-ancestors 'none'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(self "https://checkout.paddle.com") |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.utilityhouse.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://app.utilityhouse.xyz/mcp | Inconclusive | 404 |
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 →
claim_woo_release_result ~70
Claim a completed Release Gate result once. Requires release:claim; replay is never billable.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | Release Gate run identifier returned by start_woo_release_verification. It must belong to the authenticated account; never substitute a store URL, credential, or customer value. |
Structured output declared, but exposes no named fields.
No examples provided.
get_woo_release_verification ~69
Get a Release Gate run owned by the bearer token account. Requires release:read.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | Release Gate run identifier returned by start_woo_release_verification. It must belong to the authenticated account; never substitute a store URL, credential, or customer value. |
Structured output declared, but exposes no named fields.
No examples provided.
preflight_woo_store ~185
Use ONLY before a specific WooCommerce update or release when you need protocol-family evidence. Do NOT use it for a general score or fix list; use scan_woo_store_readiness for that. Inspect selected public WooCommerce and agent-protocol surfaces and return per-family PASS, FAIL, BLOCKED or UNMEASURED evidence. It changes nothing, is free, and BLOCKED or UNMEASURED is an abstention rather than a finding about the store.
| Name | Type | Req | Description |
|---|---|---|---|
| requested_families | array | – | Public protocol families to inspect. Omit to check all supported families; use only woo, robots, jsonld, mcp, ucp, or acp. |
| store_origin | string | yes | Public HTTPS origin of the WooCommerce store, with no path, query, credentials, private host, or customer data; for example https://shop.example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue_total | integer|null | yes | – |
| checks | array | yes | – |
| kind | – | yes | – |
| observed_at | string | yes | – |
| protocol_bundles | array | yes | – |
| requested_families | array | yes | – |
| sample_seed | string | yes | – |
| sample_size | integer | yes | – |
| state | string | yes | – |
| store_origin | string | yes | – |
| unknowns | array | yes | – |
No examples provided.
scan_woo_store_readiness ~180
Use ONLY for a general storefront audit, readiness score, or fix recommendations. Do NOT use it to inspect a specific update or release; use preflight_woo_store for that. Check whether a public WooCommerce storefront is readable by shopping agents. Provide the store's HTTPS origin. The tool reads only public pages and the public WooCommerce Store API, changes nothing, and returns aggregate checks and recommendations without product text or customer data. When the storefront cannot be read at all, the tool abstains: state is UNREADABLE, score and grade are null, and the caller must not present that as a finding about the store.
| Name | Type | Req | Description |
|---|---|---|---|
| demo | boolean | – | Run a deterministic synthetic demonstration instead of scanning a live store. |
| store_url | string | – | Public HTTPS origin of the WooCommerce storefront, for example https://shop.example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| billable | – | yes | – |
| checks | array | yes | – |
| evidence_status | string | yes | – |
| grade | string|null | yes | – |
| product_count_sampled | integer | yes | – |
| recommendations | array | yes | – |
| scanned_at | integer | yes | – |
| score | number|null | yes | – |
| state | string | yes | UNREADABLE is an abstention, not a verdict about the store. |
| unreadable | object|null | yes | Why nothing could be read. Null when the scan produced a score. |
No examples provided.
start_woo_release_verification ~206
Start an ownership-authorized Release Gate run. Requires a bearer token with release:start.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_run_id | string | – | Optional prior Release Gate run identifier from the same owned store to use as the comparison baseline; omit when no valid baseline exists. |
| idempotency_key | string | yes | Caller-generated retry key for this exact start request. Reuse it only when retrying the same operation; do not place credentials or customer data in it. |
| mode | string | yes | Required safety mode. The only accepted value is owned-safe-active, which requires verified store ownership before the run starts. |
| requested_families | array | yes | One or more protocol families the owner authorizes this Release Gate run to verify: woo, robots, jsonld, mcp, ucp, or acp. |
| store_id | string | yes | AgentReady store identifier owned by the authenticated account. Use the stored identifier, never a store URL, secret, or customer value. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the AgentReady Woo MCP server?
AgentReady Woo is a hosted endpoint at https://app.utilityhouse.xyz/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 · app.utilityhouse.xyz
claude mcp add --transport http xyz-utilityhouse-agentready-woo 'https://app.utilityhouse.xyz/mcp'
What is the AgentReady Woo MCP server?
AgentReady Woo is an MCP server listed in the public MCP registry as xyz.utilityhouse/agentready-woo. Check WooCommerce agent readiness and run owner-authorized release gates. This page covers its hosted endpoint (https://app.utilityhouse.xyz/mcp).
Is the AgentReady Woo MCP server safe to use?
AgentReady Woo 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 AgentReady Woo MCP server expose?
AgentReady Woo exposes 5 tools: scan_woo_store_readiness, preflight_woo_store, start_woo_release_verification, get_woo_release_verification, claim_woo_release_result. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.
Does the AgentReady Woo MCP server require authentication?
No. We connected to AgentReady Woo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentReady Woo MCP server still maintained?
AgentReady Woo 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.