Store Catalog
REMOTE · STORECATALOG.AGENTTOOLWORKS.COM
Shopify and WooCommerce product catalogs for agents: list, search, full product with barcodes.
Available components
Last scanned (19 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 752 tokens (~150/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://storecatalog.agenttoolworks.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agenttoolworks.com | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1a21db145f4dc0e80e4b7827a7639c1f |
| SANs: agenttoolworks.com, storecatalog.agenttoolworks.com, *.storecatalog.agenttoolworks.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of storecatalog.agenttoolworks.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| agenttoolworks.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://storecatalog.agenttoolworks.com/mcp | Verified | 200 | |
| http (plaintext) | http://storecatalog.agenttoolworks.com/mcp | Inconclusive | 405 |
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 →
get_product Get one product in full ~210
Returns one product of a Shopify or WooCommerce store in full: every variant with its options, SKU, barcode (GTIN/UPC/EAN, Shopify), price and sale price, stock where the store publishes it, weight in grams; options, images with alt text, description as plain text, tags, rating (WooCommerce). Pass the product page URL, or the store URL and the product handle. Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | – | The product handle (Shopify) or slug (WooCommerce), with store_url. Every list_products and search_products row carries it. |
| product_url | string | – | The product page URL, e.g. https://www.allbirds.com/products/mens-wool-runners. |
| store_url | string | – | The store's address: a home page (https://www.allbirds.com), a Shopify collection page (/collections/mens) or a WooCommerce category page (/product-category/shoes/). 'allbirds.com' works too. |
No output schema declared.
No examples provided.
get_usage Get usage and credit balance ~30
Returns your current plan, remaining credit balance and call volume over the last 30 days. Free to call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inspect_store Inspect a Shopify or WooCommerce store ~122
Detects whether a store runs Shopify or WooCommerce and whether its public catalog can be read, and returns its currency and how many products it publishes. Call it first on an unknown store: it is cheap, and every other tool needs a readable store. Light read: costs 0.2 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| store_url | string | yes | The store's address: a home page (https://www.allbirds.com), a Shopify collection page (/collections/mens) or a WooCommerce category page (/product-category/shoes/). 'allbirds.com' works too. |
No output schema declared.
No examples provided.
list_products List a store's products, one page at a time ~227
Lists the products of a Shopify or WooCommerce store, a page at a time, in a compact shape: title, URL, vendor, type, price range, sale price, currency, in stock, variant count, main image. Pass a collection or category page URL, or 'collection', to list only that part. Use 'next_page' from the answer to continue. For one product's variants, barcodes and stock, call get_product. Costs 1 credit per page.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | A Shopify collection handle or WooCommerce category slug, when the URL does not already name one, e.g. 'sale'. |
| page | integer | – | Page number, from 1. Default 1. |
| page_size | integer | – | Products per page, at most 50. Default 25. |
| store_url | string | yes | The store's address: a home page (https://www.allbirds.com), a Shopify collection page (/collections/mens) or a WooCommerce category page (/product-category/shoes/). 'allbirds.com' works too. |
No output schema declared.
No examples provided.
search_products Search a store's products by keyword ~163
Searches one Shopify or WooCommerce store for products matching a keyword, through the store's own public search, and returns the matches in the same compact shape as list_products. Up to 10 results on Shopify (its search limit), up to 20 on WooCommerce. Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results, default 10 (Shopify stops at 10). |
| query | string | yes | What to search for, e.g. 'wool runner' or 'espresso'. |
| store_url | string | yes | The store's address: a home page (https://www.allbirds.com), a Shopify collection page (/collections/mens) or a WooCommerce category page (/product-category/shoes/). 'allbirds.com' works too. |
No output schema declared.
No examples provided.
How do I install the Store Catalog MCP server?
Store Catalog is a hosted endpoint at https://storecatalog.agenttoolworks.com/mcp, 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 · storecatalog.agenttoolworks.com
claude mcp add --transport http com-agenttoolworks-storecatalog 'https://storecatalog.agenttoolworks.com/mcp'
What is the Store Catalog MCP server?
Store Catalog is an MCP server listed in the public MCP registry as com.agenttoolworks/storecatalog. Shopify and WooCommerce product catalogs for agents: list, search, full product with barcodes. This page covers its hosted endpoint (https://storecatalog.agenttoolworks.com/mcp).
Is the Store Catalog MCP server safe to use?
Store Catalog scores 84 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.
What tools does the Store Catalog MCP server expose?
Store Catalog exposes 5 tools: inspect_store, list_products, get_product, search_products, get_usage. Their descriptions and schemas cost roughly 752 tokens of context every time the server is loaded.
Does the Store Catalog MCP server require authentication?
Yes. Store Catalog 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 Catalog MCP server still maintained?
Store Catalog is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Store Catalog MCP server?
VerifyMCP ran 12 checks on Store Catalog, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Store Catalog: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.