# within · luxury boutiques (remote · shopwithin.co)

Live stock at independent luxury boutiques: pieces, sizes, prices and the page to buy each one.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `shopwithin.co`: 74/100 (this document), [markdown](https://verifymcp.io/servers/co-shopwithin-within/shopwithin.md), [page](https://verifymcp.io/servers/co-shopwithin-within/shopwithin)

## Channel facts

- Endpoint: `https://shopwithin.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-10-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2717 tokens (~226/item across 12 items; 9 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the within · luxury boutiques MCP server?

within · luxury boutiques is a hosted endpoint at https://shopwithin.co/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.

### Claude

```bash
claude mcp add --transport http co-shopwithin-within 'https://shopwithin.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-shopwithin-within": {
      "url": "https://shopwithin.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-shopwithin-within": {
      "type": "http",
      "url": "https://shopwithin.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-shopwithin-within]
url = "https://shopwithin.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-shopwithin-within": {
      "type": "remote",
      "url": "https://shopwithin.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-shopwithin-within --url 'https://shopwithin.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-shopwithin-within:
    url: "https://shopwithin.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-shopwithin-within": {
      "Transport": "http",
      "Url": "https://shopwithin.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-shopwithin-within -t streamable-http -u 'https://shopwithin.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-shopwithin-within": {
      "type": "http",
      "url": "https://shopwithin.co/mcp"
    }
  }
}
```

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-10-24 (score 74, 0)

- [security] Tool “trending_now” rewrote its description, which is the text the model reads
- [cosmetic] “trending_now” reworded the description of “limit”

### 2026-10-23 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 73)

First indexed and scored.

## MCP tools (9)

### `search_pieces` (~481 tokens)

Search the boutiques' shelves

Search pieces (clothing, shoes, bags, jewellery, watches, objects) in stock right now at independent luxury boutiques, with live sizes, price in the boutique's currency, the shop that holds each piece, and the shopwithin.co page to buy it. Use this when someone wants to find or compare a kind of piece, a designer's pieces at boutiques, a gift, or what is in stock in a city. A plain sentence works as the query (prices like 'under $400' and 'cheapest' are understood); brands, categories, sizes, boutiques, or city narrow it. With no arguments it returns the current front shelf; lens browses new arrivals, most saved, or marked down. Do not use for general style advice or for mass market retailers.

Input parameters:

- `boutiques` (array): Boutique domains to restrict to, as shown on boutiques and pieces (e.g. 'wdlt117.myshopify.com').
- `brands` (array): Designer or house names to restrict to, exactly as they appear in results.
- `categories` (array): Product types to restrict to, e.g. 'Sneakers', 'Bags'; take values from a previous result's facets.
- `city` (string): Only boutiques in this city, e.g. 'Toronto'. If within has no boutiques there yet, the answer says so and names the live cities.
- `lens` (string): Browse a shelf instead of searching: 'new' = just arrived, 'trending' = what people are saving, 'sale' = marked down. Ignored when a query or filters are given.
- `limit` (integer): Pieces per page, default 12.
- `offset` (integer): Pieces to skip; use next_offset from the previous page.
- `price_max` (number): Highest price to include, in the boutique's currency.
- `price_min` (number): Lowest price to include, in the boutique's currency.
- `query` (string): What the shopper wants, in plain words: 'black leather loafers', 'Lemaire', 'a birthday gift for my dad under $300'.
- `sizes` (array): Sizes that must be in stock, as labelled on the shelf: 'M', '42', 'US 9', 'IT 38'.
- `sort` (string)

Output parameters:

- `facets`
- `next_offset`
- `note`
- `pieces` (array)
- `related_searches` (array)
- `total`
- `total_is_floor` (boolean)
- `view_url` (string)

### `get_piece` (~170 tokens)

Read one piece

One piece in full: description, every size or variant with live stock, photographs, price and any markdown, whether it is collected in the shop or delivered, the boutique, the page to buy it, and a few pieces in the same vein. Use this when a shopper asks about a specific piece from a result, pastes a shopwithin.co link, or wants to know whether a size is in stock before buying. Identify the piece by url, or by boutique_domain and id from a previous result.

Input parameters:

- `boutique_domain` (string): The piece's boutique_domain from a previous result.
- `id` (string): The piece's id from a previous result.
- `url` (string): A shopwithin.co piece link, e.g. https://shopwithin.co/product/<boutique>/<id>.

Output parameters:

- `found` (boolean)
- `piece`
- `similar` (array)

### `trending_now` (~233 tokens)

What is trending this week

within's chart of the designer pieces trending at independent boutiques this week, updated daily: the top ten in order, each with its reason (Google searches, Pinterest searches, what boutiques worldwide are stocking, what people look at on within), its place last week and its weeks on the list, plus the designers of the week. Use this when someone asks what is trending in designer or luxury fashion right now, which designers or pieces are hot this week, or what is trending in a kind of piece (sneakers, bags, jackets, boots, jewelry…). dept narrows to women or men; kind to one kind of piece. Each piece has a url to buy it. Do not use for mass market retailers or for last year's trends.

Input parameters:

- `dept` (string): The women's or the men's chart; leave out for everyone's.
- `kind` (string): One kind of piece, e.g. 'sneakers', 'bags', 'jackets', 'boots', 'jewelry', 'dresses'.
- `limit` (integer): How many places to return, up to ten, default 10.

Output parameters:

- `as_of`
- `designers` (array)
- `items` (array)
- `json` (string)
- `kinds` (array)
- `past_weeks` (array)
- `title` (string)
- `url` (string)
- `week`

### `similar_pieces` (~103 tokens)

Pieces in the same vein

Pieces in the same vein as one piece: same spirit, same department, across every boutique, in stock now. Use this when a shopper likes a piece but wants alternatives, another price, or another shop. Identify the anchor piece by url, or by boutique_domain and id.

Input parameters:

- `boutique_domain` (string)
- `id` (string)
- `limit` (integer): Default 8.
- `url` (string): A shopwithin.co piece link.

Output parameters:

- `anchor`
- `pieces` (array)

### `list_boutiques` (~100 tokens)

The boutiques on within

The independent luxury boutiques listed on within, with neighbourhood, city, how many pieces each has live, opening hours, and whether a shopper collects in the shop or can have pieces delivered. Use this when someone asks which shops are on within, what is in a city or neighbourhood, or where to visit in person. The returned domain identifies a boutique everywhere else.

Input parameters:

- `city` (string): Only boutiques in this city, e.g. 'Toronto'.

Output parameters:

- `boutiques` (array)
- `cities` (array)

### `boutique_shelf` (~141 tokens)

One boutique's shelf

One boutique's shelf right now, newest first, with sizes and prices; a query searches inside that shop only. Use this when a shopper names a specific boutique ('what does WDLT117 have', 'show me Utopia's sneakers') or wants to browse a shop they read about. boutique_domain is the domain shown on any boutique or piece.

Input parameters:

- `boutique_domain` (string, required): The boutique's domain, as shown on boutiques and pieces (e.g. 'utopia-kicks.myshopify.com').
- `limit` (integer): Default 12.
- `offset` (integer)
- `query` (string): Search inside this boutique only.

Output parameters:

- `boutique`
- `next_offset`
- `pieces` (array)
- `view_url` (string)

### `visual_search` (~252 tokens)

Find it from a photograph

Pieces on the boutiques' shelves that resemble a photograph: a screenshot, a street style shot, a product photo, or a TikTok or Pinterest link. Answers in two tiers: pieces close enough to be the same or a near twin, and pieces in the same spirit. Use this when a shopper shares an image of something they want to find or 'something like this'. Pass image_url for a direct image, image_base64 with media_type for an uploaded file, or post_url for a TikTok or Pinterest link. Photographs are matched in memory and never stored. Do not use for Instagram links; they cannot be read, so ask for a screenshot instead.

Input parameters:

- `image_base64` (string): The image bytes, base64 encoded (under 1.5 MB decoded).
- `image_file` (object): A photograph the shopper uploaded in the chat; the host passes the file here.
- `image_url` (string): A direct, publicly reachable JPEG, PNG or WebP URL (under 1.5 MB).
- `media_type` (string): Required with image_base64.
- `post_url` (string): A TikTok or Pinterest post link; the photograph is read from the post.

Output parameters:

- `close` (array)
- `in_spirit` (array)
- `note`

### `convert_size` (~304 tokens)

Convert a size

Turn a size in one system into every other system: rings, shoes, clothing, suits, belts and hats, or one designer's own chart (pass designer as its slug, e.g. 'nike'). Answers only from the size tables on shopwithin.co/sizes, where every row comes from a named source with the day it was read, and returns the page that shows the answer. Use this when a shopper asks what their size is in another country's system, which size to take in a designer, or how a designer's sizes run. Call it without from and size to list the systems and tables a kind or a designer has.

Input parameters:

- `department` (string): Optional: only women's or men's tables.
- `designer` (string): A designer's slug, as in shopwithin.co/designers/<slug>, to read that designer's own charts instead of a kind.
- `from` (string): The system the size is written in, as a key this tool lists, e.g. 'us', 'uk', 'eu'.
- `kind` (string): What is being sized: rings, shoes, clothing, suits, belts or hats.
- `size` (string): The size as printed, e.g. '7', 'N 1/2', '42', 'M'.
- `table` (string): Optional: one table or chart id this tool lists.
- `to` (string): Optional: one system key to lead the answer with.

Output parameters:

- `designers` (array)
- `kinds` (array)
- `matches` (array)
- `note`
- `page_url` (string)
- `scope`
- `size_page_url`
- `sources` (array)
- `status` (string)
- `systems` (array)
- `tables` (array)

### `estimate_duty` (~582 tokens)

Estimate import duty

Work out what a piece of clothing, a pair of shoes, a bag, jewellery, a watch or an accessory costs at the door when it is shipped to the US, Canada, the UK or Australia: the duty, any extra tariff on the country it was made in, the tax, the government and carrier fees, and the total. Every line names its official source and the day it was read, and the answer links the page on shopwithin.co/duty-calculator that shows it. Use this when a shopper asks about customs, duty, tariffs or import tax on a cross-border order. It is an estimate; the carrier's bill is the final word.

Input parameters:

- `currency` (string, required): The currency of the price.
- `department` (string): Women's or men's; some duty rates differ.
- `kind` (string, required): What the piece is, one of: coat-wool, coat-cotton, coat-polyester, puffer-down, jacket-wool, jacket-cotton, jacket-polyester, jacket-leather, blazer-wool, blazer-cotton, blazer-polyester, trousers-wo…
- `made_in` (string, required): Two letter country code of where it was made, e.g. IT, FR, CA, US, JP.
- `price` (number, required): The price, without shipping.
- `region` (string): Canada only: the province code, e.g. ON, QC, BC.
- `ship_by` (string): us: fedex, courier or post. canada: fedex, courier or post. uk: royalmail, parcelforce or courier. australia: courier or post.
- `shipping` (number): Optional shipping cost, in the price's currency.
- `ships_from` (string, required): Two letter country code of where it ships from.
- `to` (string, required): Where the piece is shipped to.
- `usmca` (boolean): US only: true if a piece made in Canada or Mexico qualifies under USMCA.
- `weight_kg` (number): Optional weight; a few US lines add a charge per kilogram.

Output parameters:

- `currency` (string)
- `estimate_note` (string)
- `exchange_rate_date`
- `found` (boolean)
- `lines` (array)
- `note`
- `notes`
- `owed_before_delivery`
- `page` (string)
- `status` (string)
- `tax_at_checkout`
- `to` (string)
- `total`
- `value` (number)
- `what_changes_it`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-shopwithin-within/shopwithin#diagnostics

## Score history

- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73

## Common questions

### What is the within · luxury boutiques MCP server?

within · luxury boutiques is an MCP server listed in the public MCP registry as co.shopwithin/within. Live stock at independent luxury boutiques: pieces, sizes, prices and the page to buy each one. This page covers its hosted endpoint (https://shopwithin.co/mcp).

### Is the within · luxury boutiques MCP server safe to use?

within · luxury boutiques scores 74 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 within · luxury boutiques MCP server expose?

within · luxury boutiques exposes 9 tools: search_pieces, get_piece, trending_now, similar_pieces, list_boutiques, and 4 more. Their descriptions and schemas cost roughly 2,366 tokens of context every time the server is loaded.

### Does the within · luxury boutiques MCP server require authentication?

No. We connected to within · luxury boutiques without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the within · luxury boutiques MCP server still maintained?

within · luxury boutiques is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://shopwithin.co/mcp
- Website: https://shopwithin.co/agents
- Changelog RSS feed: https://verifymcp.io/servers/co-shopwithin-within/shopwithin.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-shopwithin-within/shopwithin.json
- HTML version of this page: https://verifymcp.io/servers/co-shopwithin-within/shopwithin