# Able.Style (remote · able.style)

Manage your wardrobe or closet, discover ways to wear your clothes, and get outfit suggestions.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `able.style`: 64/100 (this document), [markdown](https://verifymcp.io/servers/style-able-able-style-wardrobe-management/able.md), [page](https://verifymcp.io/servers/style-able-able-style-wardrobe-management/able)

## Channel facts

- Endpoint: `https://able.style/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.1`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: this server exposes a tool marked destructive (like-dislike-outfit-tool) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 38/100
  - 0% 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 4701 tokens (~213/item across 22 items; 15 tools + 7 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
  - Structured output schemas are declared (80% 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.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 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 Able.Style MCP server?

Able.Style is a hosted endpoint at https://able.style/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 style-able-able-style-wardrobe-management 'https://able.style/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "style-able-able-style-wardrobe-management": {
      "url": "https://able.style/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "style-able-able-style-wardrobe-management": {
      "type": "http",
      "url": "https://able.style/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.style-able-able-style-wardrobe-management]
url = "https://able.style/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "style-able-able-style-wardrobe-management": {
      "type": "remote",
      "url": "https://able.style/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add style-able-able-style-wardrobe-management --url 'https://able.style/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  style-able-able-style-wardrobe-management:
    url: "https://able.style/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "style-able-able-style-wardrobe-management": {
      "Transport": "http",
      "Url": "https://able.style/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add style-able-able-style-wardrobe-management -t streamable-http -u 'https://able.style/mcp'
```

### Other

```json
{
  "mcpServers": {
    "style-able-able-style-wardrobe-management": {
      "type": "http",
      "url": "https://able.style/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-11-05 (score 64, 0)

- [security] Resource “styles-carousel-legacy” now points somewhere else: ui://widget/styles-carousel-v6.html → ui://widget/styles-carousel-v7.html

### 2026-11-04 (score 64, 0)

- [security] Resource “styles-carousel-legacy” now points somewhere else: ui://widget/styles-carousel-v6.html → ui://widget/styles-carousel-v7.html

### 2026-11-03 (score 64, +1)

- [security] Resource “styles-carousel-legacy” now points somewhere else: ui://widget/styles-carousel-v6.html → ui://widget/styles-carousel-v7.html

### 2026-11-02 (score 63, 0)

- [security] Resource “styles-carousel-legacy” now points somewhere else: ui://widget/styles-carousel-v6.html → ui://widget/styles-carousel-v7.html

### 2026-11-01 (score 63, +1)

- [security] Resource “styles-carousel-legacy” now points somewhere else: ui://widget/styles-carousel-v6.html → ui://widget/styles-carousel-v7.html

### 2026-10-31 (score 62, 0)

- [security] Resource “styles-carousel-legacy” now points somewhere else: ui://widget/styles-carousel-v6.html → ui://widget/styles-carousel-v7.html

### 2026-10-30 (score 62, +1)

- [security] Resource “styles-carousel-legacy” now points somewhere else: ui://widget/styles-carousel-v6.html → ui://widget/styles-carousel-v7.html

### 2026-10-29 (score 61, 0)

- [security] Resource “styles-carousel-legacy” now points somewhere else: ui://widget/styles-carousel-v6.html → ui://widget/styles-carousel-v7.html

## MCP tools (15)

### `suggest-outfit-tool` (~680 tokens)

Outfit Suggestion Tool

Generates personalized fashion, style, and outfit suggestions based on wardrobe items, preferences, local weather conditions, and occasion formality. Use this tool when users ask for fashion or style advice such as: "What should I wear?", "What outfit do you recommend?", "Help me choose clothes for [occasion]", "Outfit ideas for [weather/event]", or "What should I wear in [hot/cold/rainy] weather?". Returns a complete, readable outfit description, structured item data, and an inspiration image when one can be safely supplied. Suggestions are personalized using the signed-in user's saved wardrobe items and style preferences. IMPORTANT: The structured result of this tool call — including all styleIdentifier.styleId values for each outfit item — remains in the conversation context and MUST be used verbatim by subsequent tool calls such as add-to-or-remove-from-wardrobe-by-id. After presenting the outfit, do NOT ask any follow-up questions or invite the user to request more outfits — your response is complete as-is. MANDATORY RESPONSE REQUIREMENT: Whenever suggest-outfit-tool succeeds and outfitUrl is non-null, the final user-facing response MUST include exactly one Markdown link labelled "Open in Able.Style" whose target is the exact outfitUrl value. Do not omit the link or substitute a different URL.

Input parameters:

- `inspirationId`: Optional identifier of an existing outfit inspiration to reload. Use this only when refreshing the exact outfit already displayed in the widget.
- `menswearOrWomenswear` (required): Gender category for clothing suggestions: "menswear" for men's clothing, "womenswear" for women's clothing. Set to null if unspecified or user prefers gender-neutral suggestions. Use available user p…
- `smartness` (required): Formality/dressiness level on a 1-5 scale: 1 = Casual (jeans, t-shirts, sneakers, everyday wear), 2 = Quite Casual (smart jeans, polo shirts, clean trainers), 3 = Smart Casual (chinos, button-down sh…
- `temperature` (required): Weather temperature category for outfit appropriateness: "cold" for < 6°C/43°F (winter coats, layers, boots), "cool" for 6-15°C/43-59°F (light jackets, long sleeves, closed shoes), "warm" for 15-22°C…

Output parameters:

- `result` (object): The outfit suggestion result.

### `like-dislike-outfit-tool` (~465 tokens)

Like or Dislike Outfit

Records or removes a like or dislike for a specific outfit suggestion. Use this tool when users want to save outfits they love or indicate ones they don't prefer. Use cases: "I like this outfit", "Save this to my favorites", "I don't like this one", "Remove my like from this outfit". Requires authentication - if user is not logged in, this will trigger an OAuth authentication flow. Helps personalize future outfit suggestions based on user preferences. IMPORTANT: Before calling this tool, look at the structured output of the most recent suggest-outfit-tool call earlier in this conversation. The outfitId required by this tool is at result.outfitId in that result — it IS present in your context. Do not claim you cannot see the outfitId without first examining that tool result. If after examining it you still cannot find a valid outfitId, tell the user and ask them to request a new outfit suggestion first.

Input parameters:

- `likeOrDislike` (string, required): The preference type to record: "like" to mark the outfit as preferred, or "dislike" to mark it as not preferred. Likes help surface similar outfits in future suggestions, while dislikes help filter o…
- `outfitId` (string, required): The unique identifier of the outfit to like or dislike. IMPORTANT: This exact value is available in the conversation context at result.outfitId in the most recent suggest-outfit-tool response — look…
- `value` (boolean, required): Set to true to add the preference (like/dislike), or false to remove an existing preference. Use true when user says "I like this" or "I don't like this". Use false when user says "Remove my like" or…

Output parameters:

- `result` (object): The like/dislike result.

### `add-to-or-remove-from-wardrobe-by-id` (~733 tokens)

Manage Wardrobe Item

Adds or removes a known clothing item from the user's personal wardrobe by its style ID. Use this tool when users want to track clothing items they own or indicate they have something similar. Use cases: "Add this to my wardrobe", "I have a similar jacket", "Mark that I own this", "Remove this from my wardrobe". Requires authentication - if user is not logged in, this will trigger an OAuth authentication flow. Wardrobe items are used to personalize outfit suggestions with clothes the user actually owns. IMPORTANT: Before calling this tool, look at the structured output of the most recent suggest-outfit-tool call earlier in this conversation. The styleId required by this tool is at outfitItems[i].styleIdentifier.styleId in that result — it IS present in your context. Do not claim you cannot see the styleId without first examining that tool result. If after examining it you still cannot find a matching item, tell the user and ask them to request a new outfit suggestion first.

Input parameters:

- `addOrRemove` (string, required): The action to perform: "add" to include the item in the user's wardrobe, or "remove" to delete it from their collection. Use "add" when user says "I have this shirt" or "Add the shoes to my wardrobe"…
- `categoryName`: Provide the category name of the style to add to or remove from the wardrobe. For example: "Jackets", "Shirts", "Trousers", "Shoes". This value is provided in outfit suggestion responses in the "cate…
- `isUserStyle` (boolean, required): Whether this is a user-created custom style (true) or a catalog style from the platform (false). Most items from outfit suggestions will be catalog styles (false). IMPORTANT: This value MUST be copie…
- `styleDescription` (string, required): The user-friendly description of the style to add to or remove from the wardrobe. IMPORTANT: This value MUST be copied from the `description` field of the outfit item returned in the most recent prev…
- `styleId` (string, required): The unique identifier of the clothing style/item. IMPORTANT: This value MUST be copied exactly from the `styleIdentifier.styleId` field returned in the most recent previous `suggest-outfit-tool` resp…

Output parameters:

- `result` (object): The wardrobe update result.

### `add-to-or-remove-from-closet-tool` (~763 tokens)

Manage Wardrobe Item

Backward-compatible alias of add-to-or-remove-from-wardrobe-by-id. Prefer add-to-or-remove-from-wardrobe-by-id for new calls. Adds or removes a known clothing item from the user's personal wardrobe by its style ID. Use this tool when users want to track clothing items they own or indicate they have something similar. Use cases: "Add this to my wardrobe", "I have a similar jacket", "Mark that I own this", "Remove this from my wardrobe". Requires authentication - if user is not logged in, this will trigger an OAuth authentication flow. Wardrobe items are used to personalize outfit suggestions with clothes the user actually owns. IMPORTANT: Before calling this tool, look at the structured output of the most recent suggest-outfit-tool call earlier in this conversation. The styleId required by this tool is at outfitItems[i].styleIdentifier.styleId in that result — it IS present in your context. Do not claim you cannot see the styleId without first examining that tool result. If after examining it you still cannot find a matching item, tell the user and ask them to request a new outfit suggestion first.

Input parameters:

- `addOrRemove` (string, required): The action to perform: "add" to include the item in the user's wardrobe, or "remove" to delete it from their collection. Use "add" when user says "I have this shirt" or "Add the shoes to my wardrobe"…
- `categoryName`: Provide the category name of the style to add to or remove from the wardrobe. For example: "Jackets", "Shirts", "Trousers", "Shoes". This value is provided in outfit suggestion responses in the "cate…
- `isUserStyle` (boolean, required): Whether this is a user-created custom style (true) or a catalog style from the platform (false). Most items from outfit suggestions will be catalog styles (false). IMPORTANT: This value MUST be copie…
- `styleDescription` (string, required): The user-friendly description of the style to add to or remove from the wardrobe. IMPORTANT: This value MUST be copied from the `description` field of the outfit item returned in the most recent prev…
- `styleId` (string, required): The unique identifier of the clothing style/item. IMPORTANT: This value MUST be copied exactly from the `styleIdentifier.styleId` field returned in the most recent previous `suggest-outfit-tool` resp…

Output parameters:

- `result` (object): The wardrobe update result.

### `add_wardrobe_item_from_description` (~330 tokens)

Add Wardrobe Item from Description

Adds one item that the signed-in user owns to their Able.Style wardrobe from a text description supplied by the user. Use this when the user describes an item in words and asks to add it. When a photo, attachment or image URL is the source, use add_wardrobe_item_from_image; if transfer is unavailable, use create_image_upload with purpose wardrobe_image_add. Do not infer a description from an image and call this tool unless the user explicitly requests a description-based item instead of uploading the image. For an item already returned by suggest-outfit-tool, use add-to-or-remove-from-wardrobe-by-id with its exact styleIdentifier. IMPORTANT: Before calling, make sure the description contains exactly one apparel, footwear, or wearable-accessory item and explicitly includes its colour. If colour is missing, ask the user for it before calling. An optional menswear or womenswear value overrides the user's profile preference; omit it when the profile preference should be used. The result includes a link for reviewing the added item. A newly created item's image may still be generated in the background.

Input parameters:

- `description` (string, required): A 10–150 character description of exactly one item the user owns. Use the user's text; do not substitute your interpretation of an attached image unless the user explicitly requests a description-bas…
- `menswearOrWomenswear`: Optional clothing preference for resolving categories. Supply only when the user has specified menswear or womenswear; otherwise omit it to use their profile.

Output parameters:

- `result` (object)

### `add_wardrobe_item_from_image` (~314 tokens)

Add Wardrobe Item from Image

Add one clothing item from the user's original image to their wardrobe. Use this when the user attaches a photo or supplies an image URL and asks to add/save the pictured item, for example 'Add this to my wardrobe'. The server processes the actual image. Do not replace this flow with add_wardrobe_item_from_description or your own visual interpretation. Generate requestId and provide exactly one of: ChatGPT file reference in file, publicly accessible imageUrl, or complete original image bytes in image.data. JPEG, PNG and WebP up to 10 MB. Never invent file IDs, attachment URLs or base64. If the client cannot transfer the original image, call create_image_upload with the same requestId and purpose wardrobe_image_add and show its uploadPageUrl. Poll get_wardrobe_image_activity for the result.

Input parameters:

- `file` (object): The original image attachment supplied by ChatGPT through its file-input mechanism. Use the host-provided file reference; never fabricate download_url or file_id.
- `image` (object)
- `imageUrl` (string): A real, publicly accessible HTTP(S) URL to the original image. Do not use a local path, sandbox URL or an invented URL for a chat attachment.
- `menswearOrWomenswear`: The user's clothing preference. Omit to use their saved preference.
- `requestId` (string, required): Unique identifier for this requested action. Reuse it for retries and the upload-page fallback; use a new value for another item.

### `create_image_upload` (~220 tokens)

Create Image Upload

Create a secure web or installed-app image picker when the user asks for an upload link, or an image-based action cannot receive the original image directly. Use this even when you can see a chat photo but cannot pass its real file reference, public URL or original bytes to add_wardrobe_item_from_image. For wardrobe photos, use purpose wardrobe_image_add; do not silently switch to add_wardrobe_item_from_description. Generate a requestId for a new action or reuse the same requestId from a direct-image attempt. Currently supports wardrobe_image_add: one clothing item per image. Returns uploadId, uploadPageUrl, expiresAt and a purpose-specific action reference. Show uploadPageUrl and ask the user to open it and submit their photo. Creating the link does not upload the chat attachment or add the item.

Input parameters:

- `options` (object)
- `purpose` (string, required)
- `requestId` (string, required): Unique identifier for this requested action. Reuse it for retries and the upload-page fallback; use a new value for another item.

### `get_wardrobe_image_activity` (~58 tokens)

Get Wardrobe Image Activity

Check the status of an owned wardrobe image action. Returns safe failure details or the added item and its link. Use activityId from add_wardrobe_item_from_image or create_image_upload.

Input parameters:

- `activityId` (string, required)

### `search_wardrobe` (~189 tokens)

Search Wardrobe

Use this when the user wants to browse or search their signed-in wardrobe, including questions about categories, colours, attributes, newest items, and natural-language terms such as 'flowery shirts'. Returns up to five items per call and the total number of matches across all pages. The results widget automatically loads further pages as the user scrolls. If the widget is unavailable and nextPageToken is present, call this tool again with only that pageToken when the user asks for more results. Do not combine a pageToken with query, sortBy, or filters.

Input parameters:

- `filters` (object)
- `pageToken`: Opaque continuation token from the preceding result. When supplied, omit all other inputs.
- `query`: Optional natural-language wardrobe search. Whitespace is trimmed.
- `sortBy` (string): Sort order. Defaults to relevance for a query and newest-first without a query.

Output parameters:

- `result` (object)

### `style-wear-with-get-by-id` (~190 tokens)

Styles to Wear With

Get other styles and owned userStyles that can be worn with a particular clothing item. Uses the same selection logic as the Able.Style style page and requires sign-in. Copy exact IDs from earlier results: a ref with kind style uses styleId, and kind user_style uses userStyleId. Provide exactly one of styleId or userStyleId. Returns five items per page; the widget loads more on scroll. Without a widget, call this same tool again with only nextPageToken as pageToken when more results are wanted.

Input parameters:

- `pageToken` (string): Continuation token from this tool. When supplied, omit all other inputs.
- `styleId` (string): Exact catalog style ID. Omit userStyleId and pageToken.
- `userStyleId` (string): Exact ID of a userStyle owned by the signed-in user. Omit styleId and pageToken.

Output parameters:

- `result` (object)

### `style-ways-to-wear-by-id` (~195 tokens)

Ways to Wear

Get outfit inspirations showing ways to wear a particular clothing item, including their tagged styles and owned userStyles. Uses the same selection logic as the Able.Style style page and requires sign-in. Copy exact IDs from earlier results: a ref with kind style uses styleId, and kind user_style uses userStyleId. Provide exactly one of styleId or userStyleId. Returns five items per page; the widget loads more on scroll. Without a widget, call this same tool again with only nextPageToken as pageToken when more results are wanted.

Input parameters:

- `pageToken` (string): Continuation token from this tool. When supplied, omit all other inputs.
- `styleId` (string): Exact catalog style ID. Omit userStyleId and pageToken.
- `userStyleId` (string): Exact ID of a userStyle owned by the signed-in user. Omit styleId and pageToken.

Output parameters:

- `result` (object)

### `style-purchase-options-by-id` (~159 tokens)

Style Purchase Options

Find matching products and retailers where the user can buy a catalog style. Requires sign-in. Copy the exact catalog styleId from an earlier result; userStyle IDs are not supported. An explicit country overrides the saved account delivery country; otherwise the saved account country is preferred to the optional host country hint. Ask the user to select a country when neither is available. Save deliberate country selections with update-user-settings-tool using settings.deliveryCountry. Returns the complete options snapshot, including price, availability, retailer and product links. When searching or refreshing, call again with the same styleId and country to refresh. Buy links are obtained on demand with style-purchase-buy-url.

Input parameters:

- `country` (string)
- `styleId` (string, required)

Output parameters:

- `result` (object)

### `style-purchase-buy-url` (~117 tokens)

Open Style Retailer

Recheck an exact purchase offer and return its current retailer link. Requires sign-in. Call only when the user wants to open a retailer, using the exact styleId, styleProductId, offerId and delivery country from style-purchase-options-by-id. Do not call for offers with canBuy false. This opens a product listing; it does not place an order.

Input parameters:

- `country` (string, required)
- `offerId` (string, required)
- `styleId` (string, required)
- `styleProductId` (string, required)

Output parameters:

- `result` (object)

### `update-user-settings-tool` (~31 tokens)

Update User Settings

Updates one or more settings on the signed-in user's Able Style profile.

Input parameters:

- `settings` (object, required)

Output parameters:

- `result` (object)

### `authentication-status-tool` (~37 tokens)

Check Able Style sign-in status

Checks whether the current Able Style app session is signed in. This app-only tool never starts authentication and must not be called by the model.

Output parameters:

- `result` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/style-able-able-style-wardrobe-management/able#diagnostics

## Score history

- 2026-11-05: 64
- 2026-11-04: 64
- 2026-11-03: 64
- 2026-11-02: 63
- 2026-11-01: 63
- 2026-10-31: 62
- 2026-10-30: 62
- 2026-10-29: 61
- 2026-10-28: 61
- 2026-10-27: 60
- 2026-10-26: 60
- 2026-10-25: 59
- 2026-10-24: 59
- 2026-10-23: 58
- 2026-10-22: 58
- 2026-10-21: 57
- 2026-10-20: 57

## Common questions

### What is the Able.Style MCP server?

Able.Style is an MCP server listed in the public MCP registry as style.able/able-style-wardrobe-management. Manage your wardrobe or closet, discover ways to wear your clothes, and get outfit suggestions. This page covers its hosted endpoint (https://able.style/mcp).

### Is the Able.Style MCP server safe to use?

Able.Style scores 64 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 Able.Style MCP server expose?

Able.Style exposes 15 tools: suggest-outfit-tool, like-dislike-outfit-tool, add-to-or-remove-from-wardrobe-by-id, add-to-or-remove-from-closet-tool, add_wardrobe_item_from_description, and 10 more. Their descriptions and schemas cost roughly 4,481 tokens of context every time the server is loaded.

### Does the Able.Style MCP server require authentication?

No. We connected to Able.Style without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Able.Style MCP server still maintained?

Able.Style is still listed as active in the MCP registry. We last reached this channel on 5 November 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://able.style/mcp
- Website: https://able.style/mcp
- Changelog RSS feed: https://verifymcp.io/servers/style-able-able-style-wardrobe-management/able.xml
- Changelog JSON feed: https://verifymcp.io/servers/style-able-able-style-wardrobe-management/able.json
- HTML version of this page: https://verifymcp.io/servers/style-able-able-style-wardrobe-management/able