Vitrine: Trending Fashion, Luxury, Sneakers & Design MCP Server

Find alternatives to one item (by id from an earlier result): pieces close in style, the same product type first. Use it for 'something like this but cheaper' (filters.max_price), 'but in stock' (filters.availability) or a different color. The source item is never included. Returns {anchor, count, results} in the search result shape, each with a 'why' naming the shared style. An unknown id returns an error result; an empty list means no alternative passes the filters. Read-only. Without a key, results are capped at 5 and omit trend data and match reasons; a free key (POST https://vitrine.fashion/v1/keys, sent as 'Authorization: Bearer <key>') unlocks them. Rate limits: 10 calls a minute anonymous, 60 with a key.

Brands close to a given brand (exact name, e.g. 'The Row'): similar style tags, categories, price level and catalog tier, each with a short reason. Optionally only brands with pieces in a category or tier. Unknown brand names return an error; find names with search_brands.

List what is hot or rising right now, ranked by trend score (0 to 100), optionally within one category (fashion, accessories, interior), tier or gender (men and women include unisex pieces). Use it for open questions like 'what's trending in bags' or 'in menswear'; use search when the shopper has a specific need. 'hot' means confirmed by demand data, 'rising' means early momentum not yet confirmed. Returns 5 to 20 items in the same shape as search, plus meta.updated_at. Read-only. Without a key, results are capped at 5 and omit trend data and match reasons; a free key (POST https://vitrine.fashion/v1/keys, sent as 'Authorization: Bearer <key>') unlocks them. Rate limits: 10 calls a minute anonymous, 60 with a key. With a key, each item also carries trend_reason (why it has its trend status), trend_sources (the signals behind it: source, url, signal type, date, contribution; [] when the status comes from curation alone) and trend_review (when the status last changed and whether a human reviewer approved it).

Hot and rising brands right now, ranked by brand trend status and score, optionally within a category or tier. Uses Vitrine's reviewed brand-level trend signals where a brand has them, otherwise aggregates its item trend scores; each result's trend_source says which (brand_signal or item_aggregate).

Find brands in the index by name (case and accents ignored, partial names work) or by a style word such as 'y2k' or 'quiet luxury', optionally within a category or catalog tier. Returns brands with item count, main tier, categories, price range and, with a key, trend status, trend score and top style tags. An empty query lists brands with the most items first.

Build around one item (by id from an earlier result). For fashion it returns one piece per missing slot of an outfit (layer, top, bottom, shoes, bag, accessory; a dress skips top and bottom); for an interior piece it returns the other objects of a room (lamp, vase, table, textiles). Pieces are chosen for shared style, color harmony, shared occasion, season and a similar price tier, and never from the item's own slot. Use it for 'what goes with this', 'style this' or 'finish the room'; use find_similar for alternatives to the item itself. Filters apply to every added piece (for example max_price per piece, size or ship_to). Returns {anchor, kind, count, pieces}, each piece with a slot label and, with a key, a 'why'. An unknown id returns an error result. Read-only. Without a key, results are capped at 5 and omit trend data and match reasons; a free key (POST https://vitrine.fashion/v1/keys, sent as 'Authorization: Bearer <key>') unlocks them. Rate limits: 10 calls a minute anonymous, 60 with a key.

Convert a size between systems so the shopper orders the right one: women's clothing (letter, US, UK, EU, FR, IT, DE), men's tailoring (letter, US, UK, EU, IT), women's and men's shoes (EU, US, UK, European luxury convention), athletic sneakers (US_M, US_W, UK, EU, CM), rings (US, UK, EU, millimetres) and jeans waist. Use it whenever the shopper's size and the item's sizes are in different systems, before recommending a size. Returns every equivalent, a note on the convention used, and 'approximate' or 'ambiguous' when the size is between or spans rows. The brand's own chart always wins. No key needed; read-only.

Get the full record for one item, using an id from a search, trending or find_similar result. Use it before recommending a piece, to check sizes, materials, colors, shipping regions and seller. With a key it adds silhouette, occasion, season and trend data. Returns {item, meta}. An unknown id returns an error result telling you to search again. Read-only. Without a key, results are capped at 5 and omit trend data and match reasons; a free key (POST https://vitrine.fashion/v1/keys, sent as 'Authorization: Bearer <key>') unlocks them. Rate limits: 10 calls a minute anonymous, 60 with a key. With a key, each item also carries trend_reason (why it has its trend status), trend_sources (the signals behind it: source, url, signal type, date, contribution; [] when the status comes from curation alone) and trend_review (when the status last changed and whether a human reviewer approved it).

Find fashion, accessories or interior pieces for a shopper's request. Use this first for any need stated in words ('a quiet luxury bag for work under $1,000'); use trending when there is no specific need, and find_similar to vary an item you already have. Hard filters (category, gender, tier, price, colors, size, brand, availability, ship_to) exclude items outright; filters.gender 'men' or 'women' also keeps unisex pieces unless gender_exact is true. Words like "men's" or "for her" in the query only rerank, like the optional taste_profile. Returns up to 20 items ranked by text match, taste and trend, each with price, availability, image, trend status, a one-line 'why' and an outbound_url to the retailer, where checkout happens. No pagination; an empty list means nothing fits, so loosen filters. Read-only. Without a key, results are capped at 5 and omit trend data and match reasons; a free key (POST https://vitrine.fashion/v1/keys, sent as 'Authorization: Bearer <key>') unlocks them. Rate limits: 10 calls a minute anonymous, 60 with a key. With a key, each item also carries trend_reason (why it has its trend status), trend_sources (the signals behind it: source, url, signal type, date, contribution; [] when the status comes from curation alone) and trend_review (when the status last changed and whether a human reviewer approved it).

Shop a photo: an outfit picture, a street-style shot, a screenshot or a room. Look at the image yourself and send the pieces you see as `pieces` (description such as 'oversized camel wool coat', plus subcategory, colors, materials, style_tags and gender when clear). Vitrine returns the closest pieces it indexes for each one, matched on type, color, material and style, with price, stock and a link. Send image_url or image_base64 only if you cannot see the image; that path may be unavailable. Never describe people, only what they wear or what is in the room. Filters apply to every match (max_price per piece, size, ship_to). Returns {source, count, pieces: [{seen, matches}]}; then call complete_the_look on a match to finish the outfit. Read-only. Without a key, results are capped at 5 and omit trend data and match reasons; a free key (POST https://vitrine.fashion/v1/keys, sent as 'Authorization: Bearer <key>') unlocks them. Rate limits: 10 calls a minute anonymous, 60 with a key.

The exact controlled values agents should use in filters and taste profiles, read from the live catalog with item counts: categories, catalog tiers, price tiers with their price bands, availability, trend statuses with meanings, style tags, silhouettes, occasions, seasons, colors, materials, sizes, conditions and ship-to regions, plus every filter field name with its type. No arguments. Cacheable: call it once per session, before building filters.