xyz.utilityhouse/agentready-woo

Est-ce que xyz.utilityhouse/agentready-woo est sûr ?

Au dernier audit MCP Hub, le serveur MCP « xyz.utilityhouse/agentready-woo » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• claim_woo_release_result≈ 1521 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • run_id · string · requis
    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.

  Exemple d'appel

  {"name": "claim_woo_release_result", "arguments": {"run_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_woo_release_verification≈ 362 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • run_id · string · requis
    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.

  Exemple d'appel

  {"name": "get_woo_release_verification", "arguments": {"run_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• preflight_woo_store≈ 1021 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • store_origin · string · requis
    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 · array · optionnel
    Public protocol families to inspect. Omit to check all supported families; use only woo, robots, jsonld, mcp, ucp, or acp.

  Exemple d'appel

  {"name": "preflight_woo_store", "arguments": {"store_origin": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"kind": "texte", "state": "ACCEPTED", "checks": [], "unknowns": [], "observed_at": "texte", "sample_seed": "texte", "sample_size": 1, "store_origin": "texte", "catalogue_total": 1, "protocol_bundles": [], "requested_families": []}}

• scan_woo_store_readiness≈ 650 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • demo · boolean · optionnel
    Run a deterministic synthetic demonstration instead of scanning a live store.
  • store_url · string · optionnel
    Public HTTPS origin of the WooCommerce storefront, for example https://shop.example.com

  Exemple d'appel

  {"name": "scan_woo_store_readiness", "arguments": {"demo": true, "store_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"grade": "texte", "score": 1, "state": "SCORED", "checks": [], "billable": "texte", "scanned_at": 1, "unreadable": {}, "evidence_status": "LIVE_PUBLIC_SCAN", "recommendations": [], "product_count_sampled": 1}}

• start_woo_release_verification≈ 631 tokens

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

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "start_woo_release_verification", "arguments": {"mode": "texte", "store_id": "texte", "idempotency_key": "texte", "requested_families": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://app.utilityhouse.xyz/mcp