# ShopSavvy (remote · api.shopsavvy.com)

Product lookup, current prices across retailers, price history and buying guides. No key needed.

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `api.shopsavvy.com`: 66/100, [markdown](https://verifymcp.io/servers/shopsavvy-shopsavvy-mcp-server/api.md), [page](https://verifymcp.io/servers/shopsavvy-shopsavvy-mcp-server/api)
- remote · `api.shopsavvy.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/shopsavvy-shopsavvy-mcp-server/api-2.md), [page](https://verifymcp.io/servers/shopsavvy-shopsavvy-mcp-server/api-2)

## Channel facts

- Endpoint: `https://api.shopsavvy.com/mcp/sse`
- Transports: `sse`
- Auth: `none`
- Version: `2.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (product_schedule).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 40/100
  - Verified sse transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http shopsavvy-shopsavvy-mcp-server 'https://api.shopsavvy.com/mcp/sse'
```

### Cursor

```json
{
  "mcpServers": {
    "shopsavvy-shopsavvy-mcp-server": {
      "url": "https://api.shopsavvy.com/mcp/sse"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shopsavvy-shopsavvy-mcp-server": {
      "type": "http",
      "url": "https://api.shopsavvy.com/mcp/sse"
    }
  }
}
```

### Codex

```toml
[mcp_servers.shopsavvy-shopsavvy-mcp-server]
url = "https://api.shopsavvy.com/mcp/sse"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shopsavvy-shopsavvy-mcp-server": {
      "type": "remote",
      "url": "https://api.shopsavvy.com/mcp/sse",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shopsavvy-shopsavvy-mcp-server --url 'https://api.shopsavvy.com/mcp/sse' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  shopsavvy-shopsavvy-mcp-server:
    url: "https://api.shopsavvy.com/mcp/sse"
```

### Netclaw

```json
{
  "McpServers": {
    "shopsavvy-shopsavvy-mcp-server": {
      "Transport": "http",
      "Url": "https://api.shopsavvy.com/mcp/sse"
    }
  }
}
```

### Vellum

```bash
assistant mcp add shopsavvy-shopsavvy-mcp-server -t streamable-http -u 'https://api.shopsavvy.com/mcp/sse'
```

### Other

```json
{
  "mcpServers": {
    "shopsavvy-shopsavvy-mcp-server": {
      "type": "http",
      "url": "https://api.shopsavvy.com/mcp/sse"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 60, +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.

### 2026-11-21 (score 59, +2)

- [security improvement] HSTS header: fail → pass

### 2026-11-20 (score 57, +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.

### 2026-11-18 (score 56, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 55)

First indexed and scored.

## MCP tools (15)

### `product_lookup` (~189 tokens)

Look up a product

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.

Input parameters:

- `identifier` (string, required): Product identifier (barcode/UPC/EAN, ASIN, product URL, model number, product name, or ShopSavvy ID)

### `product_lookup_batch` (~124 tokens)

Look up several products

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.

Input parameters:

- `identifiers` (string, required): Comma-separated list of product identifiers (barcodes, ASINs, URLs, etc.)

### `product_search` (~189 tokens)

Search products

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.

Input parameters:

- `limit` (number): Maximum number of results to return (default: 20, max: 100)
- `offset` (number): Offset for pagination (default: 0)
- `query` (string, required): Search query or keyword (e.g., 'iphone 15 pro', 'samsung tv', 'nike shoes')

### `product_offers` (~220 tokens)

Compare current prices

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.

Input parameters:

- `identifier` (string, required): Product identifier (barcode, ASIN, URL, model number, product name, or ShopSavvy ID)

### `product_offers_retailer` (~183 tokens)

Current prices at one retailer

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.

Input parameters:

- `identifier` (string, required): Product identifier (barcode, ASIN, URL, model number, product name, or ShopSavvy ID)
- `retailer` (string, required): Retailer domain name (e.g., 'amazon.com', 'bestbuy.com', 'target.com')

### `product_price_history` (~362 tokens)

Price history

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.

Input parameters:

- `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, required): 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.

### `product_schedule` (~142 tokens)

Schedule price re-checks

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.

Input parameters:

- `identifiers` (string, required): Comma-separated list of product identifiers
- `retailer` (string): Optional: specific retailer domain to monitor
- `schedule` (string, required): Monitoring frequency

### `product_unschedule` (~55 tokens)

Stop scheduled price re-checks

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.

Input parameters:

- `identifiers` (string, required): Comma-separated list of product identifiers to unschedule

### `scheduled_products_list` (~54 tokens)

List scheduled products

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.

### `api_usage` (~63 tokens)

API key credit usage

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.

### `content_best_picks` (~160 tokens)

Best-of buying guides

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.

Input parameters:

- `limit` (number): Maximum articles to return (default: 5, max: 20)
- `query` (string, required): Search term or category (e.g., 'gaming laptop', 'wireless earbuds', 'smart tv', 'running shoes')

### `content_tldr_review` (~153 tokens)

Quick product review

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.

Input parameters:

- `identifier` (string): Product identifier (barcode, ASIN, URL, product name, or ShopSavvy ID)
- `product_path` (string): Direct product path if known (e.g., 'products/abc123')

### `content_qa_answers` (~158 tokens)

Product questions and answers

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.

Input parameters:

- `identifier` (string, required): 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

### `content_buying_guide` (~172 tokens)

When-to-buy guides

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.

Input parameters:

- `include_gift_guides` (boolean): Include gift guide articles in results (default: false)
- `query` (string, required): Product category or brand (e.g., 'Apple', 'Samsung TV', 'mattress', 'laptop')

### `universal_search` (~215 tokens)

Ranked category search

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.

Input parameters:

- `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, required): Search query (e.g., 'gaming laptop', '85 inch tv', 'running shoes', 'air fryer')

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/shopsavvy-shopsavvy-mcp-server/api-2#diagnostics

## Score history

- 2026-11-22: 60
- 2026-11-21: 59
- 2026-11-20: 57
- 2026-11-19: 56
- 2026-11-18: 56
- 2026-11-17: 55

## Common questions

### 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.

## Links

- Remote endpoint: https://api.shopsavvy.com/mcp/sse
- Repository: https://github.com/shopsavvy/shopsavvy-mcp-server
- Website: https://shopsavvy.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/shopsavvy-shopsavvy-mcp-server/api-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/shopsavvy-shopsavvy-mcp-server/api-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/shopsavvy-shopsavvy-mcp-server/api-2.json
- HTML version of this page: https://verifymcp.io/servers/shopsavvy-shopsavvy-mcp-server/api-2
