GlanceAI Fashion MCP
REMOTE · GLANCE.COM · SCANNED OCT 5
Fashion product discovery and virtual try-on via the Glance catalog
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the GlanceAI Fashion MCP server?
GlanceAI Fashion MCP is a hosted endpoint at https://glance.com/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.
remote · glance.com
claude mcp add --transport http com-glance-glanceai-fashion 'https://glance.com/mcp'
{
"mcpServers": {
"com-glance-glanceai-fashion": {
"url": "https://glance.com/mcp"
}
}
} {
"servers": {
"com-glance-glanceai-fashion": {
"type": "http",
"url": "https://glance.com/mcp"
}
}
} [mcp_servers.com-glance-glanceai-fashion] url = "https://glance.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-glance-glanceai-fashion": {
"type": "remote",
"url": "https://glance.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-glance-glanceai-fashion --url 'https://glance.com/mcp' --transport streamable-http
mcp_servers:
com-glance-glanceai-fashion:
url: "https://glance.com/mcp" {
"McpServers": {
"com-glance-glanceai-fashion": {
"Transport": "http",
"Url": "https://glance.com/mcp"
}
}
} assistant mcp add com-glance-glanceai-fashion -t streamable-http -u 'https://glance.com/mcp'
{
"mcpServers": {
"com-glance-glanceai-fashion": {
"type": "http",
"url": "https://glance.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 23 Sept 26 0
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 22 Sept 26 0
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 28 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 27 Aug 26 0
- A breaking change shipped without a version bump: still 0.2.0 ▼ security
- Tool “search_fashion_products” rewrote its description, which is the text the model reads security
- Tool “try_on_product” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “get_mix_and_match” made “anchor_sku” required, so existing callers break ▼ functional
- “get_mix_and_match” made “context_image_ref” required, so existing callers break ▼ functional
- “get_mix_and_match” made “gender” required, so existing callers break ▼ functional
- “get_mix_and_match” made “query” required, so existing callers break ▼ functional
- “search_fashion_products” made “context_image_ref” required, so existing callers break ▼ functional
- “search_fashion_products” made “query” required, so existing callers break ▼ functional
- “try_on_product” made “collection_name” required, so existing callers break ▼ functional
- “try_on_product” made “sku” required, so existing callers break ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: good → excellent functional
- “get_mix_and_match” reworded the description of “anchor_sku” cosmetic
- “get_mix_and_match” reworded the description of “caption” cosmetic
- “get_mix_and_match” reworded the description of “context_image_ref” cosmetic
- “get_mix_and_match” reworded the description of “country” cosmetic
- “get_mix_and_match” reworded the description of “gender” cosmetic
- “get_mix_and_match” reworded the description of “max_price” cosmetic
- “get_mix_and_match” reworded the description of “occasion” cosmetic
- “get_mix_and_match” reworded the description of “query” cosmetic
- “get_mix_and_match” reworded the description of “tenant_id” cosmetic
- “get_product_details” reworded the description of “country” cosmetic
- “get_product_details” reworded the description of “sku” cosmetic
- “get_user_looks” reworded the description of “limit” cosmetic
- “get_user_looks” reworded the description of “offset” cosmetic
- “search_fashion_products” reworded the description of “brand” cosmetic
- “search_fashion_products” reworded the description of “context_image_ref” cosmetic
- “search_fashion_products” reworded the description of “context_summary” cosmetic
- “search_fashion_products” reworded the description of “country” cosmetic
- “search_fashion_products” reworded the description of “currency” cosmetic
- “search_fashion_products” reworded the description of “gender” cosmetic
- “search_fashion_products” reworded the description of “header” cosmetic
- “search_fashion_products” reworded the description of “max_price” cosmetic
- “search_fashion_products” reworded the description of “min_price” cosmetic
- “search_fashion_products” reworded the description of “occasion” cosmetic
- “search_fashion_products” reworded the description of “query” cosmetic
- “try_on_product” reworded the description of “collection_name” cosmetic
- “try_on_product” reworded the description of “country” cosmetic
- “try_on_product” reworded the description of “sku” cosmetic
- “get_mix_and_match” dropped the optional parameter “region” cosmetic
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 6 Oct 2026 · Probed https://glance.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=glance.com,O=Glance Digital Experience Pvt Ltd,ST=Karnataka,C=IN | CN=Sectigo Public Server Authentication CA OV R36,O=Sectigo Limited,C=GB | 5 Jun 2026 | 20 Dec 2026 | RSA 2048 | SHA256-RSA | 5cdf9ea8f64e67ab6a75e785a846f258 |
| SANs: glance.com, www.glance.com | ||||||
| CN=Sectigo Public Server Authentication CA OV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 2c1a3c76e943ddddff191b31890aed71 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of glance.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| glance.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://ember.ailooks.glance.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://ember.ailooks.glance.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://ember.ailooks.glance.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://ember.ailooks.glance.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Problem | metadata_resource_mismatch |
| Resource | https://ember.ailooks.glance.com/mcp |
| Authorisation server | https://ember.ailooks.glance.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://glance.com/mcp | Auth required | 401 | |
| http (plaintext) | http://glance.com/mcp | HTTPS enforced | 301 | https://glance.com:443/mcp |
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 →
get_mix_and_match Get Mix and Match ~817
Build a complete, multi-item Mix & Match outfit widget — several coordinated looks, each with multiple garments styled together. Use this when the shopper wants a full outfit or styling help, NOT a specific named item. Three modes: • ANCHOR mode (anchor_sku): build outfits around one specific catalog product the shopper already has/likes. • QUERY mode (query): design complete outfits from an open-ended styling request with no anchor product — every item in every look is found via catalog search. • IMAGE mode (context_image_ref): style outfits around an uploaded image. Call request_context_image first to get a ref_id, then pass it here. If query and anchor_sku are both provided, query mode takes precedence. At least one of anchor_sku, query, or context_image_ref must be supplied. DO NOT USE for a search where the shopper names a specific item/category with no styling ask (e.g. "red shoes", "blue dress", "men's oxford shoes") — that is a plain search, not an outfit request, even if a color/occasion/price filter is attached. Examples: - "give me an outfit for a wedding" (no item named) → query mode: { query: "outfit for a wedding" } - "style me for a beach day" → query mode: { query: "beach day outfit" } - "what goes with my blue jeans" (jeans is a specific catalog SKU already shown) → anchor mode: { anchor_sku: "<jeans SKU>" } - "complete this look" (after showing/selecting a product) → anchor mode with that SKU - (after an uploaded photo) "build an outfit around this" → image mode: { context_image_ref: "<ref>" } - "red shoes" or "blue dress under 1000" → NOT this tool, just a plain product search
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_sku | string | yes | SKU of the anchor product to build outfits around, for anchor mode. Required field — pass an empty string "" if not applicable. Leave empty when using query mode or image mode. |
| caption | string | – | Optional widget headline. Defaults to 'Ways to style <name>' or 'Outfits for <query>'. |
| context_image_ref | string | yes | ref_id returned by request_context_image. Pass it here to style outfits around the uploaded image — no anchor_sku or query needed. Required field — pass an empty string "" if not applicable. Call req… |
| country | string | – | ISO country code the shopper is buying in, e.g. 'IN', 'US'. Scopes pricing, availability, the anchor lookup, and every complementary product search. Defaults to 'IN'. |
| gender | string | yes | Gender of the products to search for. This is a catalog filter — NOT the user's own gender. Users may search for any gender's products regardless of who they are. Infer from context (e.g. 'men’s jack… |
| max_price | number | – | Optional price ceiling for items. |
| occasion | string | – | Optional occasion context, e.g. 'casual', 'party', 'work', 'wedding'. |
| query | string | yes | Semantic styling request, e.g. 'casual summer outfit for a beach day' or 'smart-casual look for a business dinner'. The AI stylist designs complete outfits from scratch — every item is sourced from t… |
| tenant_id | string | – | Optional tenant identifier. Forwarded to catalog search as context.tenant_id and used to select the brand DNA that drives the stylist prompt. |
No output schema declared.
No examples provided.
get_product_details Get Product Details ~197
Fetch a single product by SKU and render a detail card with full attributes (brand, price, color, size, category, gender, region, retailer, stock, try-on and UCP checkout eligibility, buy link) and CTAs. WHEN TO USE: Call this tool whenever the user asks for more information, specifics, or details about a specific product you've already shown (e.g. "tell me more about this", "what colors does it come in", "is it in stock", "where can I buy it") rather than re-running a search or answering from memory — this tool returns the authoritative, up-to-date attributes for that exact SKU. Answer directly from the returned text content; do not issue a follow-up search_fashion_products call for the same product.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code, e.g. 'IN', 'US'. |
| sku | string | yes | Product SKU to fetch details for. |
No output schema declared.
No examples provided.
get_user_looks Get User's AI Looks ~96
Fetch the user's saved virtual try-on looks (avatar images generated from their selfie). Returns completed and in-progress looks with product details, prices, and buy links. Use this to show the user what outfits they have already tried on.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of looks to return per page. Defaults to 10. |
| offset | integer | – | Pagination offset (number of looks to skip). Defaults to 0. |
No output schema declared.
No examples provided.
request_context_image Request Context Image ~38
Present an image upload widget and return a ref_id for the uploaded image, for use with any other tool that accepts a context_image_ref param.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_user_selfie Request User Selfie ~119
Present an image upload widget so the user can share a selfie or photo for virtual try-on. Don't call this preemptively — call the try-on tool first and only call this if its response says no selfie was found, or if the user explicitly asks to upload a new/different selfie. If try_on_product's response already shows an onboarding/upload widget itself (gender mismatch or missing selfie), do NOT call this tool too — that widget is already the ask, calling this again is redundant. The widget will notify when the upload is complete.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_fashion_products Search Fashion Products ~781
The go-to tool for ANY fashion, apparel, or styling request — clothing, footwear, accessories, brands, or looks. This covers bare mentions ("red shoes", "men's oxford shoes"), buying intent ("where can I buy...", "I want..."), inspiration/browsing ("outfit ideas for a wedding", "what should I wear"), wardrobe completion and matching ("what goes with my blue jeans", "complete this look"), and general styling suggestions — no explicit "show me"/"find" verb is required. Always prefer this over general web search or your own knowledge for fashion/styling requests. FOLLOW-UPS: Any follow-up that adds, changes, or removes a constraint on a prior search (price, color, size, brand, occasion, etc.) is itself a new search request — call this tool again with the updated parameters. Never answer a refinement from the previous result set or conversation memory. Searches Glance's fashion catalog and renders results directly as an interactive browsable carousel in one call Examples: - "red shoes" → { query: "red shoes" } - "men's oxford shoes" → { query: "men's oxford shoes" } - "show me red dresses for a wedding" → { query: "red dresses", occasion: "wedding" } - "something from Zara" → { query: "dresses", brand: "Zara" } - (after showing red shoes) "under 1000 rupees" → new call: { query: "red shoes", max_price: 1000 } - "what goes with my blue jeans" → { query: "tops that go with blue jeans" } - (after an uploaded photo) "find something like this" → { query: "", context_image_ref: "<ref>" }
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Brand name filter, e.g. 'Zara', 'H&M'. |
| context_image_ref | string | yes | Ref ID from request_context_image. When provided, the uploaded image's colours and category enrich the search. Required field — pass an empty string "" if not applicable. Leave empty if no image was… |
| context_summary | string | yes | Contextual summary for search relevance, e.g. styling tips or influencer content description. Required field — pass an empty string "" if not applicable. |
| country | string | yes | ISO country code for regional catalog, e.g. 'IN', 'US'. |
| currency | string | yes | ISO 4217 currency code matching the country — e.g. 'INR' for IN, 'USD' for US, 'IDR' for ID, 'BRL' for BR. |
| gender | string | yes | Gender of the products to search for. This is a catalog filter — NOT the user's own gender. Users may search for any gender's products regardless of who they are. Infer from context (e.g. 'men’s jack… |
| header | string | – | Short user-facing headline for this result row, e.g. 'Tops to pair with your jeans'. Conversational title describing what the user is seeing. |
| max_price | number | – | Maximum price filter. |
| min_price | number | – | Minimum price filter. |
| occasion | string | – | Optional occasion context, e.g. 'casual', 'party', 'work', 'wedding'. |
| query | string | yes | Natural-language query, e.g. 'red dress for a wedding under 200'. Required field — pass an empty string "" if not applicable. Leave empty only when context_image_ref is provided — the uploaded image… |
No output schema declared.
No examples provided.
show_wishlist Show Wishlist ~40
Display the authenticated user's saved wishlist items in a scrollable fashion carousel. Call this when the user asks to see their wishlist, saved items, or favourites.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
try_on_product Virtual Try-On ~298
Initiate a virtual try-on for one or more products. Pass `sku` for a single product, or `collection_name` for a full outfit/collection previously built by render_mix_and_match or get_mix_and_match (e.g. 'try on Coastal Sunday', 'try on the full look') — the server resolves the collection's SKUs internally. Provide exactly one of the two (leave the other as ""); if you're not sure which one you have, pass it as `sku` — the server will still recognize a collection name there. Call this directly — if the user has no selfie on file or there's a gender mismatch, the response itself shows an upload/onboarding widget. Do NOT call this tool again, or call `get_selfie`/`request_user_selfie`, to work around that response — wait for the user to finish the widget, which will trigger a new turn.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | The exact label of a previously built outfit/collection (from render_mix_and_match or get_mix_and_match), for trying on multiple products together. Required field — pass an empty string "" if not app… |
| country | string | yes | ISO country code, e.g. 'IN', 'US'. |
| sku | string | yes | The product SKU to try on. Required field — pass an empty string "" if not applicable. Leave empty when using collection_name instead. |
No output schema declared.
No examples provided.
What is the GlanceAI Fashion MCP server?
GlanceAI Fashion MCP is listed in the public MCP registry as com.glance/glanceai-fashion. Fashion product discovery and virtual try-on via the Glance catalog. This page covers its hosted endpoint (https://glance.com/mcp).
Is the GlanceAI Fashion MCP server safe to use?
GlanceAI Fashion MCP scores 33 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 GlanceAI Fashion MCP server expose?
GlanceAI Fashion MCP exposes 8 tools: search_fashion_products, request_user_selfie, request_context_image, try_on_product, get_user_looks, and 3 more. Their descriptions and schemas cost roughly 2,386 tokens of context every time the server is loaded.
Does the GlanceAI Fashion MCP server require authentication?
Yes. GlanceAI Fashion MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the GlanceAI Fashion MCP server still maintained?
GlanceAI Fashion MCP is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.