# AgentReady Woo (remote · app.utilityhouse.xyz)

Check WooCommerce agent readiness and run owner-authorized release gates.

- Trust score: 68/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `app.utilityhouse.xyz`: 68/100 (this document), [markdown](https://verifymcp.io/servers/xyz-utilityhouse-agentready-woo/app.md), [page](https://verifymcp.io/servers/xyz-utilityhouse-agentready-woo/app)

## Channel facts

- Endpoint: `https://app.utilityhouse.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 19 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 5 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http xyz-utilityhouse-agentready-woo 'https://app.utilityhouse.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-utilityhouse-agentready-woo": {
      "url": "https://app.utilityhouse.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-utilityhouse-agentready-woo": {
      "type": "http",
      "url": "https://app.utilityhouse.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-utilityhouse-agentready-woo]
url = "https://app.utilityhouse.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-utilityhouse-agentready-woo": {
      "type": "remote",
      "url": "https://app.utilityhouse.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-utilityhouse-agentready-woo --url 'https://app.utilityhouse.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-utilityhouse-agentready-woo:
    url: "https://app.utilityhouse.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-utilityhouse-agentready-woo": {
      "Transport": "http",
      "Url": "https://app.utilityhouse.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-utilityhouse-agentready-woo -t streamable-http -u 'https://app.utilityhouse.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-utilityhouse-agentready-woo": {
      "type": "http",
      "url": "https://app.utilityhouse.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-11 (score 68, 0)

- [security improvement] DNSSEC: fail → pass

### 2026-09-10 (score 68, +3)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 18% → 100%
- [functional] Schema quality: good → excellent
- [cosmetic] “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”

### 2026-09-09 (score 65, +1)

- [security] 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
- [functional regression] Schema quality: 71 → 95
- [functional regression] Schema quality: 71 → 83
- [functional improvement] Tool coverage: 80% → 100%
- [functional improvement] Tool “preflight_woo_store” now declares an output schema
- [functional] Server version: 1.1.0 → 1.2.0

### 2026-09-07 (score 64, +6)

- [security regression] Stability: 0.13 → fail
- [security regression] Tool “agentready_woo_agentic_commerce_readiness_toolkit_for_self_h” was removed
- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Tool coverage: 43% → 18%
- [functional improvement] 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”

### 2026-09-05 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 57, +5)

- [security improvement] 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
- [functional regression] Schema quality: 287 → 320
- [functional improvement] Tool coverage: 0% → 43%
- [functional] Schema quality: fair → good
- [cosmetic] “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”

### 2026-09-02 (score 52, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-01 (score 51, +23)

- [security regression] Authorization: fail → unverified
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fair
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail

## MCP tools (5)

### `scan_woo_store_readiness` (~180 tokens)

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.

Input parameters:

- `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

Output parameters:

- `billable`
- `checks` (array)
- `evidence_status` (string)
- `grade` (string|null)
- `product_count_sampled` (integer)
- `recommendations` (array)
- `scanned_at` (integer)
- `score` (number|null)
- `state` (string): UNREADABLE is an abstention, not a verdict about the store.
- `unreadable` (object|null): Why nothing could be read. Null when the scan produced a score.

### `preflight_woo_store` (~185 tokens)

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.

Input parameters:

- `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, required): Public HTTPS origin of the WooCommerce store, with no path, query, credentials, private host, or customer data; for example https://shop.example.com.

Output parameters:

- `catalogue_total` (integer|null)
- `checks` (array)
- `kind`
- `observed_at` (string)
- `protocol_bundles` (array)
- `requested_families` (array)
- `sample_seed` (string)
- `sample_size` (integer)
- `state` (string)
- `store_origin` (string)
- `unknowns` (array)

### `start_woo_release_verification` (~206 tokens)

Start an ownership-authorized Release Gate run. Requires a bearer token with release:start.

Input parameters:

- `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, required): 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, required): Required safety mode. The only accepted value is owned-safe-active, which requires verified store ownership before the run starts.
- `requested_families` (array, required): One or more protocol families the owner authorizes this Release Gate run to verify: woo, robots, jsonld, mcp, ucp, or acp.
- `store_id` (string, required): AgentReady store identifier owned by the authenticated account. Use the stored identifier, never a store URL, secret, or customer value.

### `get_woo_release_verification` (~69 tokens)

Get a Release Gate run owned by the bearer token account. Requires release:read.

Input parameters:

- `run_id` (string, required): 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.

### `claim_woo_release_result` (~70 tokens)

Claim a completed Release Gate result once. Requires release:claim; replay is never billable.

Input parameters:

- `run_id` (string, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-utilityhouse-agentready-woo/app#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 68
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 68
- 2026-09-09: 65
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-05: 58
- 2026-09-04: 57
- 2026-09-03: 52
- 2026-09-02: 52
- 2026-09-01: 51
- 2026-08-31: 28
- 2026-08-30: 28
- 2026-08-29: 28
- 2026-08-28: 28
- 2026-08-27: 28

## Common questions

### 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 68 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://app.utilityhouse.xyz/mcp
- Repository: https://github.com/tytutueh13-sudo/agentready-woo
- Website: https://app.utilityhouse.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-utilityhouse-agentready-woo/app.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-utilityhouse-agentready-woo/app.json
- HTML version of this page: https://verifymcp.io/servers/xyz-utilityhouse-agentready-woo/app