About AgentReady Woo
AgentReady Woo checks the public, agent-facing surfaces of WooCommerce stores and supports owner-authorized release gates. It gives deployment teams reasoned states without changing orders, checkout, inventory, or payment access.
Key features
- 01Read-only WooCommerce public preflight
- 02Checks robots, JSON-LD, MCP, UCP, and ACP
- 03Reason-coded states and unknown reasons
- 04Owner-authorized release gate
- 05Node 24 deployment action
Use cases
- 01Check store-facing protocols after a release
- 02Add a readiness gate to deployment workflows
- 03Review signed aggregate plugin evidence
MCP support
The hosted MCP endpoint advertises tools for public store scans, release preflight, and owner-authorized gate runs. Some gate tools require a scoped bearer token and verified store ownership.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://app.utilityhouse.xyz/mcpclaude mcp add --transport http xyz-utilityhouse-agentready-woo https://app.utilityhouse.xyz/mcp{"mcpServers":{"xyz-utilityhouse-agentready-woo":{"type":"http","url":"https://app.utilityhouse.xyz/mcp"}}}Open in Cursor{"servers":{"xyz-utilityhouse-agentready-woo":{"type":"http","url":"https://app.utilityhouse.xyz/mcp"}}}Open in VS Code{"mcpServers":{"xyz-utilityhouse-agentready-woo":{"type":"http","url":"https://app.utilityhouse.xyz/mcp"}}}{"mcpServers":{"xyz-utilityhouse-agentready-woo":{"serverUrl":"https://app.utilityhouse.xyz/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
5| Parameter | Type | Required | Description |
|---|---|---|---|
| demo | boolean | No | Run a deterministic synthetic demonstration instead of scanning a live store. |
| store_url | string | No | Public HTTPS origin of the WooCommerce storefront, for example https://shop.example.com |
Details
From the project READMEAgentReady Woo — WooCommerce Release Gate

Verify the agent-facing WooCommerce surface after a release—without touching orders, checkout or payment credentials.
Run the free public preflight or add the
dependency-free Node 24 action to a deployment workflow. It fails CI only on an
explicit HOLD by default; BLOCKED, UNMEASURED and UNREADABLE remain
visible abstentions.
- name: AgentReady Woo preflight
uses: tytutueh13-sudo/agentready-woo@v1
with:
store-origin: https://shop.example
What the release check gives you
- One read-only public preflight for WooCommerce, robots, JSON-LD, MCP, UCP and ACP surfaces.
- A finite decision and unknown-reason list instead of a padded readiness score.
- An optional owner-authorized gate fed by signed, aggregate-only WordPress evidence.
- No order creation, inventory reservation, checkout mutation or payment access.
Live service: app.utilityhouse.xyz
AgentReady runs a passive public preflight, then lets a verified store owner make a version-pinned release decision from signed plugin evidence. A target that cannot be read returns an abstention rather than a fabricated low score.
This is not a certification, ranking promise or checkout test. The root tools do not create orders, reserve inventory, send customer email or handle payment credentials.
Public MCP tools
POST https://app.utilityhouse.xyz/mcp speaks MCP JSON-RPC 2.0 and advertises
five tools. Always use
tools/list as the authoritative schema.
| Tool | Use it for |
|---|---|
scan_woo_store_readiness | A general public-store audit, score and fix list |
preflight_woo_store | Protocol-family evidence for a specific update or release |
Three additional tools start, read and claim an owner-authorized Release Gate run. They require a scoped bearer token and verified store ownership.
The general scanner returns state: UNREADABLE with score: null when it
cannot read the target. Diagnostic accuracy against real merchant stores is
unmeasured. Release Gate settlement is disabled.
GitHub Action
The repository includes a dependency-free Node 24 action. It calls the same
public preflight contract, writes a reason-coded job summary and fails only on
an explicit HOLD. BLOCKED and UNMEASURED remain abstentions.
Add families: woo,robots,jsonld,mcp when the workflow should check only those
four protocol families.
The public endpoint allows three calls per target origin per day and ten calls per calling IP per day. The action changes nothing on the store.
WordPress plugin
wordpress-plugin/utilityhouse-release-gate-for-woocommerce is version 1.2.1. It provides a useful local
readiness snapshot before connection. Activation neither contacts UtilityHouse
nor creates a schedule. An administrator must make a one-time manual send or
separately opt in to a daily signed aggregate evidence schedule.
The evidence envelope contains version identifiers, opaque store/run fields, timestamps, nonce, family name and aggregate check state/count. It contains no customer, order, payment, email, address, product description, URL, credential or raw log field.
Build the deterministic plugin package with:
npm run build:plugin
Try the local-only snapshot without touching a real store in the version-pinned WordPress Playground demo. The disposable site configures no UtilityHouse endpoint and sends no evidence.
REST preflight
POST https://app.utilityhouse.xyz/api/v2/preflight is documented in
mcp-registry/openapi-preflight.yaml. HTTP 200 does not necessarily mean the
target was measurable; inspect the returned state and per-family checks.
Separate commerce surface
An authenticated account may connect read-only WooCommerce credentials to a
store-bound catalog, offer and signed cart-handoff surface at /mcp/{store_id}.
That is a separate product contract and does not grant Release Gate access.
Checkout and payment remain on the merchant's store.
Development
npm install
npm run typecheck
npm test
npm run test:wordpress
This public repository is a review mirror, not the production deployment
source. Its wrangler.toml carries a placeholder database id. Deployment is
performed from the private monorepo.
License scope
action.ymlandaction/**are licensed under the MIT License inaction/LICENSE.wordpress-plugin/utilityhouse-release-gate-for-woocommerce/**is licensed GPL-2.0-or-later as declared in the plugin header andreadme.txt.- No license is granted for the remaining server, test, deployment or mirror files unless a file or subtree states one explicitly. Those files remain all rights reserved.
The scoped licenses do not apply to the hosted AgentReady service, its data, trademarks or private deployment configuration.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.