Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Uwear

REMOTE · API.UWEAR.AI

AI photoshoot studio: garments, avatars, locations, and art direction

Available components

0 this week 84 Trust /100

Last scanned (10 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

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 Security92
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 16336 tokens (~152/item across 107 items; 93 tools + 14 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management45
  • Stability check failed: schema churn in the 30 days we've observed: 32 tool removals, 8 breaking changes, 0 auth/transport breaks, 59 additions. See how to fix → Fail
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 78% of tool parameters carry a description.Partial
  • Structured output schemas are declared (2% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 95 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 2 Nov 26 0
    • New tool “edit_montage”, which the server declares destructive security
    • New tool “generate_montage_clips”, which the server declares destructive security
    • Tool “mcp_export_montage” rewrote its description, which is the text the model reads security
    • Tool “mcp_generate_clip” rewrote its description, which is the text the model reads security
    • Tool “propose_montage” rewrote its description, which is the text the model reads security
    • Tool “update_montage_proposal” rewrote its description, which is the text the model reads security
    • New resource “video-guide” functional
    • New tool “create_montage” functional
    • New tool “export_montage” functional
    • New tool “get_montage_run” functional
    • New tool “list_montages” functional
    • New tool “quote_montage” functional
    • New tool “read_montage” functional
    • New tool “read_video_guide” functional
    • “propose_montage” reworded the description of “base_resolution” cosmetic
    • “update_montage_proposal” reworded the description of “base_resolution” cosmetic
  • 25 Oct 26 0
    • A breaking change shipped without a version bump: still 2.0.0 ▼ security
    • Tool “create_automation” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “update_automation”, which the server declares destructive security
    • Tool “add_chat_photos_to_board” rewrote its description, which is the text the model reads security
    • Tool “confirm_brief” rewrote its description, which is the text the model reads security
    • Tool “list_templates” rewrote its description, which is the text the model reads security
    • Tool “set_garment_side” rewrote its description, which is the text the model reads security
    • Tool “update_brief” rewrote its description, which is the text the model reads security
    • Tool coverage: 87% → 81% ▼ functional
    • New tool “get_automation” functional
    • New tool “plan_shoot_background_removal” functional
    • New tool “plan_shoot_camera_change” functional
    • New tool “plan_shoot_edit” functional
    • New tool “plan_shoot_image” functional
    • New tool “plan_shoot_upscale” functional
    • New tool “plan_shoot_video” functional
    • New tool “remove_shoot_image” functional
    • New tool “remove_shoot_step” functional
    • New tool “save_automation” functional
    • “add_chat_photos_to_board” added an optional parameter “back_of” cosmetic
    • “list_templates” added an optional parameter “created_by_profile_id” cosmetic
    • “list_templates” added an optional parameter “kind” cosmetic
    • “list_templates” added an optional parameter “sort” cosmetic
    • “set_garment_side” added an optional parameter “from_garment_id” cosmetic
    • “update_brief” added an optional parameter “expected_brief_revision” cosmetic
    • “propose_brief” reworded the description of “recipe_workflow_id” cosmetic
    • “update_brief” reworded the description of “recipe_workflow_id” cosmetic
  • 24 Oct 26 0
    • A breaking change shipped without a version bump: still 2.0.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “confirm_brief” rewrote its description, which is the text the model reads security
    • Tool “propose_brief” rewrote its description, which is the text the model reads security
    • Tool “update_brief” rewrote its description, which is the text the model reads security
    • “confirm_brief” added a required parameter “runs”, so existing callers break ▼ functional
    • “confirm_brief” made “expected_total_credits” required, so existing callers break ▼ functional
    • New tool “create_automation” functional
    • “confirm_brief” reworded the description of “expected_total_credits” cosmetic
    • “propose_brief” reworded the description of “direction” cosmetic
    • “propose_brief” reworded the description of “image_model” cosmetic
    • “propose_brief” reworded the description of “recipe_workflow_id” cosmetic
    • “propose_brief” reworded the description of “video_model” cosmetic
    • “update_brief” reworded the description of “direction” cosmetic
    • “update_brief” reworded the description of “image_model” cosmetic
    • “update_brief” reworded the description of “recipe_look_keys” cosmetic
    • “update_brief” reworded the description of “recipe_workflow_id” cosmetic
    • “update_brief” reworded the description of “video_model” cosmetic
    • “propose_brief” dropped the optional parameter “output” cosmetic
    • “propose_brief” dropped the optional parameter “recipe” cosmetic
    • “update_brief” dropped the optional parameter “output” cosmetic
    • “update_brief” dropped the optional parameter “recipe” cosmetic
  • 23 Oct 26 0
    • A breaking change shipped without a version bump: still 2.0.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “confirm_brief” rewrote its description, which is the text the model reads security
    • Tool “mcp_brief_runs” rewrote its description, which is the text the model reads security
    • Tool “propose_brief” rewrote its description, which is the text the model reads security
    • Tool “queue_generation_result_qa” rewrote its description, which is the text the model reads security
    • Tool “save_art_direction” rewrote its description, which is the text the model reads security
    • Tool “update_brief” rewrote its description, which is the text the model reads security
    • “propose_brief” made “direction” required, so existing callers break ▼ functional
    • New tool “list_automations” functional
    • New tool “list_briefs” functional
    • “propose_brief” added an optional parameter “image_model” cosmetic
    • “propose_brief” added an optional parameter “video_model” cosmetic
    • “confirm_brief” reworded the description of “idempotency_key” cosmetic
    • “propose_brief” reworded the description of “direction” cosmetic
    • “propose_brief” reworded the description of “output” cosmetic
    • “propose_brief” reworded the description of “recipe_workflow_id” cosmetic
    • “queue_generation_result_qa” reworded the description of “generation_result_ids” cosmetic
    • “update_brief” reworded the description of “direction” cosmetic
    • “update_brief” reworded the description of “image_model” cosmetic
    • “update_brief” reworded the description of “output” cosmetic
    • “update_brief” reworded the description of “recipe_workflow_id” cosmetic
    • “update_brief” reworded the description of “video_model” cosmetic
    • “propose_brief” dropped the optional parameter “from_brief_id” cosmetic
  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “add_chat_photos_to_board” rewrote its description, which is the text the model reads security
    • Tool “confirm_brief” rewrote its description, which is the text the model reads security
    • Tool “get_brief” rewrote its description, which is the text the model reads security
    • Tool “get_generation_results” rewrote its description, which is the text the model reads security
    • Tool “get_generation_status” rewrote its description, which is the text the model reads security
    • Tool “mcp_brief_runs” rewrote its description, which is the text the model reads security
    • Tool “propose_brief” rewrote its description, which is the text the model reads security
    • Tool “update_brief” rewrote its description, which is the text the model reads security
    • New tool “set_garment_side” functional
    • “add_chat_photos_to_board” added an optional parameter “sides” cosmetic
    • “propose_brief” added an optional parameter “from_brief_id” cosmetic
    • “propose_brief” added an optional parameter “output” cosmetic
    • “update_brief” added an optional parameter “output” cosmetic
    • “add_chat_photos_to_board” reworded the description of “upload_handles” cosmetic
    • “confirm_brief” reworded the description of “idempotency_key” cosmetic
    • “propose_brief” reworded the description of “direction” cosmetic
    • “propose_brief” made “direction” optional cosmetic
    • Tool “get_generation_results” changed its title: Get Generation Results → Show Results cosmetic
    • Tool “get_generation_status” changed its title: Get Generation Status → Generation Status cosmetic
    • Tool “mcp_brief_runs” changed its title: Brief Runs → Follow Brief Runs cosmetic
  • 12 Oct 26 −5

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • Tool “add_avatar_reference” was removed ▼ security
    • Tool “apply_backdrop” was removed ▼ security
    • Tool “author_art_direction” was removed ▼ security
    • Tool “build_avatar_prompt” was removed ▼ security
    • Tool “copy_template_to_generate_node_config” was removed ▼ security
    • Tool “create_art_direction” was removed ▼ security
    • Tool “create_avatar_from_references” was removed ▼ security
    • Tool “create_outfit_from_garment_ids” was removed ▼ security
    • Tool “delete_template” was removed ▼ security
    • Tool “duplicate_art_direction” was removed ▼ security
    • Tool “estimate_cost” was removed ▼ security
    • Tool “finish_local_garment_upload” was removed ▼ security
    • Tool “generate_avatar” was removed ▼ security
    • Tool “get_art_direction_authoring_job” was removed ▼ security
    • Tool “get_connection_identity” was removed ▼ security
    • Tool “get_garment” was removed ▼ security
    • Tool “get_items_by_tag” was removed ▼ security
    • Tool “get_location” was removed ▼ security
    • Tool “get_outfit” was removed ▼ security
    • Tool “get_template” was removed ▼ security
    • Tool “iterate_art_direction” was removed ▼ security
    • Tool “list_models” was removed ▼ security
    • Tool “prepare_local_garment_upload” was removed ▼ security
    • Tool “propose_outfits” was removed ▼ security
    • Tool “save_generated_avatar” was removed ▼ security
    • Injection markers: fail → pass ▲ security
    • Tool “confirm_brief” rewrote its description, which is the text the model reads security
    • Tool “get_brief” rewrote its description, which is the text the model reads security
    • Tool “get_generation_results” rewrote its description, which is the text the model reads security
    • Tool “get_generation_status” rewrote its description, which is the text the model reads security
    • Tool “list_avatars” rewrote its description, which is the text the model reads security
    • Tool “list_garments” rewrote its description, which is the text the model reads security
    • Tool “mcp_add_context” rewrote its description, which is the text the model reads security
    • Tool “mcp_clear_context” rewrote its description, which is the text the model reads security
    • Tool “mcp_export_montage” rewrote its description, which is the text the model reads security
    • Tool “mcp_generate_clip” rewrote its description, which is the text the model reads security
    • Tool “mcp_get_context” rewrote its description, which is the text the model reads security
    • Tool “mcp_list_files” rewrote its description, which is the text the model reads security
    • Tool “mcp_replace_context” rewrote its description, which is the text the model reads security
    • Tool “mcp_save_retouch” rewrote its description, which is the text the model reads security
    • Tool “propose_brief” rewrote its description, which is the text the model reads security
    • Tool “request_user_context” rewrote its description, which is the text the model reads security
    • Tool “propose_brief” no longer declares itself destructive security
    • Tool coverage: 100% → 87% ▼ functional
    • Tool coverage: 18% → 3% ▼ functional
    • “confirm_brief” added a required parameter “board_id”, so existing callers break ▼ functional
    • “confirm_brief” added a required parameter “expected_brief_revision”, so existing callers break ▼ functional
    • “confirm_brief” added a required parameter “idempotency_key”, so existing callers break ▼ functional
    • “get_brief” added a required parameter “board_id”, so existing callers break ▼ functional
    • “mcp_add_context” added a required parameter “board_id”, so existing callers break ▼ functional
    • “mcp_add_context” added a required parameter “expected_revision”, so existing callers break ▼ functional
    • “mcp_clear_context” added a required parameter “board_id”, so existing callers break ▼ functional
    • “mcp_clear_context” added a required parameter “expected_revision”, so existing callers break ▼ functional
    • “mcp_get_context” added a required parameter “board_id”, so existing callers break ▼ functional
    • “mcp_replace_context” added a required parameter “board_id”, so existing callers break ▼ functional
    • “mcp_replace_context” added a required parameter “expected_revision”, so existing callers break ▼ functional
    • “propose_brief” added a required parameter “board_id”, so existing callers break ▼ functional
    • “propose_brief” added a required parameter “direction”, so existing callers break ▼ functional
    • “propose_brief” added a required parameter “looks”, so existing callers break ▼ functional
    • “propose_brief” dropped the required parameter “commands” ▼ functional
    • Schema quality: 225 → 163 ▲ functional
    • Schema quality: excellent → good functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • “confirm_brief” added an optional parameter “expected_total_credits” cosmetic
    • “get_generation_results” added an optional parameter “include_snapshot” cosmetic
    • “get_generation_status” added an optional parameter “include_snapshot” cosmetic
    • “mcp_add_context” added an optional parameter “board_version” cosmetic
    • “mcp_clear_context” added an optional parameter “board_version” cosmetic
    • “mcp_get_context” added an optional parameter “board_version” cosmetic
    • “mcp_list_files” added an optional parameter “query” cosmetic
    • “mcp_list_files” added an optional parameter “tag_ids” cosmetic
    • “mcp_replace_context” added an optional parameter “board_version” cosmetic
    • “propose_brief” added an optional parameter “recipe” cosmetic
    • “propose_brief” added an optional parameter “recipe_workflow_id” cosmetic
    • “propose_brief” added an optional parameter “title” cosmetic
    • “propose_montage” added an optional parameter “board_id” cosmetic
    • “request_user_context” added an optional parameter “board_id” cosmetic
    • “confirm_brief” reworded the description of “brief_id” cosmetic
    • “get_brief” reworded the description of “brief_id” cosmetic
    • “get_generation_status” reworded the description of “generation_id” cosmetic
    • “list_garments” reworded the description of “include_uncategorized” cosmetic
    • “confirm_brief” dropped the optional parameter “execute” cosmetic
    • “propose_brief” dropped the optional parameter “creative_context” cosmetic
    • “propose_brief” dropped the optional parameter “execute_immediately” cosmetic
    • Tool “confirm_brief” changed its title: Approve and Run Brief → Generate Brief cosmetic
    • Tool “get_brief” changed its title: Reopen Saved Brief → Read Brief cosmetic
    • Tool “list_avatars” changed its title: List Avatars → List Models cosmetic
    • Tool “propose_brief” changed its title: Create Brief for Approval → Propose Brief cosmetic
    • Tool “request_user_context” changed its title: Ask User to Pick Assets → New Shoot Board cosmetic
  • 2 Oct 26 89

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://api.uwear.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.uwear.ai CN=Amazon RSA 2048 M04,O=Amazon,C=US 20 Jun 2026 3 Jan 2027 RSA 2048 SHA256-RSA 7972aca3b35635c62a4a2f54fc31faa
SANs: api.uwear.ai
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.uwear.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814, 3799 8, 8 Verified
uwear.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://api.uwear.ai/.well-known/oauth-protected-resource/mcp", scope="mcp"

Bearer resource_metadata="https://api.uwear.ai/.well-known/oauth-protected-resource/mcp", scope="mcp"

Protected resource metadata

Document https://api.uwear.ai/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://api.uwear.ai/mcp
Authorisation server https://api.uwear.ai

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.uwear.ai/mcp Verified 200
http (plaintext) http://api.uwear.ai/mcp HTTPS enforced
MCP tools · 93 exposed · ~15,978 tokens

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 →

Tool Tokens
add_chat_photos_to_board ~772

Use this when the user attaches images in this chat and wants them in Uwear, on the Shoot Board or in a shoot: clothing, a Model, a Location or a reference. Put each attachment in its own field, image_file_1, image_file_2, ... in attachment order, as the chat provides it: ChatGPT passes the file itself, also when you see only a file name or path. Chat attachments only: a web address is refused (ask the user to attach that photo). kinds: {image_file_N: garment|avatar|location|reference} for photos whose kind the user said or is clear (avatar: a person to use as a Model); Uwear sorts the rest. Saves each photo to the library (a repeat is reused), adds it to the board and returns its pile and asset id for propose_brief / update_brief. A photo returned unsure lists two candidates: ask the user and call again with the same files, kinds, sides and back_of. back_of: {image_file_N: image_file_M} when image_file_N is the back of the same garment image_file_M shows from the front (you can see they match): Uwear saves one garment with both photos. sides: {image_file_N: back} for a garment photo that plainly shows a garment's back with no front photo of it here; left out, a photo is its garment's front.

NameTypeReqDescription
back_ofobject–Two photos of one garment, when you can see they match: {image_file_N: image_file_M} for image_file_N showing the back of the garment image_file_M shows from the front. Uwear saves one garment with b…
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
image_file_1objectyesAn image attached in this chat, passed as the chat provides it.
image_file_10object–An image attached in this chat, passed as the chat provides it.
image_file_2object–An image attached in this chat, passed as the chat provides it.
image_file_3object–An image attached in this chat, passed as the chat provides it.
image_file_4object–An image attached in this chat, passed as the chat provides it.
image_file_5object–An image attached in this chat, passed as the chat provides it.
image_file_6object–An image attached in this chat, passed as the chat provides it.
image_file_7object–An image attached in this chat, passed as the chat provides it.
image_file_8object–An image attached in this chat, passed as the chat provides it.
image_file_9object–An image attached in this chat, passed as the chat provides it.
kindsobject–What each photo is, when you can tell (garment: clothing; avatar: a person to use as a Model; location: a place; reference: a pose, mood or styling photo), or the user's answer for one that came back…
sidesobject–Garment photos only, when you can see which side one shows: {image_file_N: back} for a photo of the garment's back. A photo left out is its garment's front.
upload_handlesobject–Only after running a previous call's upload_command: {image_file_N: the sha256 it printed for that photo}. Never the attachments themselves: those go in image_file_N.

No output schema declared.

No examples provided.

confirm_brief ~250

Executes the reviewed photoshoot flow, including its declared image and video steps. Spends credits at the brief's quote. This client may show no approval prompt, so call it only when the user agreed in chat to run the brief: their message asking to generate or run it is that agreement, a request to change the brief is not one; otherwise give the quote and wait for their yes. expected_brief_revision, runs and expected_total_credits must match the latest brief; if they changed, nothing runs and the current brief is returned. The same idempotency_key never runs or charges twice.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
brief_idintegeryes–
expected_brief_revisionintegeryesThe board's brief_revision shown with this brief.
expected_total_creditsintegeryesThe credits this Generate charges, as get_brief returns them.
idempotency_keystringyesRetry key for one Generate: never runs or charges twice.
runsarrayyesWhat this Generate runs: each Automation, its looks and its steps, as get_brief returns them.

No output schema declared.

No examples provided.

create_location ~136

Create a reusable location/scene reference from an image URL. If no description is supplied, the backend analyzes the image. Use the returned location_id in propose_brief/update_brief.

NameTypeReqDescription
descriptionstring–Optional location description. If omitted, the system analyzes the image.
image_urlstringyesURL of the location/reference image
namestringyesName for the reusable location/scene reference
source_metadataobject–Optional provenance metadata for the source image
tag_idsarray–Optional tag IDs to assign after creating the location
thumbnail_urlstring–Optional thumbnail URL

No output schema declared.

No examples provided.

create_montage ~68

Create an empty saved montage. Read read_video_guide before you plan a video, then fill it with edit_montage. Free.

NameTypeReqDescription
aspect_ratiostring––
fit_modestring––
resolutioninteger––
titlestring––

No output schema declared.

No examples provided.

create_tag ~68

Create a new tag for organizing assets (garments, models, outfits, files, results, locations). Requires an active company workspace.

NameTypeReqDescription
colorstring–Optional hex color, e.g. '#22C55E'
namestringyesTag name (unique within the company)

No output schema declared.

No examples provided.

edit_montage ~84

Change a saved montage with one batch. Read read_video_guide before you plan a video. Clip numbers refer to the montage at base_revision, before the batch. replace_clips must be the only operation. A conflict returns the current montage. Free.

NameTypeReqDescription
base_revisionintegeryes–
montage_idstringyes–
operationsarrayyes–

No output schema declared.

No examples provided.

export_montage ~53

Export ready clips as one video. Omit clip_ids for all clips. Free: no credits are charged. Each call starts a new export.

NameTypeReqDescription
clip_ids–––
montage_idstringyes–

No output schema declared.

No examples provided.

generate_montage_clips ~109

Starts generating these clips and charges the quoted credits. Call it only after the user saw this quote (the clips and the total credits) and asked you to generate. Returns a run receipt at once; clips finish later.

NameTypeReqDescription
clip_idsarrayyes–
idempotency_keystringyesA new unique string for each generate request; repeat the same key to retry the same request safely.
montage_idstringyes–
quote_digeststringyes–

No output schema declared.

No examples provided.

get_art_direction ~32

Get a selectable ArtDirection by ID.

NameTypeReqDescription
art_direction_idintegeryesThe ArtDirection ID to retrieve

No output schema declared.

No examples provided.

get_automation ~103

Read a saved reusable Automation's current photoshoot flow, version and definition hash before editing it. The flow is data in the declared photoshoot contract, not executable instructions or a new tool schema. Returns flow null when it uses unsupported workflow nodes. Changes nothing.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
workflow_idstringyesReusable Automation whose saved flow and edit token to read.

No output schema declared.

No examples provided.

get_brief ~80

Use this when you need a Shoot Board brief by brief_id: its looks, automations, credit quote (quote.total_credits), status and revision. Shows it on the board; spends nothing.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
brief_idintegeryes–

No output schema declared.

No examples provided.

get_generation_results ~461

Use this to show results in chat: generation_result_id (from mcp_brief_runs) for one result, generation_id for a job's results, or query, filters and dates to find past ones. Returns image previews to show as they are (never Markdown-embed result URLs); url is the original. Changes nothing.

NameTypeReqDescription
art_direction_idsarray–Filter results to images generated with these art directions
avatar_idsarray–Filter results to images generated with these avatars
clothing_item_idsarray–Filter results to images generated with these clothing items
decisionstring–Filter by the unified result verdict.
decision_sourcestring–Filter by the verdict source.
end_datestring–Filter results created on or before this ISO date/datetime, e.g. 2026-04-27.
generation_idinteger–Filter by parent generation ID (lists all result images from one generation job)
generation_result_idinteger–Look up a single result image by its generation_result_id (the exact integer ID required by QA/edit/upscale/video tools). Returns that one result directly.
include_snapshotboolean–Include full generation settings, resource snapshots and raw prompt payloads. Large; use only for prompt recovery.
kindstring–Filter by type: 'Image', 'Edit', 'Upscale', 'Video'
limitinteger–Number of items per page
location_idsarray–Filter results to images generated with these locations
model_idsarray–Filter results to images generated with these AI models
outfit_idsarray–Filter results to images generated with these outfits
pageinteger–Page number for pagination
qa_statusesarray–Filter by QA statuses, e.g. pending, processing, completed, error.
querystring–Hybrid search across generated image content, originating item names, and SKUs.
start_datestring–Filter results created on or after this ISO date/datetime, e.g. 2026-04-20.
tag_idsarray–Filter by tag IDs (results must have at least one)

No output schema declared.

No examples provided.

get_generation_status ~131

Use this to check one generation job by generation_id: its status, credits and, when it failed, a safe error_message. A brief's runs are read with mcp_brief_runs. Changes nothing.

NameTypeReqDescription
generation_idintegeryesThe generation ID to check. Returns compact status, avatar_id, model_id, model_slug, and use_case. UI 'Gemini Pro' maps to model_slug nano-banana-pro or nano_banana_pro_clothing.
include_snapshotboolean–Include full generation settings, resource snapshots and raw prompt payloads. Large; use only for prompt recovery.

No output schema declared.

No examples provided.

get_montage_run ~39

Read a montage run's current clip progress. done is true when every clip is ready or failed.

NameTypeReqDescription
run_idstringyes–

No output schema declared.

No examples provided.

get_user_credits ~16

Get user's current credit balance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_art_directions ~134

List selectable ArtDirections as compact summaries: visible system ArtDirections plus company ArtDirections. Use query to match exact names and natural-language creative requests. Use this as the catalog step before choosing an art_direction_id for a brief; if there is no clear match, fall back to the user's phrase as prompt/creative_context. Use get_art_direction for the full markdown document before reusing one in a brief.

NameTypeReqDescription
limitinteger–Number of compact ArtDirection summaries per page
pageinteger–Page number for pagination
querystring–Hybrid search across saved ArtDirection names and creative content.

No output schema declared.

No examples provided.

list_automations ~101

Lists the user's Automations, most recently used first, one row each. 10 per page (limit up to 25; cursor: next_cursor for more). Changes nothing.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
cursorstring–The next rows: the next_cursor of the previous page.
limitinteger–Rows per page (default 10).

No output schema declared.

No examples provided.

list_avatars ~228

List the user's Models: the reusable people who wear the Clothing (not the AI models; for those, use mcp_list_model_catalog). Supports structured filters or query for hybrid name/metadata/image-attribute search. Set include_image_url=true when the Model's image itself is needed.

NameTypeReqDescription
avatar_idsarray–Filter to specific avatar IDs
end_datestring–Filter: created on or before this date (ISO format)
include_image_urlboolean–Set true when you need to inspect or reuse the avatar/model image URL.
limitinteger–Number of items per page
pageinteger–Page number for pagination
querystring–Hybrid search across avatar/model names, metadata, and visual attributes.
sortstring–Sort order: 'field:direction', e.g. 'created_at:desc'. Default: created_at:desc
start_datestring–Filter: created on or after this date (ISO format)
tag_idsarray–Filter to avatars with any of these tags

No output schema declared.

No examples provided.

list_briefs ~252

Use this to find a past shoot when the user refers to one ("run the same as last week") or asks what ran: the account's briefs, newest first, 10 by default (limit up to 25; before: next_before for older ones; status ran for generated ones only; automation_workflow_id for the runs of one Automation). Each compact row has its brief_id, title, status, ran_at, automations, direction label, image model, output, look count and credits. Then read the one you need with get_brief for its full values. Changes nothing.

NameTypeReqDescription
automation_workflow_idstring–Only briefs on this Automation (a workflow_id from list_automations or a brief row), its copies included; the board's draft counts unless status is ran.
beforeinteger–Older briefs: the next_before of the previous page.
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
limitinteger–Rows per page (default 10).
statusstring–ran: briefs that were generated; draft: this board's unrun brief. Omit for both.

No output schema declared.

No examples provided.

list_garments ~409

List user's garments with structured filters or query for hybrid name/SKU/metadata/image-attribute search. body_zone expands to categories and is ORed with category when both are given. With a category or body_zone filter and include_uncategorized=false, uncategorized_count reports garments hidden by the category filter within the same scope. If matches are short and uncategorized_count > 0, call again with include_uncategorized=true and inspect those garments.

NameTypeReqDescription
body_zonearray–Filter to categories in any of these body zones; OR with category when both are given.
categoryarray–Filter to garments in any of these canonical categories; OR with body_zone when both are given.
clothing_item_idsarray–Filter to specific garment IDs
end_datestring–Filter: created on or before this date (ISO format)
exclude_clothing_item_idsarray–Exclude these garment IDs, for example the attached garment.
include_image_urlboolean–Set true when the garment image itself is needed for visual display or reuse.
include_uncategorizedboolean–Also include garments with no category when category and/or body_zone filters are used. If the first result has uncategorized_count > 0 and too few matches, call again with true and inspect those gar…
limitinteger–Number of items per page
pageinteger–Page number for pagination
querystring–Hybrid search across garment names, SKUs, metadata, and visual attributes.
sortstring–Sort order: 'field:direction', e.g. 'created_at:desc', 'clothing_item_name:asc'. Default: created_at:desc
start_datestring–Filter: created on or after this date (ISO format, e.g. '2025-06-01')
tag_idsarray–Filter to garments with any of these tags

No output schema declared.

No examples provided.

list_locations ~214

List reusable location/scene reference images by structured filters or query: IDs, tags, date range, and sort. Use when the user wants to pick a saved background/location reference for a generation.

NameTypeReqDescription
end_datestring–Filter: created on or before this date (ISO format)
include_image_urlboolean–Set true when the location/reference image URL is needed for inspection or reuse.
limitinteger–Number of items per page
location_idsarray–Filter to specific location IDs
pageinteger–Page number for pagination
querystring–Hybrid search across location names, metadata, and visual attributes.
sortstring–Sort order: 'field:direction', e.g. 'created_at:desc', 'location_name:asc'. Default: created_at:desc
start_datestring–Filter: created on or after this date (ISO format)
tag_idsarray–Filter to locations with any of these tags

No output schema declared.

No examples provided.

list_montages ~43

List your saved montages, most recently updated first. Returns summaries and page information.

NameTypeReqDescription
items_per_pageinteger––
pageinteger––

No output schema declared.

No examples provided.

list_outfits ~225

List user's outfits (saved garment combinations). Filter by garment IDs, active status, date range, or query against contained garments.

NameTypeReqDescription
clothing_item_idsarray–Filter to outfits containing any of these garments
end_datestring–Filter: created on or before this date (ISO format)
is_activestring–Filter by status: 'true', 'false', or 'both' (default: both)
limitinteger–Number of items per page
outfit_idsarray–Filter to specific outfit IDs
pageinteger–Page number for pagination
querystring–Search outfit names and contained garments.
sortstring–Sort: 'field:direction'. Use 'latest_generation_at:desc' to surface recently generated outfits. Default: created_at:desc
sourcestring–Filter by outfit source.
start_datestring–Filter: created on or after this date (ISO format)
tag_idsarray–Filter to outfits with any of these tags

No output schema declared.

No examples provided.

list_tags ~74

List available tags for the user's company. Use this to resolve user-provided tag names like 'summer26' before selecting garments, outfits, models, files, generations, or locations. For no-UI MCP flows, find the tag ID here, then call get_items_by_tag or the relevant list_* tool with tag_ids.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_templates ~211

List canonical company templates, optionally filtered by kind, scope, command use case, creator, or public t-xxxx share code, with usage sorting. Keeps identify which values apply. Templates persist canonical commands but do not execute generations. System templates named `Demo — …` are worked examples of the canonical command language; read one with `get_template` before authoring a first brief or workflow.

NameTypeReqDescription
catalog_scope––Filter by library or owner_only. Owner-only templates are hidden unless explicitly requested.
created_by_profile_idinteger––
items_per_pageinteger–Number of templates per page
kindstring––
pageinteger–Page number for pagination
share_codestring–Return the template assigned this public t-xxxx share code
sortstring––
template_kind––Filter generation presets or read-only historical batch_workflow records
use_casestring–Filter by a use_case present in any stored command

No output schema declared.

No examples provided.

mcp_add_context ~117

Append items to the Uwear Shoot Board.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
board_versioninteger–Pass 2 to receive board v2 state, including the board's output settings
context_itemsarrayyesShoot Board items to append to the current list
expected_revisionintegeryesBoard revision this write is based on; a stale revision returns a revision_conflict error with the current board instead of overwriting it

No output schema declared.

No examples provided.

mcp_add_garment_view ~267

A Clothing card dropped on another. The photo of from_garment_id becomes the back, side or detail view of garment_id, and from_garment_id leaves the board (deleted only when it is a fresh drop nothing else uses). Or a photo put in the brief's missing-photo slot: image_url instead of from_garment_id, nothing leaves the board. The board's draft brief is saved again when the view changes it. Returns the board (and brief); asking again answers status unchanged.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
expected_revisionintegeryesBoard revision this write is based on; a stale revision returns a revision_conflict error with the current board instead of overwriting it
from_garment_idinteger–the board garment whose photo it is; it leaves the board
garment_idintegeryesthe board garment that gains the photo as a view
image_urlstring–instead of from_garment_id: the stored photo (host file download URL, or the image_url mcp_upload_intake_photo returned)
viewstringyesback, side, or detail (a close-up)

No output schema declared.

No examples provided.

mcp_brief_list ~81

The account's Shoot Board briefs, newest first: every brief that ran (on any Shoot Board) and this board's draft, each with its status, looks, automations, credits and covers.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
pageinteger––

No output schema declared.

No examples provided.

mcp_brief_runs ~140

Use this after confirm_brief or when the user asks how a shoot is going: each look's run of brief_id with its status, credits, results (generation_result_id, kind, url) by step and the error of every step that failed (failures lists them all). Read it again until done is true; while it runs, say so (the board shows progress). Then show the results with get_generation_results. Changes nothing.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
brief_idinteger––
workflow_run_idsarray––

No output schema declared.

No examples provided.

mcp_clear_context ~122

Clear all Shoot Board items, or only one context type.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
board_versioninteger–Pass 2 to receive board v2 state, including the board's output settings
expected_revisionintegeryesBoard revision this write is based on; a stale revision returns a revision_conflict error with the current board instead of overwriting it
typestring–Context type to remove; omit to clear the entire Shoot Board

No output schema declared.

No examples provided.

mcp_commit_intake ~137

Save sorted Shoot Board photos to the library as garments, avatars, locations or reference files, skip ones already saved, and add them to the Shoot Board at expected_revision; a board that changed is refused before anything is saved (revision_conflict with the current board).

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
expected_revisionintegeryesBoard revision this write is based on; a stale revision returns a revision_conflict error with the current board instead of overwriting it
itemsarrayyesPhotos to save, each with its confirmed kind

No output schema declared.

No examples provided.

mcp_delete_generation_results ~53

Delete the user's results and their stored images, as the platform's Delete. Cannot be undone: call it only after the user confirmed in chat which results to delete.

NameTypeReqDescription
generation_result_idsarrayyes–

No output schema declared.

No examples provided.

mcp_edit_brief ~146

Edit the Shoot Board's brief by hand: add, remove or change looks, or run looks through another automation. Saves a new brief linked to the board and returns the board, the brief, its quote and the credit delta; dry_run only quotes.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
brief_idintegeryesThe board's brief (board.brief_id).
dry_runboolean–Quote the edit and its credit delta; save nothing.
expected_brief_revisionintegeryesThe board's brief_revision shown with the brief.
opsarrayyes–

No output schema declared.

No examples provided.

mcp_export_montage ~131

Export montage clips as one stitched video. Spends credits: call it only after the user confirmed the clips and their order in chat. Returns the generation_id to poll with get_generation_status. Prefer export_montage for a saved montage the user can open in Uwear.

NameTypeReqDescription
aspect_ratiostringyesOutput video aspect ratio in W:H format
base_resolutionintegeryesOutput base resolution in pixels
clipsarrayyesOrdered generation-result clips to stitch into the montage
fit_modestringyesHow each clip fits the output frame: contain or cover

No output schema declared.

No examples provided.

mcp_extract_video_frame ~71

Save a still frame of a video result as a new image result, as POST /generation-result/{id}/extract-frame. The result viewer's Save frame.

NameTypeReqDescription
generation_result_idintegeryes–
timestamp_secondsnumber|null–Frame time in seconds; omit for the last frame.

No output schema declared.

No examples provided.

mcp_generate_clip ~248

Queue an image-to-video generation for one montage clip. Spends credits: call it only after the user agreed in chat. Returns the generation_id to poll with get_generation_status. Prefer generate_montage_clips for a saved montage the user can open in Uwear.

NameTypeReqDescription
durationinteger|null–Video duration in seconds; defaults to 5
generate_audioboolean|null–Include audio in the delivered video. False delivers a silent file; fixed-audio providers are muted after generation at the same credits.
generation_result_idinteger|null–Existing generation result ID to use as the source image; provide exactly one source
image_urlstring|null–HTTPS source image URL; provide exactly one source
last_frame_urlstring|null–Optional final-frame image URL for supported video models
modelstringyesVideo model slug or supported model name
promptstring|null–Optional motion prompt for the video clip
resolutionstring|null–Optional output resolution; defaults to 480p
uploaded_file_idinteger|null–Uploaded file ID to use as the source image; provide exactly one source

No output schema declared.

No examples provided.

mcp_get_context ~64

Read the Uwear Shoot Board.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
board_versioninteger–Pass 2 to receive board v2 state, including the board's output settings

No output schema declared.

No examples provided.

mcp_intake_files ~109

Sort photos dropped on the Shoot Board into garment, avatar, location or reference (or unsure with two candidates) and report duplicates within the drop and in the library. Saves nothing. A photo the call had no time left for comes back with error deferred: send it again.

NameTypeReqDescription
board_idstring–The open Shoot Board's board_id, from Open Shoot Board or your context.
filesarrayyesDropped photos, in drop order; results use the same index

No output schema declared.

No examples provided.

mcp_list_files ~97

List uploaded (reference) files for the Uwear MCP workspace files tab and the Shoot Board's References tab.

NameTypeReqDescription
limitinteger–Maximum number of uploaded files per page
pageinteger–Page number for uploaded file results
querystring–Optional search over file names and tags (the Shoot Board's References tab)
tag_idsarray–Optional: only files with any of these tags

No output schema declared.

No examples provided.

mcp_list_model_catalog ~37

The active AI models with their capabilities and pricing rules, as GET /models returns them, for the widget's model pickers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mcp_read_generation ~49

One generation with its results as GET /generation/{id} returns it (prompt, model, settings, inputs), for the result viewer's Info panel.

NameTypeReqDescription
generation_idintegeryes–

No output schema declared.

No examples provided.

mcp_read_generation_result ~52

One generation result as GET /generation-result/{id} returns it (tags, review verdict, QA, prompt, model), for the widget's result viewer.

NameTypeReqDescription
generation_result_idintegeryes–

No output schema declared.

No examples provided.

mcp_recipe_copy ~70

Copy an automation as a new automation for this shoot.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
namestring––
source_version_idstring––
source_workflow_idstringyes–

No output schema declared.

No examples provided.

mcp_recipe_history ~86

An automation's past runs, newest first: one row per Shoot Board Generate (its looks) or per run started on Uwear, with when, how it went, credits and covers.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
pageinteger––
workflow_idstringyes–

No output schema declared.

No examples provided.

mcp_recipe_list ~114

The company's shoot automations (and other automations to copy).

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
include_automationsboolean–Also list automations (read/copy only).
include_definitionsboolean–Also return each listed automation's live graph (the cards that draw its steps).
items_per_pageinteger––
pageinteger––
querystring–Name search.

No output schema declared.

No examples provided.

mcp_recipe_open ~152

Open the brief's automation in the builder: its draft, or once Generate published it its live version (saving an edit of it makes a new automation); another automation opens read-only.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
read_onlyboolean–Show a published version (version_id, else the live one) without opening a draft: a brief that ran shows what it ran, the board's pinned Automation its live version.
version_idstring–The published version to show (an automation, or read_only); a brief recipe opened to edit always opens its draft.
workflow_idstringyes–

No output schema declared.

No examples provided.

mcp_recipe_preflight ~77

Validate and price the automation being edited.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
graphobjectyesThe unsaved authoring graph (as the builder holds it).
version_idstringyes–
workflow_idstringyes–

No output schema declared.

No examples provided.

mcp_recipe_save_draft ~113

Save the automation's draft.

NameTypeReqDescription
base_version_idstring––
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
contract_versionstring––
edgesarrayyes–
expected_definition_hashstring––
failure_policystring––
nodesarrayyes–
result_projectionarray––
version_idstring––
workflow_idstringyes–

No output schema declared.

No examples provided.

mcp_reclassify_board_item ~171

Move a Shoot Board photo between the Clothing, Models and Locations piles. Saves the same image as the new kind and swaps it on the board; the old asset is deleted only if intake saved it in the last 24 hours and nothing uses it, otherwise it stays in the library. Asking for a move that already happened changes nothing and returns the board (status "unchanged").

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
expected_revisionintegeryesBoard revision this write is based on; a stale revision returns a revision_conflict error with the current board instead of overwriting it
itemobjectyesThe board item to move
tostringyesThe pile to move it to

No output schema declared.

No examples provided.

mcp_replace_context ~142

Replace the Uwear Shoot Board items.

NameTypeReqDescription
board_idstringyesThe open Shoot Board's board_id, from Open Shoot Board or your context.
board_versioninteger–Pass 2 to receive board v2 state, including the board's output settings
context_itemsarray–Shoot Board items that replace the current list when context_state is omitted
context_stateobject–Complete Shoot Board state to sanitize and persist; takes precedence over context_items
expected_revisionintegeryesBoard revision this write is based on; a stale revision returns a revision_conflict error with the current board instead of overwriting it

No output schema declared.

No examples provided.

Install

How do I install the Uwear MCP server?

Uwear is a hosted endpoint at https://api.uwear.ai/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 · api.uwear.ai

# add to Claude Code
claude mcp add --transport http ai-uwear-uwear 'https://api.uwear.ai/mcp'
Common questions

What is the Uwear MCP server?

Uwear is an MCP server listed in the public MCP registry as ai.uwear/uwear. AI photoshoot studio: garments, avatars, locations, and art direction. This page covers its hosted endpoint (https://api.uwear.ai/mcp).

Is the Uwear MCP server safe to use?

Uwear scores 84 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 Uwear MCP server expose?

Uwear exposes 93 tools: request_user_context, read_shoot_board, search_uwear_library, modify_shoot_board, show_in_shoot_board, and 88 more. Their descriptions and schemas cost roughly 15,978 tokens of context every time the server is loaded.

Does the Uwear MCP server require authentication?

Yes. Uwear 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 Uwear MCP server still maintained?

Uwear 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.

What did VerifyMCP test on the Uwear MCP server?

VerifyMCP ran 13 checks on Uwear, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.