# Pedrogbraz Cronus Ui MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.pedrogbraz%2Fcronus-ui
Registry id: `mcp-registry/io.github.pedrogbraz/cronus-ui`
Status: live (checked 2026-10-27T07:00:38.218Z)

## Verdict

Pedrogbraz Cronus Ui MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 862 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 8 tools, costing an agent about 1,464 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 862 ms | 23% of MCP servers |
| p95 handshake latency | 2911 ms | — |
| Checks in 30 days | 5,033 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 8 | — |
| Tool-list size for an agent | ~1,464 tokens | 59% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "pedrogbraz-cronus-ui-mcp-server": {
      "type": "http",
      "url": "https://aicronus.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http pedrogbraz-cronus-ui-mcp-server https://aicronus.com/mcp
```

## Tools (8)

- `get_component`: Fetch the full detail for a single Cronus UI component or block by name: its source file(s) (path + content), its npm `dependencies`, its `registryDependencies`
- `get_design_context`: Return the Cronus UI visual taste file (DESIGN.md) for a theme × look. Use this before generating UI so the agent follows Aurora/Neutral dual identity, one prim
- `get_install_command`: Build the `npx cronus-ui add ...` command for one or more components/blocks. The CLI resolves and installs each item's registry dependencies automatically. This
- `list_blocks`: List the installable Cronus UI blocks (registry items of type 'registry:block') — larger, composed sections such as hero, pricing, login, and dashboard. Returns
- `list_catalog`: Return compact Hydra-ready cards for every component, block, variant, and template: name, short description, design style, palette, motion, intents, and the ins
- `list_components`: List the installable Cronus UI components (registry items of type 'registry:ui'). Returns each component's name, a readable title, its npm and registry dependen
- `match_catalog`: Two-query catalog match for low-context agents. Pass a free-text `query` (e.g. 'login page with smooth animation') and/or structured filters (`intent`, `motion`
- `search_registry`: Fuzzy-search Cronus UI components and blocks by name (case-insensitive substring match). Use this to find the right item before fetching its source with `get_co

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.