A
licenseNot graded
qualityB
maintenanceEnables AI agents to create and manage consistent multi-screen UI designs through a token-efficient MCP interface, with design system tokens, components, flows, and visual review.
277
AGPL 3.0
Uizze
Server Details
Focused full-screen UI references and hosted design materials for coding agents.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- uizze/uizze
- GitHub Stars
- 0
- Server Listing
- UIZZE
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
check_ui_slop11 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / cssAdded value: +{ + "description": "CSS source to check.", + "maxLength": 150000, + "type": "string" +} - removed
Input schema / properties / designSystemNotesRemoved value: -{ - "description": "Short notes about the product design system and constraints.", - "maxLength": 1000, - "type": "string" -} - removed
Input schema / properties / implementationCssRemoved value: -{ - "description": "CSS or class-heavy source excerpt. Provide this or implementationHtml.", - "maxLength": 30000, - "type": "string" -} - removed
Input schema / properties / implementationHtmlRemoved value: -{ - "description": "Rendered HTML or component markup. Provide this or implementationCss.", - "maxLength": 30000, - "type": "string" -} - added
Input schema / properties / markupAdded value: +{ + "description": "Rendered HTML or JSX source to check.", + "maxLength": 150000, + "type": "string" +} - removed
Input schema / properties / platformRemoved value: -{ - "description": "Optional target platform.", - "enum": [ - "ios", - "web" - ], - "type": "string" -} - removed
Input schema / properties / requiredStatesRemoved value: -{ - "description": "Relevant states the implementation must cover.", - "items": { - "maxLength": 60, - "minLength": 1, - "type": "string" - }, - "maxItems": 12, - "type": "array" -} - removed
Input schema / properties / taskRemoved value: -{ - "description": "What the interface is supposed to help the user accomplish.", - "maxLength": 300, - "minLength": 1, - "type": "string" -} - removed
Input schema / requiredRemoved value: -[ - "task" -] - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "checks": { + "additionalProperties": false, + "properties": { + "deterministic": { + "enum": [ + "passed", + "issues" + ], + "type": "string" + }, + "visual": { + "const": "not_run", + "type": "string" + } + }, + "required": [ + "deterministic", + "visual" + ], + "type": "object" + }, + "findings": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "enum": [ + "layout", + "responsive", + "interaction", + "state", + "accessibility", + "runtime", + "hierarchy", + "genericity", + "design_system", + "privacy" + ], + "type": "string" + }, + "confidence": { + "enum": [ + "high", + "medium", + "low" + ], + "type": "string" + }, + "evidence": { + "maxLength": 500, + "minLength": 1, + "type": "string" + }, + "fix": { + "maxLength": 500, + "minLength": 1, + "type": "string" + }, + "id": { + "pattern": "^finding_[a-f0-9]{20}$", + "type": "string" + }, + "region": { + "additionalProperties": false, + "properties": { + "height": { + "exclusiveMinimum": 0, + "type": "number" + }, + "width": { + "exclusiveMinimum": 0, + "type": "number" + }, + "x": { + "minimum": 0, + "type": "number" + }, + "y": { + "minimum": 0, + "type": "number" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + }, + "selector": { + "maxLength": 500, + "minLength": 1, + "type": "string" + }, + "severity": { + "enum": [ + "blocker", + "major", + "minor", + "note" + ], + "type": "string" + }, + "source": { + "enum": [ + "visual", + "deterministic", + "runtime" + ], + "type": "string" + }, + "userImpact": { + "maxLength": 500, + "minLength": 1, + "type": "string" + }, + "view": { + "maxLength": 120, + "minLength": 1, + "type": "string" + } + }, + "required": [ + "severity", + "category", + "view", + "evidence", + "userImpact", + "fix", + "confidence", + "source" + ], + "type": "object" + }, + "maxItems": 3, + "type": "array" + }, + "kind": { + "const": "ui_slop_check", + "type": "string" + }, + "limitations": { + "items": { + "maxLength": 300, + "minLength": 1, + "type": "string" + }, + "maxItems": 3, + "type": "array" + }, + "schemaVersion": { + "const": "uizze.mcp.preview.v1", + "type": "string" + }, + "summary": { + "maxLength": 240, + "minLength": 1, + "type": "string" + }, + "verdict": { + "enum": [ + "pass", + "needs_fixes" + ], + "type": "string" + } + }, + "required": [ + "schemaVersion", + "kind", + "summary", + "verdict", + "checks", + "findings", + "limitations" + ], + "type": "object" +}
1 tool update
- Changed
check_ui_slop1 field changed- changed
Input schema / properties / platform / descriptionPrevious value: -"Target platform."New value: +"Optional target platform."
1 tool update
- First observed
check_ui_slop
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
UI design from prompts, screenshots, and URLs for AI coding agents and theme tokens.
Turns any agent into a full agentic application — branded, interactive screens generated at runtime.
Curated design references for AI — real CSS values, typography specs, and color palettes.
Measured design systems decoded from 588 real products, for coding agents.
Related MCP Servers
- AlicenseAqualityAmaintenancehe industry standard reference for safe, observable, and steerable AI agent UX. Browse and search 10 Blueprint principles, clusters, curated implementation examples, and application guides. 13 public tools require no credentials.293MIT
- AlicenseAqualityCmaintenanceTurns AI coding hosts into a guided mobile-UI design tool with design interviews, token contracts, linters, and local browser preview.814MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to turn CollectUI links or any image/GIF/video URL into a detailed design and motion brief with measured timings, easing curves, displacement, palette, and opt-in keyframes.31MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion. The tool's purpose is clearly specified.
Naming Consistency5/5
The name 'check_ui_slop' follows a clear verb_noun pattern, is descriptive, and there are no other names to conflict.
Tool Count3/5
One tool is borderline thin for a server named UIZZE, which implies a broader UI toolkit. However, the tool is highly specialized, so the count is acceptable but not robust.
Completeness3/5
The tool covers specific source-level risks but explicitly excludes visual and taste dimensions, leaving notable gaps in the UI slop domain. A more complete surface would include additional UI quality checks.