Home / MCP registry index / ai.uwear/uwear

Uwear

ai.uwear/uwear in the official MCP registry. Endpoint https://api.uwear.ai/mcp.

The registry describes it as: AI photoshoot studio: garments, avatars, locations, and art direction

We read its 71 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

request_user_context read_shoot_board search_uwear_library modify_shoot_board show_in_shoot_board add_chat_photos_to_board set_garment_side save_art_direction propose_brief update_brief get_brief confirm_brief mcp_brief_runs get_generation_status get_generation_results list_garments upload_garment_from_public_url list_avatars upload_avatar_from_chat_file list_outfits list_locations create_location create_tag queue_generation_result_qa read_generation_result_qa set_generation_result_favorite propose_montage update_montage_proposal get_user_credits list_tags save_reference_file_from_chat_file list_art_directions get_art_direction list_templates mcp_get_context mcp_replace_context mcp_add_context mcp_clear_context mcp_list_files mcp_save_retouch mcp_export_montage mcp_generate_clip mcp_intake_files mcp_commit_intake mcp_reclassify_board_item mcp_add_garment_view mcp_upload_intake_photo mcp_edit_brief mcp_recipe_history mcp_brief_list mcp_recipe_list mcp_recipe_open mcp_recipe_preflight mcp_recipe_save_draft mcp_recipe_copy mcp_workflow_assets mcp_workflow_gallery mcp_workflow_tags mcp_workflow_garment_categories mcp_workflow_cameras and 11 more

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/ai-uwear-uwear/badge.svg)](https://lazaretto.dev/mcp-registry/ai-uwear-uwear)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.