ShopSavvy
REMOTE · API.SHOPSAVVY.COM · 2 COMPONENTS
Product lookup, current prices across retailers, price history and buying guides. No key needed.
Available components
Last scanned (11 minutes ago)
Scores higher than 45% of remote servers
Reachable. Last reached 22 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (product_schedule). See how to fix → View diagnostics → Fail
- 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
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3001 tokens (~200/item across 15 items; 15 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 22 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Nov 26 +2
- HSTS header: fail → pass ▲ security
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 55
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 Nov 2026 · Probed https://api.shopsavvy.com/mcp/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.shopsavvy.com | CN=YR2,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | RSA 2048 | SHA256-RSA | 6fbcb7a0e4b062ff3461575a8edc50a99d4 |
| SANs: api.shopsavvy.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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.shopsavvy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| shopsavvy.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://api.shopsavvy.com/mcp/sse | Verified | 200 | |
| http (plaintext) | http://api.shopsavvy.com/mcp/sse | HTTPS enforced | 301 | https://api.shopsavvy.com/mcp/sse |
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 →
api_usage API key credit usage ~63
Show this month's Data API credit usage for the API key: credits used, monthly limit, credits remaining and request count. No credits used. Without a key there is no credit account; anonymous use is limited to 10 tool calls a minute and 100 an hour instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
content_best_picks Best-of buying guides ~160
Search ShopSavvy's published 'best of' buying guides (for example 'gaming laptop' or 'wireless earbuds') and return each guide's ranked picks with a short reason and a link to the full guide on shopsavvy.com. Use it for category research, then check current prices with product_offers. Free without an API key; with a key, 1 credit per guide returned (minimum 1). If no guide matches, say so; do not invent picks.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum articles to return (default: 5, max: 20) |
| query | string | yes | Search term or category (e.g., 'gaming laptop', 'wireless earbuds', 'smart tv', 'running shoes') |
No output schema declared.
No examples provided.
content_buying_guide When-to-buy guides ~172
When-to-buy guides for a product category or brand (for example 'Samsung TV', 'mattress' or 'Apple'): the months and sales events when prices usually drop, with a link to each guide on shopsavvy.com; set include_gift_guides for gift guides too. Pair it with product_price_history to answer 'buy now or wait?'. Free without an API key; with a key, 1 credit per guide returned (minimum 1). If no guide matches, say so; do not guess a sale date.
| Name | Type | Req | Description |
|---|---|---|---|
| include_gift_guides | boolean | – | Include gift guide articles in results (default: false) |
| query | string | yes | Product category or brand (e.g., 'Apple', 'Samsung TV', 'mattress', 'laptop') |
No output schema declared.
No examples provided.
content_qa_answers Product questions and answers ~158
Published answers to common questions about one product, optionally filtered by a question phrase, each with a link to the full answer on shopsavvy.com. Pass an identifier (barcode, ASIN, URL, name or ShopSavvy ID). Free without an API key; with a key, 1 credit per 5 answers returned (minimum 1). If nothing matches, say there is no published answer; do not make one up.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Product identifier (barcode, ASIN, URL, product name, or ShopSavvy ID) |
| limit | number | – | Maximum answers to return (default: 5, max: 20) |
| question | string | – | Optional: specific question to search for |
No output schema declared.
No examples provided.
content_tldr_review Quick product review ~153
Short review summary for one product from ShopSavvy's published TLDR reviews: an overall score out of 10 where available, pros, cons and a bottom-line verdict. Pass an identifier (barcode, ASIN, URL, name or ShopSavvy ID) or the product_path from an earlier result. Free without an API key; 1 credit with a key when a review exists. If no review exists for the product, say so; do not write one yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | – | Product identifier (barcode, ASIN, URL, product name, or ShopSavvy ID) |
| product_path | string | – | Direct product path if known (e.g., 'products/abc123') |
No output schema declared.
No examples provided.
product_lookup Look up a product ~189
Look up one product and return its ShopSavvy record: title, brand, model, MPN, barcode, Amazon ASIN and ShopSavvy ID (pass that ID to every follow-up tool), plus a link to its ShopSavvy page. Accepts a barcode (UPC/EAN/ISBN), ASIN, product URL, model number, ShopSavvy ID or a product name; barcodes, ASINs and URLs match most reliably, while a name can resolve to a different size or variant. Use product_search instead when you only have a keyword and want a list. Free without an API key; 1 credit with a key. If nothing is found, say that no data was found; do not guess.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Product identifier (barcode/UPC/EAN, ASIN, product URL, model number, product name, or ShopSavvy ID) |
No output schema declared.
No examples provided.
product_lookup_batch Look up several products ~124
Look up several products in one call from a comma-separated list of identifiers (barcodes, ASINs, URLs, model numbers or ShopSavvy IDs) and return the product_lookup fields for each one found. Use it when comparing two or more specific products. Free without an API key; 1 credit per product found with a key. Identifiers that match nothing are left out of the result: report those as not found rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| identifiers | string | yes | Comma-separated list of product identifiers (barcodes, ASINs, URLs, etc.) |
No output schema declared.
No examples provided.
product_offers Compare current prices ~220
Current prices for one product at every retailer ShopSavvy has an offer from, lowest price first: retailer, price, availability, condition, marketplace seller, when the offer was last checked, and a link; then any in-store shelf prices read from shoppers' receipts (store, address, receipt date; labeled user-collected, a price on that day, not current stock); followed by a source line naming ShopSavvy with the product page link (cite it when you quote prices). Online prices are in US dollars. Use product_offers_retailer for a single store and product_price_history for past prices; a barcode, ASIN or ShopSavvy ID gives the most reliable match. Free without an API key; 3 credits with a key, nothing when no offers or in-store prices are found. If no offers are returned, say no current prices were found; do not estimate a price.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Product identifier (barcode, ASIN, URL, model number, product name, or ShopSavvy ID) |
No output schema declared.
No examples provided.
product_offers_retailer Current prices at one retailer ~183
Current prices for one product at a single retailer, given as a domain such as amazon.com, bestbuy.com or target.com: each offer from that store (including marketplace sellers) with price, availability, condition, when it was last checked and a link, followed by a ShopSavvy source line. Prices are in US dollars. Use product_offers to compare every retailer at once. Free without an API key; 2 credits with a key, nothing when no offers are found. If that retailer has no offer, say so; do not substitute another store's price.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Product identifier (barcode, ASIN, URL, model number, product name, or ShopSavvy ID) |
| retailer | string | yes | Retailer domain name (e.g., 'amazon.com', 'bestbuy.com', 'target.com') |
No output schema declared.
No examples provided.
product_price_history Price history ~362
Recorded prices for one product between start_date and end_date (YYYY-MM-DD, both today or earlier), grouped by retailer, each point with its date, price and availability, followed by a ShopSavvy source line. Optionally pass a retailer domain to limit it to one store. Use it to judge whether today's price is a good deal or when a product was cheapest; use product_offers for current prices. History goes back to 2011 for some products and is dense from 2019; the window is capped, so request long periods in narrower slices if the server says the range is too wide. Free without an API key; with a key, 1 credit per day in the window plus 3 (2 with a retailer filter), nothing when no history is found. If no history is returned, say there is no recorded history for that window; do not infer one.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Alias for 'end_date' (the REST spelling). End date in YYYY-MM-DD format. |
| end_date | string | – | End date in YYYY-MM-DD format (e.g., '2024-01-31'). Alias: 'end' (the REST spelling) is also accepted. |
| identifier | string | yes | Product identifier (barcode, ASIN, URL, model number, product name, or ShopSavvy ID) |
| retailer | string | – | Optional: specific retailer domain name to filter results |
| start | string | – | Alias for 'start_date' (the REST spelling). Start date in YYYY-MM-DD format. |
| start_date | string | – | Start date in YYYY-MM-DD format (e.g., '2024-01-01'). Alias: 'start' (the REST spelling) is also accepted. |
No output schema declared.
No examples provided.
product_schedule Schedule price re-checks ~142
Schedule products (comma-separated identifiers) for automatic price re-checks hourly, daily or weekly, optionally at one retailer, so later product_offers and product_price_history calls return fresher prices. Requires a Data API key: schedules belong to the key's account (see scheduled_products_list). Scheduled re-checks run on that cadence for retailers ShopSavvy can re-check through an official retailer API; other retailers update as ShopSavvy sees them. 1 credit per product scheduled.
| Name | Type | Req | Description |
|---|---|---|---|
| identifiers | string | yes | Comma-separated list of product identifiers |
| retailer | string | – | Optional: specific retailer domain to monitor |
| schedule | string | yes | Monitoring frequency |
No output schema declared.
No examples provided.
product_search Search products ~189
Keyword search over the ShopSavvy catalog. Returns ranked products (title, brand, identifiers and ShopSavvy ID), best match first, paginated with limit (default 20, max 100) and offset. Use it when the user names a product type or partial name; use product_lookup for an exact barcode, ASIN or URL, and universal_search for broad 'best X' category questions where reviews help. Free without an API key; 1 credit per product returned with a key. If no products match, say so; do not invent products.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results to return (default: 20, max: 100) |
| offset | number | – | Offset for pagination (default: 0) |
| query | string | yes | Search query or keyword (e.g., 'iphone 15 pro', 'samsung tv', 'nike shoes') |
No output schema declared.
No examples provided.
product_unschedule Stop scheduled price re-checks ~55
Stop scheduled price re-checks for the given comma-separated identifiers on the API key's account. Requires a Data API key. No credits used.
| Name | Type | Req | Description |
|---|---|---|---|
| identifiers | string | yes | Comma-separated list of product identifiers to unschedule |
No output schema declared.
No examples provided.
scheduled_products_list List scheduled products ~54
List the products scheduled for automatic price re-checks on the API key's account, grouped by frequency, with ShopSavvy ID, barcode, ASIN and retailer filter. Requires a Data API key. No credits used.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
universal_search Ranked category search ~215
Category search with pre-computed rankings for broad queries such as 'gaming laptop', '85 inch tv' or 'air fryer': returns the top-ranked products with short review summaries and matching best-picks guides. Use it for open-ended 'what should I buy' questions; use product_search for a specific product name and product_lookup for an exact identifier, then product_offers for prices. Free without an API key; with a key, 2 credits plus 1 per product review and 1 per guide included. If nothing ranks for the query, say so; do not invent products.
| Name | Type | Req | Description |
|---|---|---|---|
| include_best_picks | boolean | – | Include matching best picks articles (default: true) |
| include_reviews | boolean | – | Include TLDR review summaries in results (default: true) |
| limit | number | – | Maximum products to return (default: 10, max: 50) |
| query | string | yes | Search query (e.g., 'gaming laptop', '85 inch tv', 'running shoes', 'air fryer') |
No output schema declared.
No examples provided.
How do I install the ShopSavvy MCP server?
ShopSavvy is a hosted endpoint at https://api.shopsavvy.com/mcp/sse, 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.shopsavvy.com
claude mcp add --transport http shopsavvy-shopsavvy-mcp-server 'https://api.shopsavvy.com/mcp/sse'
What is the ShopSavvy MCP server?
ShopSavvy is an MCP server listed in the public MCP registry as io.github.shopsavvy/shopsavvy-mcp-server. Product lookup, current prices across retailers, price history and buying guides. No key needed. This page covers its hosted endpoint (https://api.shopsavvy.com/mcp/sse).
Is the ShopSavvy MCP server safe to use?
ShopSavvy scores 60 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 ShopSavvy MCP server expose?
ShopSavvy exposes 15 tools: product_lookup, product_lookup_batch, product_search, product_offers, product_offers_retailer, and 10 more. Their descriptions and schemas cost roughly 2,439 tokens of context every time the server is loaded.
Does the ShopSavvy MCP server require authentication?
No. We connected to ShopSavvy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ShopSavvy MCP server still maintained?
ShopSavvy is still listed as active in the MCP registry. We last reached this channel on 22 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 ShopSavvy MCP server?
VerifyMCP ran 13 checks on ShopSavvy, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.