Woocommerce (lockon0927) MCP Server

@lockon0927/woocommerce-mcp npm v1.0.6

Published by @lockon0927 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for WooCommerce integration

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Read-and-egress in one tool: "woo_webhooks_create"MTC-FLOW-003

Tool "woo_webhooks_create" can both read sensitive data and send data to an external destination. Even without an explicit untrusted-input leg, this is a single-call data-exfiltration path if the model is ever manipulated.

Fix: Separate reading from sending; require explicit user confirmation before egress of file/secret contents.

Location: flow woo_webhooks_create

medium Unconstrained URL/host parameter "delivery_url" on "woo_webhooks_create"MTC-CAP-007

Tool "woo_webhooks_create" takes a URL/host parameter "delivery_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool woo_webhooks_create · inputSchema.properties.delivery_url

Tools 55

Each tool and what it can reach — statically extracted from the published source.

  • woo_webhooks_createnetwork egressreads sensitive data
  • woo_coupons_createno sensitive capability
  • woo_coupons_deleteno sensitive capability
  • woo_coupons_getno sensitive capability
  • woo_coupons_listno sensitive capability
  • woo_coupons_updateno sensitive capability
  • woo_customers_createno sensitive capability
  • woo_customers_getno sensitive capability
  • woo_customers_listno sensitive capability
  • woo_customers_updateno sensitive capability
Show 45 more tools ↓
  • woo_orders_batch_updateno sensitive capability
  • woo_orders_createno sensitive capability
  • woo_orders_deleteno sensitive capability
  • woo_orders_getno sensitive capability
  • woo_orders_listno sensitive capability
  • woo_orders_notes_createno sensitive capability
  • woo_orders_refunds_createno sensitive capability
  • woo_orders_updateno sensitive capability
  • woo_payment_gateways_getno sensitive capability
  • woo_payment_gateways_listno sensitive capability
  • woo_payment_gateways_updateno sensitive capability
  • woo_products_batch_updateno sensitive capability
  • woo_products_categories_createno sensitive capability
  • woo_products_categories_listno sensitive capability
  • woo_products_createno sensitive capability
  • woo_products_deleteno sensitive capability
  • woo_products_getno sensitive capability
  • woo_products_listno sensitive capability
  • woo_products_reviews_listno sensitive capability
  • woo_products_tags_listno sensitive capability
  • woo_products_updateno sensitive capability
  • woo_products_variations_listno sensitive capability
  • woo_reports_customersno sensitive capability
  • woo_reports_low_stockno sensitive capability
  • woo_reports_ordersno sensitive capability
  • woo_reports_productsno sensitive capability
  • woo_reports_salesno sensitive capability
  • woo_reports_stockno sensitive capability
  • woo_reports_top_sellersno sensitive capability
  • woo_settings_getno sensitive capability
  • woo_settings_listno sensitive capability
  • woo_shipping_zone_methods_createno sensitive capability
  • woo_shipping_zone_methods_listno sensitive capability
  • woo_shipping_zones_createno sensitive capability
  • woo_shipping_zones_getno sensitive capability
  • woo_shipping_zones_listno sensitive capability
  • woo_shipping_zones_updateno sensitive capability
  • woo_system_statusno sensitive capability
  • woo_system_tools_listno sensitive capability
  • woo_system_tools_runno sensitive capability
  • woo_tax_classes_listno sensitive capability
  • woo_tax_rates_createno sensitive capability
  • woo_tax_rates_getno sensitive capability
  • woo_tax_rates_listno sensitive capability
  • woo_webhooks_listno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.6 latest A 93/100 2 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/lockon0927-woocommerce-mcp/badge.svg)](https://mcptrustchecker.com/registry/lockon0927-woocommerce-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/lockon0927-woocommerce-mcp"><img src="https://mcptrustchecker.com/registry/lockon0927-woocommerce-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/lockon0927-woocommerce-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @lockon0927/woocommerce-mcp --online

Use the free API → How scoring works

Other implementations of Woocommerce 7

Independent packages implementing the same tool, scanned with the same engine. Compare all 8 side by side →

More in API Development