Skip to content

AgentReady Woo MCP server

xyz.utilityhouse/agentready-wooutilityhouse.xyzstreamable-httpv1.2.0Scanned

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

5 tools: 4 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 4 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 6 findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AgentReady Woo MCP server can do

The AgentReady Woo MCP server is published by utilityhouse.xyz, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: scan_woo_store_readiness, preflight_woo_store, start_woo_release_verification and claim_woo_release_result), but cannot delete data. 1 tool only reads.

3 tools bring in text other people can write (scan_woo_store_readiness, preflight_woo_store and start_woo_release_verification).

The fixed checks matched 6 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 4Claude Code: ask
  • claim_woo_release_resultClaim a completed Release Gate result once.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The input schema at properties.run_id.description mentions "credential".

      Matched text

      inputSchema.properties.run_id.description: "...account; never substitute a store URL, credential, or customer value."

      What this check looks for
    Description, as the server wrote it
    Claim a completed Release Gate result once. Requires release:claim; replay is never billable.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • preflight_woo_storeUse ONLY before a specific WooCommerce update or release when you need protocol-family evidence.Reads text others write2 findings

    Why it is in this group

    • The name "preflight_woo_store" says "store": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.store_origin.description mentions "credentials".

      Matched text

      inputSchema.properties.store_origin.description: "...WooCommerce store, with no path, query, credentials, private host, or customer data; for ex..."

      What this check looks for
    • Warn

      The server marks "preflight_woo_store" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "preflight_woo_store" says "store": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • scan_woo_store_readinessUse ONLY for a general storefront audit, readiness score, or fix recommendations.Reads text others write1 finding

    Why it is in this group

    • The name "scan_woo_store_readiness" says "store": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "scan_woo_store_readiness" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "scan_woo_store_readiness" says "store": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • start_woo_release_verificationStart an ownership-authorized Release Gate run.Reads text others write1 finding

    Why it is in this group

    • The name "start_woo_release_verification" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.idempotency_key.description mentions "credentials".

      Matched text

      inputSchema.properties.idempotency_key.description: "...trying the same operation; do not place credentials or customer data in it."

      What this check looks for
    Description, as the server wrote it
    Start an ownership-authorized Release Gate run. Requires a bearer token with release:start.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • get_woo_release_verificationGet a Release Gate run owned by the bearer token account.1 finding

    Why it is in this group

    • The name "get_woo_release_verification" says "get": a word for reading.

    Findings

    • Info

      The input schema at properties.run_id.description mentions "credential".

      Matched text

      inputSchema.properties.run_id.description: "...account; never substitute a store URL, credential, or customer value."

      What this check looks for
    Description, as the server wrote it
    Get a Release Gate run owned by the bearer token account. Requires release:read.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.utilityhouse.xyz/mcp: tools/list returned 5 tools to an anonymous client, including scan_woo_store_readiness (write), preflight_woo_store (write), start_woo_release_verification (write), claim_woo_release_result (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn4 info
  • The server marks "scan_woo_store_readiness" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "scan_woo_store_readiness" says "store": a word for a change.

    What this check looks for
  • The server marks "preflight_woo_store" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "preflight_woo_store" says "store": a word for a change.

    What this check looks for
  • The input schema at properties.store_origin.description mentions "credentials".

    Matched text

    inputSchema.properties.store_origin.description: "...WooCommerce store, with no path, query, credentials, private host, or customer data; for ex..."

    What this check looks for
  • The input schema at properties.idempotency_key.description mentions "credentials".

    Matched text

    inputSchema.properties.idempotency_key.description: "...trying the same operation; do not place credentials or customer data in it."

    What this check looks for
  • The input schema at properties.run_id.description mentions "credential".

    Matched text

    inputSchema.properties.run_id.description: "...account; never substitute a store URL, credential, or customer value."

    What this check looks for
  • The input schema at properties.run_id.description mentions "credential".

    Matched text

    inputSchema.properties.run_id.description: "...account; never substitute a store URL, credential, or customer value."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agentready-woo__get_woo_release_verification"
    ],
    "ask": [
      "mcp__agentready-woo__scan_woo_store_readiness",
      "mcp__agentready-woo__preflight_woo_store",
      "mcp__agentready-woo__start_woo_release_verification",
      "mcp__agentready-woo__claim_woo_release_result"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agentready-woo. Review it before you use it.

Capability tags behind 3 rules
  • mcp__agentready-woo__scan_woo_store_readiness untrusted-input
  • mcp__agentready-woo__preflight_woo_store untrusted-input
  • mcp__agentready-woo__start_woo_release_verification untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/xyz.utilityhouse/agentready-woo/verify?hash=8a574469bf190f9608e61b71a94ece268ad4fb458b88c4d8e09d7103f8e3f690" | jq -e '.changed == false'

Pinned hash 8a574469bf19, from Nov 18, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/xyz.utilityhouse/agentready-woo/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for xyz.utilityhouse/agentready-woo
[![Anlyon Radar](https://radar.anlyon.com/badge/xyz.utilityhouse/agentready-woo.svg)](https://radar.anlyon.com/servers/xyz.utilityhouse/agentready-woo)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.

AgentReady Woo MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AgentReady Woo MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AgentReady Woo MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AgentReady Woo MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the AgentReady Woo MCP server have?

5 tools: 4 write, 1 read. scan_woo_store_readiness, preflight_woo_store, start_woo_release_verification, claim_woo_release_result and get_woo_release_verification.

Does the AgentReady Woo MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AgentReady Woo MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AgentReady Woo MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.