# Cronus UI (remote · aicronus.com)

Search, install, compose, add-page, and theme Cronus UI from the live registry.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `aicronus.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/pedrogbraz-cronus-ui/aicronus.md), [page](https://verifymcp.io/servers/pedrogbraz-cronus-ui/aicronus)
- npm · `cronus-ui-mcp`: 77/100, [markdown](https://verifymcp.io/servers/pedrogbraz-cronus-ui/cronus-ui-mcp.md), [page](https://verifymcp.io/servers/pedrogbraz-cronus-ui/cronus-ui-mcp)

## Channel facts

- Endpoint: `https://aicronus.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.6`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 972 tokens (~97/item across 10 items; 8 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Cronus UI MCP server?

Cronus UI is a hosted endpoint at https://aicronus.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.pedrogbraz-cronus-ui]
url = "https://aicronus.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pedrogbraz-cronus-ui": {
      "type": "remote",
      "url": "https://aicronus.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pedrogbraz-cronus-ui --url 'https://aicronus.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pedrogbraz-cronus-ui:
    url: "https://aicronus.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pedrogbraz-cronus-ui": {
      "Transport": "http",
      "Url": "https://aicronus.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pedrogbraz-cronus-ui -t streamable-http -u 'https://aicronus.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-09 (score 69)

First indexed and scored.

## MCP tools (8)

### `list_components` (~59 tokens)

List Cronus UI 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 dependencies, and the `npx cronus-ui add <name>` command to install it.

### `list_blocks` (~66 tokens)

List Cronus UI blocks

List the installable Cronus UI blocks (registry items of type 'registry:block') — larger, composed sections such as hero, pricing, login, and dashboard. Returns each block's name, title, dependencies, and its `npx cronus-ui add <name>` install command.

### `list_catalog` (~96 tokens)

List the tagged Cronus UI catalog

Return compact Hydra-ready cards for every component, block, variant, and template: name, short description, design style, palette, motion, intents, and the install command. No source files — cheap on tokens. Filter with `kind`. Use `match_catalog` to pick the best item for a prompt (login + smooth animation, etc.).

Input parameters:

- `kind` (string): Restrict to component, block, variant, or template cards.

### `match_catalog` (~257 tokens)

Match Cronus UI catalog tags

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`, `style`, `palette`). Returns `pick` (the recommended combination), `intent` hits, `motion` hits, and ranked `matches`. Cards carry description, design style, palette, motion, and intents — not source. Fetch source with `get_component` only after picking a name.

Input parameters:

- `intent` (string): Use-case intent: login, signup, pricing, dashboard, chart, form, …
- `kind` (string): Restrict to component, block, variant, or template.
- `limit` (integer): Max hits per list. Default 8.
- `motion` (string): Motion: none, snappy, smooth, cinematic.
- `palette` (string): Palette: semantic (follows theme), aurora, neutral, midnight, sunset, emerald.
- `query` (string): Natural-language request, e.g. 'login page with smooth animation'. Intent and motion are inferred from the text when those fields are omitted.
- `style` (string): Design style: default, editorial, operational, glass, brutalist.

### `search_registry` (~67 tokens)

Search the Cronus UI 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_component`.

Input parameters:

- `query` (string, required): Search text matched against component and block names, e.g. 'button' or 'card'.

### `get_design_context` (~139 tokens)

Get Cronus UI DESIGN.md taste

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 primary CTA, hairline elevation, and look rules. compact fits a system prompt; extended is the repo file. Does not modify the project.

Input parameters:

- `format` (string): compact (~prompt) or extended (full DESIGN.md). Default extended.
- `look` (string): Material: default, brutalist, or glass. Orthogonal to theme.
- `theme` (string): Palette: aurora (generated product), neutral (docs chrome), midnight, sunset, emerald.

### `get_component` (~99 tokens)

Get a Cronus UI component or block

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` (other registry items it needs), and the `npx cronus-ui add <name>` install command. Works for both components and blocks.

Input parameters:

- `name` (string, required): The exact registry item name, e.g. 'button', 'data-table', or 'pricing'.

### `get_install_command` (~84 tokens)

Build a Cronus UI 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 only returns the command string — to actually install, use `install_component`.

Input parameters:

- `names` (array, required): One or more registry item names to install, e.g. ['button', 'card', 'dialog'].

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pedrogbraz-cronus-ui/aicronus#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69

## Common questions

### What is the Cronus UI MCP server?

Cronus UI is an MCP server listed in the public MCP registry as io.github.pedrogbraz/cronus-ui. Search, install, compose, add-page, and theme Cronus UI from the live registry. This page covers its hosted endpoint (https://aicronus.com/mcp).

### Is the Cronus UI MCP server safe to use?

Cronus UI scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Cronus UI MCP server expose?

Cronus UI exposes 8 tools: list_components, list_blocks, list_catalog, match_catalog, search_registry, and 3 more. Their descriptions and schemas cost roughly 867 tokens of context every time the server is loaded.

### Does the Cronus UI MCP server require authentication?

No. We connected to Cronus UI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Cronus UI MCP server still maintained?

Cronus UI is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://aicronus.com/mcp
- Repository: https://github.com/pedrogbraz/cronus-ui
- Website: https://aicronus.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/pedrogbraz-cronus-ui/aicronus.xml
- Changelog JSON feed: https://verifymcp.io/servers/pedrogbraz-cronus-ui/aicronus.json
- HTML version of this page: https://verifymcp.io/servers/pedrogbraz-cronus-ui/aicronus