mcp-registry/ai.uwear/uwear · v2.0.0
As of 2026-10-21 15:11 UTC, the Uwear MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
AI photoshoot studio: garments, avatars, locations, and art direction
Claude Code
claude mcp add --transport http uwear-mcp-server https://api.uwear.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"uwear-mcp-server": {
"type": "http",
"url": "https://api.uwear.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 tool definition(s) exceed ~1,200 tokens each (largest: upload_avatar_from_chat_file, ~1,999).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~8,579 tokens every session. How to fix →
70 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
47 parameter(s) across 22 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~31,792 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
In the last 30 days: 32 tool(s) removed and 28 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 22 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.uwear%2Fuwear/fixes
{
"name": "mcp_save_retouch",
"description": "Save an edited image (image_base64) as a new child result of parent_generation_result_id. Changes no existing result.",
"inputSchema": {
"type": "object",
"required": [
"parent_generation_result_id",
"image_base64"
],
"properties": {
"file_name": {
"type": [
"string",
"null"
],
"description": "Optional filename for the saved retouched image"
},
"mime_type": {
"type": [
"string",
"null"
],
"description": "Optional image MIME type; inferred from a data URL or defaults to image/png"
},
"operations": {
"description": "Optional retouch operation metadata stored with the child result",
"type": "string"
},
"image_base64": {
"type": "string",
"description": "Retouched image encoded as base64 or an image data URL"
},
"parent_generation_result_id": {
"type": "integer",
"minimum": 1,
"description": "Generation result ID of the original image"
}
}
},
"annotations": {
"title": "Save Retouched Image",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
},
"title": "Save Retouched Image"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.uwear/uwear"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.uwear/uwear"}) over MCP.
upload_avatar_from_chat_file ~1,999 tokensupdate_brief ~1,931 tokenspropose_brief ~1,730 tokensmcp_edit_brief ~1,670 tokenssave_reference_file_from_chat_file ~1,628 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.uwear%2Fuwear?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.uwear%2Fuwear?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.uwear%2Fuwear.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.uwear%2Fuwear.svg :target: https://glimind.com/server/mcp-registry%2Fai.uwear%2Fuwear?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d54b1d4d3974b582…, first seen 2026-10-17, included at leaf 13996 of 40,195. Version history · verify what your client received.
Compare: most reliable media servers · most reliable other servers · most reliable files servers · most reliable data servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 15:11 UTC, the Uwear MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Uwear MCP server advertises 70 tools, including add_chat_photos_to_board, confirm_brief, create_location, create_tag, get_art_direction.
Point your MCP client at this streamable-http endpoint: https://api.uwear.ai/mcp
Glimind scanned all 70 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.