Aimé Leon Dore catalogue search, products and prices.
within · luxury boutiques is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Live stock at independent luxury boutiques: pieces, sizes, prices and the page to buy each one.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http within-luxury-boutiques-mcp https://shopwithin.co/mcp
# 2 — ask your agent for something these tools do
# search_pieces, get_piece, trending_now and 6 more
within · luxury boutiques costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http within-luxury-boutiques-mcp https://shopwithin.co/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What the shopper wants, in plain words: 'black leather loafers', 'Lemaire', 'a birthday gift for my dad under $300'. |
| brands | array | no | Designer or house names to restrict to, exactly as they appear in results. |
| categories | array | no | Product types to restrict to, e.g. 'Sneakers', 'Bags'; take values from a previous result's facets. |
| sizes | array | no | Sizes that must be in stock, as labelled on the shelf: 'M', '42', 'US 9', 'IT 38'. |
| boutiques | array | no | Boutique domains to restrict to, as shown on boutiques and pieces (e.g. 'wdlt117.myshopify.com'). |
| city | string | no | Only boutiques in this city, e.g. 'Toronto'. If within has no boutiques there yet, the answer says so and names the live cities. |
| price_min | number | no | Lowest price to include, in the boutique's currency. |
| price_max | number | no | Highest price to include, in the boutique's currency. |
| sort | string | no | — |
| lens | string | no | 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 | no | Pieces per page, default 12. |
| offset | integer | no | Pieces to skip; use next_offset from the previous page. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | A shopwithin.co piece link, e.g. https://shopwithin.co/product/<boutique>/<id>. |
| boutique_domain | string | no | The piece's boutique_domain from a previous result. |
| id | string | no | The piece's id from a previous result. |
within's chart of the designer pieces trending at independent boutiques this week, updated daily: the first 20 places 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 luxu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dept | string | no | The women's or the men's chart; leave out for everyone's. |
| kind | string | no | One kind of piece, e.g. 'sneakers', 'bags', 'jackets', 'boots', 'jewelry', 'dresses'. |
| limit | integer | no | How many places to return, default 10. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | A shopwithin.co piece link. |
| boutique_domain | string | no | — |
| id | string | no | — |
| limit | integer | no | Default 8. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | no | Only boutiques in this city, e.g. 'Toronto'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| boutique_domain | string | yes | The boutique's domain, as shown on boutiques and pieces (e.g. 'utopia-kicks.myshopify.com'). |
| query | string | no | Search inside this boutique only. |
| limit | integer | no | Default 12. |
| offset | integer | no | — |
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 me
| Parameter | Type | Required | Notes |
|---|---|---|---|
| image_url | string | no | A direct, publicly reachable JPEG, PNG or WebP URL (under 1.5 MB). |
| image_base64 | string | no | The image bytes, base64 encoded (under 1.5 MB decoded). |
| media_type | string | no | Required with image_base64. |
| post_url | string | no | A TikTok or Pinterest post link; the photograph is read from the post. |
| image_file | object | no | A photograph the shopper uploaded in the chat; the host passes the file here. |
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 cou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | What is being sized: rings, shoes, clothing, suits, belts or hats. |
| designer | string | no | A designer's slug, as in shopwithin.co/designers/<slug>, to read that designer's own charts instead of a kind. |
| from | string | no | The system the size is written in, as a key this tool lists, e.g. 'us', 'uk', 'eu'. |
| size | string | no | The size as printed, e.g. '7', 'N 1/2', '42', 'M'. |
| to | string | no | Optional: one system key to lead the answer with. |
| department | string | no | Optional: only women's or men's tables. |
| table | string | no | Optional: one table or chart id this tool lists. |
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-
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | string | yes | Where the piece is shipped to. |
| price | number | yes | The price, without shipping. |
| currency | string | yes | The currency of the price. |
| kind | string | yes | 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-woo |
| department | string | no | Women's or men's; some duty rates differ. |
| made_in | string | yes | Two letter country code of where it was made, e.g. IT, FR, CA, US, JP. |
| ships_from | string | yes | Two letter country code of where it ships from. |
| ship_by | string | no | us: fedex, courier or post. canada: fedex, courier or post. uk: royalmail, parcelforce or courier. australia: courier or post. |
| region | string | no | Canada only: the province code, e.g. ON, QC, BC. |
| shipping | number | no | Optional shipping cost, in the price's currency. |
| weight_kg | number | no | Optional weight; a few US lines add a charge per kilogram. |
| usmca | boolean | no | US only: true if a piece made in Canada or Mexico qualifies under USMCA. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install within · luxury boutiques or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_pieces | no tags | |
| get_piece | no tags | |
| trending_now | no tags | |
| similar_pieces | no tags | |
| list_boutiques | no tags | |
| boutique_shelf | untrusted-input | untrusted-input: keyword "browse" |
| visual_search | no tags | |
| convert_size | no tags | |
| estimate_duty | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish within · luxury boutiques can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.