Store Manager for WooCommerce
REMOTE · API.ADDSYNAPSE.COM
Run a WooCommerce store from Claude: reports, SEO, prices, stock. You approve every change first.
Available components
Last scanned (22 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 22 Oct 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 21 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Oct 26 52
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://api.addsynapse.com/mcp/woocommerce
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=addsynapse.com | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 4096 | SHA256-RSA | 5819132e401f9c21a1b9b8c1127c4335854 |
| SANs: addsynapse.com, admin.addsynapse.com, api.addsynapse.com, app.addsynapse.com, guard-api.addsynapse.com, www.addsynapse.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.addsynapse.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| addsynapse.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="addsynapse-mcp", resource_metadata="https://api.addsynapse.com/.well-known/oauth-protected-resource/mcp/woocommerce", scope="ops:read ops:write"
Bearer realm="addsynapse-mcp", resource_metadata="https://api.addsynapse.com/.well-known/oauth-protected-resource/mcp/woocommerce", scope="ops:read ops:write"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| www-authenticate | Bearer realm="addsynapse-mcp", resource_metadata="https://api.addsynapse.com/.well-known/oauth-protected-resource/mcp/woocommerce", scope="ops:read ops:write" |
Protected resource metadata
| Document | https://api.addsynapse.com/.well-known/oauth-protected-resource/mcp/woocommerce |
|---|---|
| Retrieved | Yes |
| Resource | https://api.addsynapse.com/mcp/woocommerce |
| Authorisation server | https://app.addsynapse.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.addsynapse.com/mcp/woocommerce | Verified | 200 | |
| http (plaintext) | http://api.addsynapse.com/mcp/woocommerce | HTTPS enforced | 301 | https://api.addsynapse.com/mcp/woocommerce |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
No tool schema has been captured from this endpoint yet.
How do I install the Store Manager for WooCommerce MCP server?
Store Manager for WooCommerce is a hosted endpoint at https://api.addsynapse.com/mcp/woocommerce, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.addsynapse.com
claude mcp add --transport http com-addsynapse-woocommerce 'https://api.addsynapse.com/mcp/woocommerce'
What is the Store Manager for WooCommerce MCP server?
Store Manager for WooCommerce is an MCP server listed in the public MCP registry as com.addsynapse/woocommerce. Run a WooCommerce store from Claude: reports, SEO, prices, stock. You approve every change first. This page covers its hosted endpoint (https://api.addsynapse.com/mcp/woocommerce).
Is the Store Manager for WooCommerce MCP server safe to use?
Store Manager for WooCommerce scores 52 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Does the Store Manager for WooCommerce MCP server require authentication?
Yes. Store Manager for WooCommerce asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Store Manager for WooCommerce MCP server still maintained?
Store Manager for WooCommerce is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.