Loading ToolBench
MCP server for Uiverse.io — browse, search, and fetch 3,800+ open-source UI components (buttons, cards, loaders, inputs, and more) directly in Claude Code, Cursor, Codex, or any MCP-compatible agent.
Strong tool naming (all verb-first: list_, search_, get_, refresh_, cache_). Descriptions are clear and actionable (avg 180 chars, within 10-1024 baseline). All 7 tools have explicit input schemas with proper JSON Schema structure. Parameters are well-constrained (enums for categories, min/max for pagination). However, output schemas are not formally documented, responses are described in prose only. Error handling guidance is minimal. No tool annotations (readOnlyHint/destructiveHint) despite clear risk profiles.
Report cache metadata: last sync time, current commit SHA, total components indexed, per-category counts. Use to debug sync issues.
Fetch the full HTML + CSS of a specific component by category + id. Returns markup, CSS (or note if Tailwind-based), tags, author, preview URL. Use after browsing with list_components or search_components.
Return the public uiverse.io URL for visual preview of a component. Open this in a browser to see the component rendered with animations. Does NOT fetch HTML — use get_component for code.
List all Uiverse component categories with their component counts. Categories: Buttons, Cards, Checkboxes, Forms, Inputs, Notifications, Patterns, Radio-buttons, Toggle-switches, Tooltips, loaders. Call this first when you don't know what's available.
List components in a specific category with pagination. Returns summaries only (id, author, name, tags, preview_url) — no HTML payload. Call get_component to fetch actual HTML/CSS for a specific component. Optional: filter by author.
Output schemas not formally documented. Descriptions mention 'Returns markup, CSS, tags, author, preview URL' but no JSON Schema or structured field definitions provided. LLMs cannot reliably extract fields or plan downstream calls.
No tool annotations (readOnlyHint/destructiveHint/idempotentHint) despite clear risk profiles. refresh_cache is marked WRITE but tool definition lacks destructiveHint. All READ_ONLY tools lack readOnlyHint annotation.
Error handling guidance absent. No recovery hints in descriptions (e.g., 'If component not found, try search_components'). No documented error codes or categorization (retryable vs. user-fixable vs. fatal).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
Pull the latest commits from the uiverse-io/galaxy repo and rebuild the in-memory index. Use when you suspect the cache is stale (last sync > 1 week). Returns commit SHA delta and new total count.
Fuzzy search components by name, tags, or author. Returns top matches as summaries (no HTML). Use this when the user asks for a specific style like 'glowing button', 'glass card', 'ripple loader'. Optional category filter narrows the search.
refresh_cache description lacks clarity on side effects and prerequisites. Does it require git credentials? Can it fail? What happens if the galaxy repo is unreachable? Agents need explicit state-change documentation.
Parameter descriptions for 'id' in get_component and get_component_preview are minimal ('Component id (filename without .html)'). Should clarify format constraints and how to obtain valid IDs from prior calls.