AgentReady Woo

by xyz.utilityhouse

Overview Discussions Admin

Server Details

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

Ownership verified

Status: Healthy
Last Tested: 2026-09-21 13:38
Transport: Streamable HTTP · MCP 2025-06-18
URL
Repository: tytutueh13-sudo/agentready-woo
GitHub Stars: 0
Server Listing: agentready-woo

TDQS

A4.2/5.0

Scored 2026-09-10 20:00 across 5 tools

Disambiguation5/5

Every tool has a distinct role: preflight vs scan are explicitly differentiated by purpose (specific release vs general audit), and the three release verification tools form a clear start/get/claim lifecycle. No two tools overlap ambiguously.

Naming Consistency5/5

All tools follow a consistent verb_woo_<resource> snake_case pattern (claim/get/start_woo_release_*, preflight/scan_woo_store_*). The naming clearly indicates the action and domain, with no stylistic mixing.

Tool Count5/5

Five tools is well-scoped for this server's dual purpose of store readiness auditing and release verification. Each tool earns its place with no redundancy or bloat.

Completeness5/5

The store readiness side covers both specific preflight checks and general scans, while the release verification side covers the full start, retrieve, and claim lifecycle. No critical operations appear missing for the stated domain.

Available Tools

5 tools

claim_woo_release_resultAInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`run_id`	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.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds meaningful behavior beyond the generic annotations: it discloses the required permission ('release:claim') and the billing implication ('replay is never billable'). It also implies one-time claim semantics. It does not state what happens on a repeated claim (e.g., error vs. idempotent no-op), but the disclosed information is useful and non-contradictory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences deliver the core action ('Claim a completed Release Gate result once') and immediately add the two key constraints (permission and billing). No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single parameter, an existing output schema, and modest annotation coverage, the description provides enough context: what to claim, when it applies, required permission, and billing behavior. It does not explain what happens if the same run_id is claimed twice, but the 'once' wording partially covers that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The run_id parameter is already fully documented in the schema, including its source, ownership constraint, and what values must NOT be passed. With 100% schema coverage, the description does not need to add much; it remains at baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Claim') with a clear object ('a completed Release Gate result') and a key qualifier ('once'). This distinguishes it semantically from sibling tools like get_woo_release_verification and start_woo_release_verification, though it does not explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'completed Release Gate result' implies the tool is used after verification finishes, and 'Requires release:claim' gives an authorization condition. However, there is no explicit guidance on when to use this tool instead of get_woo_release_verification, nor any exclusion or prerequisite beyond the permission.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_woo_release_verificationA

Read-only

Inspect

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

ParametersJSON Schema

Name	Required	Description	Default
`run_id`	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.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds meaningful behavioral context beyond the annotations: it discloses the auth requirement (release:read) and the ownership constraint (run must belong to the bearer token account). This enriches the agent's understanding of what the tool can and cannot do without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one concise sentence that states the action and the permission requirement, with no filler. It is front-loaded with the core purpose and then the constraint, making it efficient for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple getter with an output schema and read-only annotations, the description covers the essential context: what it does, the required permission, and the ownership constraint. It does not need to explain return values because an output schema exists, and there are no side effects to disclose. It is complete for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides 100% coverage of the single parameter run_id, with a detailed description explaining its origin, ownership, and what not to substitute. The tool description adds no additional parameter semantics beyond what the schema already offers, so the baseline of 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb 'get' and a specific resource 'Release Gate run', and adds an ownership constraint ('owned by the bearer token account') that clearly distinguishes it from sibling tools like start_woo_release_verification (creation) and claim_woo_release_result (claiming a result). It also mentions the required permission, making the tool's purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a permission requirement ('Requires release:read') which implies the tool is only usable under that condition, but it does not explicitly state when to use this tool versus alternatives like claim_woo_release_result or start_woo_release_verification. Usage is implied (retrieve a run you started), but no explicit when/when-not guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

preflight_woo_storeA

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`store_origin`	Yes	Public HTTPS origin of the WooCommerce store, with no path, query, credentials, private host, or customer data; for example https://shop.example.com.
`requested_families`	No	Public protocol families to inspect. Omit to check all supported families; use only woo, robots, jsonld, mcp, ucp, or acp.

Output Schema

ParametersJSON Schema

Name	Required	Description
`kind`	Yes
`state`	Yes
`checks`	Yes
`unknowns`	Yes
`observed_at`	Yes
`sample_seed`	Yes
`sample_size`	Yes
`store_origin`	Yes
`catalogue_total`	Yes
`protocol_bundles`	Yes
`requested_families`	Yes

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds meaningful behavioral context beyond the annotations: it states the tool 'changes nothing', is free, and that BLOCKED or UNMEASURED is an abstention rather than a finding. This explains result semantics and side-effect profile, which annotations alone (readOnlyHint, openWorldHint, destructiveHint) do not cover. It reinforces the read-only nature and clarifies how to interpret outcomes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all information-dense and front-loaded. The primary usage constraint is stated first, the exclusion and alternative second, and the behavioral/result semantics third. No filler or redundant content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 params, output schema present), the description covers usage context, scope, result interpretation, side-effects, and the alternative tool. It is complete for an agent to decide when to call it and what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters (store_origin and requested_families) are already documented in the schema. The description references 'selected public surfaces' but does not add syntax or format details beyond the schema's own descriptions. With full schema coverage, the baseline of 3 is appropriate; the description provides marginal added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool inspects public WooCommerce and agent-protocol surfaces and returns per-family evidence (PASS, FAIL, BLOCKED, UNMEASURED). It explicitly distinguishes itself from scan_woo_store_readiness by naming it as the alternative for general scores or fix lists, so an agent can tell them apart without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance ('Use ONLY before a specific WooCommerce update or release when you need protocol-family evidence') and when-not-to ('Do NOT use it for a general score or fix list'), naming the sibling tool to use instead. No inference is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

scan_woo_store_readinessA

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`demo`	No	Run a deterministic synthetic demonstration instead of scanning a live store.
`store_url`	No	Public HTTPS origin of the WooCommerce storefront, for example https://shop.example.com

Output Schema

ParametersJSON Schema

Name	Required	Description
`grade`	Yes
`score`	Yes
`state`	Yes	UNREADABLE is an abstention, not a verdict about the store.
`checks`	Yes
`billable`	Yes
`scanned_at`	Yes
`unreadable`	Yes	Why nothing could be read. Null when the scan produced a score.
`evidence_status`	Yes
`recommendations`	Yes
`product_count_sampled`	Yes

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations, the description discloses that it reads only public pages, returns aggregate checks/recommendations without product text or customer data, and abstains with null score/grade when the store is unreadable. This clarifies non-obvious behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the exact use case and exclusion, followed by essential behavioral details accordingly. Every sentence adds decision-relevant info without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete enough: it distinguishes from sibling preflight_woo_store, clarifies read-only scope, return nature, and unreadable handling, while params are fully covered by an explicit schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters (store_url and demo) are clearly described in the schema. The description reinforces that the store URL should be an HTTPS origin but does not add significant new parameter semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('audit/readiness/fix recommendations' for a WooCommerce storefront) and explicitly differentiates itself from the sibling preflight_woo_store, telling the agent exactly what it is for and what it is not for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use the tool (general audit, readiness score, fix recommendations), when NOT to use it (specific update/release verification), and names the alternative tool (preflight_woo_store). It also specifies the required input type (public HTTPS origin).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

start_woo_release_verificationBInspect

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

ParametersJSON Schema

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

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

B3.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive. The description adds the auth requirement (bearer token with release:start), which is useful, but does not elaborate on side effects or the meaning of openWorldHint. It is consistent with annotations, so no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is front-loaded with the core purpose and contains no filler. It is appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and annotations cover safety, the description is minimal but adequate for initiating a run. However, it does not explain the openWorldHint or mention that this likely starts an asynchronous process, leaving some context implicit. Overall, it is sufficient but not rich.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds no parameter-specific information; all semantics are already in the schema. The description does not compensate for anything because nothing is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool starts an ownership-authorized Release Gate run, using a specific verb and resource. It does not mention sibling tools or differentiate itself, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus its siblings (claim, get, preflight, scan). It only says 'start a run,' implying the obvious, but does not state prerequisites beyond a bearer token or indicate when alternatives are more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesSep 10, 2026

Changedclaim_woo_release_result1 field changed

addedInput schema / properties / run_id / description

Added value: +"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."

Changedget_woo_release_verification1 field changed

addedInput schema / properties / run_id / description

Added value: +"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."

Changedpreflight_woo_store2 fields changed

addedInput schema / properties / requested_families / description

Added value: +"Public protocol families to inspect. Omit to check all supported families; use only woo, robots, jsonld, mcp, ucp, or acp."

addedInput schema / properties / store_origin / description

Added value: +"Public HTTPS origin of the WooCommerce store, with no path, query, credentials, private host, or customer data; for example https://shop.example.com."

Changedstart_woo_release_verification6 fields changed

addedInput schema / properties / baseline_run_id / description

Added value: +"Optional prior Release Gate run identifier from the same owned store to use as the comparison baseline; omit when no valid baseline exists."

addedInput schema / properties / idempotency_key / description

Added value: +"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."

addedInput schema / properties / mode / description

Added value: +"Required safety mode. The only accepted value is owned-safe-active, which requires verified store ownership before the run starts."

addedInput schema / properties / mode / type
```
Added value: +"string"
```

addedInput schema / properties / requested_families / description

Added value: +"One or more protocol families the owner authorizes this Release Gate run to verify: woo, robots, jsonld, mcp, ucp, or acp."

addedInput schema / properties / store_id / description

Added value: +"AgentReady store identifier owned by the authenticated account. Use the stored identifier, never a store URL, secret, or customer value."

1 tool updateSep 8, 2026

Changedpreflight_woo_store1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "catalogue_total": {
+      "minimum": 0,
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "checks": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "evidence": {
+            "type": "object"
+          },
+          "family": {
+            "enum": [
+              "woo",
+              "robots",
+              "jsonld",
+              "mcp",
+              "ucp",
+              "acp"
+            ],
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "reasonCode": {
+            "enum": [
+              "TARGET_INVALID",
+              "TARGET_PRIVATE",
+              "TARGET_REDIRECT_UNSAFE",
+              "TARGET_DNS_REBIND",
+              "TARGET_TIMEOUT",
+              "TARGET_BYTES_EXCEEDED",
+              "TARGET_RATE_LIMITED",
+              "ROBOTS_BLOCKED",
+              "WOO_API_UNAVAILABLE",
+              "WOO_SAMPLE_EMPTY",
+              "JSONLD_PRODUCT_MISSING",
+              "JSONLD_OFFER_MISSING",
+              "DISCOVERY_UNDECLARED",
+              "PROTOCOL_VERSION_UNSUPPORTED",
+              "PROTOCOL_SCHEMA_INVALID",
+              "MCP_INITIALIZE_FAILED",
+              "MCP_TOOLS_LIST_FAILED",
+              "MCP_TOOL_ANNOTATION_UNSAFE",
+              "MCP_TOOL_CALL_FAILED",
+              "UCP_PROFILE_INVALID",
+              "ACP_PROFILE_INVALID",
+              "CROSS_SURFACE_CONFLICT",
+              "OWNERSHIP_REQUIRED",
+              "OWNERSHIP_EXPIRED",
+              "ACTIVE_FLOW_FORBIDDEN",
+              "EVIDENCE_INVALID",
+              "INFRA_PERSISTENCE_FAILED",
+              "UNMEASURED_SOURCE",
+              "CONNECTION_UNVERIFIABLE",
+              "INVALID_MIME",
+              "INVALID_JSON",
+              "PAGINATION_DRIFT",
+              "CANCELED_BY_CALLER"
+            ],
+            "type": "string"
+          },
+          "state": {
+            "enum": [
+              "PASS",
+              "FAIL",
+              "BLOCKED",
+              "NOT_APPLICABLE",
+              "UNMEASURED"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "family",
+          "state",
+          "evidence"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "kind": {
+      "const": "preflight"
+    },
+    "observed_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "protocol_bundles": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "requested_families": {
+      "items": {
+        "enum": [
+          "woo",
+          "robots",
+          "jsonld",
+          "mcp",
+          "ucp",
+          "acp"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "sample_seed": {
+      "type": "string"
+    },
+    "sample_size": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "state": {
+      "enum": [
+        "ACCEPTED",
+        "REJECTED",
+        "PARTIAL",
+        "BLOCKED",
+        "UNMEASURED"
+      ],
+      "type": "string"
+    },
+    "store_origin": {
+      "format": "uri",
+      "type": "string"
+    },
+    "unknowns": {
+      "items": {
+        "enum": [
+          "TARGET_INVALID",
+          "TARGET_PRIVATE",
+          "TARGET_REDIRECT_UNSAFE",
+          "TARGET_DNS_REBIND",
+          "TARGET_TIMEOUT",
+          "TARGET_BYTES_EXCEEDED",
+          "TARGET_RATE_LIMITED",
+          "ROBOTS_BLOCKED",
+          "WOO_API_UNAVAILABLE",
+          "WOO_SAMPLE_EMPTY",
+          "JSONLD_PRODUCT_MISSING",
+          "JSONLD_OFFER_MISSING",
+          "DISCOVERY_UNDECLARED",
+          "PROTOCOL_VERSION_UNSUPPORTED",
+          "PROTOCOL_SCHEMA_INVALID",
+          "MCP_INITIALIZE_FAILED",
+          "MCP_TOOLS_LIST_FAILED",
+          "MCP_TOOL_ANNOTATION_UNSAFE",
+          "MCP_TOOL_CALL_FAILED",
+          "UCP_PROFILE_INVALID",
+          "ACP_PROFILE_INVALID",
+          "CROSS_SURFACE_CONFLICT",
+          "OWNERSHIP_REQUIRED",
+          "OWNERSHIP_EXPIRED",
+          "ACTIVE_FLOW_FORBIDDEN",
+          "EVIDENCE_INVALID",
+          "INFRA_PERSISTENCE_FAILED",
+          "UNMEASURED_SOURCE",
+          "CONNECTION_UNVERIFIABLE",
+          "INVALID_MIME",
+          "INVALID_JSON",
+          "PAGINATION_DRIFT",
+          "CANCELED_BY_CALLER"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "kind",
+    "state",
+    "store_origin",
+    "requested_families",
+    "sample_seed",
+    "sample_size",
+    "catalogue_total",
+    "checks",
+    "protocol_bundles",
+    "observed_at",
+    "unknowns"
+  ],
+  "type": "object"
+}

5 tool updatesSep 7, 2026

Addedclaim_woo_release_result
Addedget_woo_release_verification
Addedpreflight_woo_store

Changedscan_woo_store_readiness1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "billable": {
+      "const": false
+    },
+    "checks": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "ok": {
+            "type": "boolean"
+          },
+          "weight": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "label",
+          "ok",
+          "weight"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "evidence_status": {
+      "enum": [
+        "LIVE_PUBLIC_SCAN",
+        "SYNTHETIC_DEMO"
+      ],
+      "type": "string"
+    },
+    "grade": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "product_count_sampled": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "recommendations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "scanned_at": {
+      "type": "integer"
+    },
+    "score": {
+      "maximum": 100,
+      "minimum": 0,
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "state": {
+      "description": "UNREADABLE is an abstention, not a verdict about the store.",
+      "enum": [
+        "SCORED",
+        "UNREADABLE"
+      ],
+      "type": "string"
+    },
+    "unreadable": {
+      "additionalProperties": false,
+      "description": "Why nothing could be read. Null when the scan produced a score.",
+      "properties": {
+        "detail": {
+          "type": "string"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "reason",
+        "detail"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "state",
+    "score",
+    "grade",
+    "unreadable",
+    "checks",
+    "product_count_sampled",
+    "recommendations",
+    "scanned_at",
+    "billable",
+    "evidence_status"
+  ],
+  "type": "object"
+}

Addedstart_woo_release_verification

2 tool updatesSep 5, 2026
- Removedagentready_woo_agentic_commerce_readiness_toolkit_for_self_h
- Addedscan_woo_store_readiness

1 tool updateSep 3, 2026

Changedagentready_woo_agentic_commerce_readiness_toolkit_for_self_h7 fields changed

addedInput schema / properties / action / enum

Added value: +[
+  "search_products",
+  "get_offer",
+  "get_feed",
+  "create_cart_link",
+  "verify_cart_link"
+]

addedInput schema / properties / cart_url

Added value: +{
+  "description": "verify_cart_link only",
+  "type": "string"
+}

addedInput schema / properties / page

Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / per_page

Added value: +{
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / product_id

Added value: +{
+  "description": "get_offer and create_cart_link",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / quantity

Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "search_products only",
+  "maxLength": 200,
+  "type": "string"
+}

1 tool updateSep 1, 2026
- First observedagentready_woo_agentic_commerce_readiness_toolkit_for_self_h

Related MCP Connectors

Site Passport A
org.sitepassport
Live-checks whether a WordPress site is ready to be safely operated by AI agents.
AI & Machine Learning Monitoring Security
11
ACN Preflight C
io.github.Abacore-net
Preflight checks for agent repository contributions, bounty work, and Base payments.
31
Agent Utility MCP A
io.github.insivotron
Stop your agent before it runs rm -rf /etc or emails your .env. Deterministic preflight checks.
Security Agent Orchestration Autonomous Agents
41
Woo Revenue Incident Graph A
io.github.tytutueh13-sudo
Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
E-commerce & Retail Payments & Billing Monitoring
41

Related MCP Servers

evidence-lint
Research & Data Testing & QA Tools
Dankaro-projects
A
license
Not graded
quality
C
maintenance
Enables AI agents to run evidence QC gates mid-workflow—checking claims, sources, prose, and vault hygiene deterministically before research ships.
Updated 3 days ago (2026-09-18 05:44 UTC)
MIT
haiec-ai-agent-security-free
Code Analysis Penetration Testing AI & Machine Learning
subodhkc
A
license
A
quality
A
maintenance
Offers a control surface for AI agent security with four independent checks: source-code scanning, tenant isolation, LLM content verification, and deploy gating. Currently in pre-release, with no functional scanning engines yet.
Updated a month ago (2026-08-21 05:19 UTC)
1
5,465 npm
4
MIT
K-Work Trust Public Demo
Autonomous Agents Security
hycore220
F
license
Not graded
quality
D
maintenance
Remote MCP/API trust gate for AI agents to inspect readiness before performing Korean business workflow operations like vendor onboarding and payment release.
Updated 4 months ago (2026-05-13 22:21 UTC)
-
flashgate
Embedded system Testing & QA Tools CI/CD & DevOps
Lion-1209
A
license
Not graded
quality
A
maintenance
The agent can't claim the firmware works — until the board says so. Hardware-in-the-loop verification gate: build → flash → boot banner → exit code.
Updated 3 days ago (2026-09-18 02:26 UTC)
1
MIT

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources