Cronus UI
REMOTE · AICRONUS.COM · 2 COMPONENTS · SCANNED SEP 20
Search, install, compose, add-page, and theme Cronus UI from the live registry.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 972 tokens (~97/item across 10 items; 8 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · aicronus.com
claude mcp add --transport http pedrogbraz-cronus-ui 'https://aicronus.com/mcp'
{
"mcpServers": {
"pedrogbraz-cronus-ui": {
"url": "https://aicronus.com/mcp"
}
}
} {
"servers": {
"pedrogbraz-cronus-ui": {
"type": "http",
"url": "https://aicronus.com/mcp"
}
}
} [mcp_servers.pedrogbraz-cronus-ui] url = "https://aicronus.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pedrogbraz-cronus-ui": {
"type": "remote",
"url": "https://aicronus.com/mcp",
"enabled": true
}
}
} openclaw mcp add pedrogbraz-cronus-ui --url 'https://aicronus.com/mcp' --transport streamable-http
mcp_servers:
pedrogbraz-cronus-ui:
url: "https://aicronus.com/mcp" {
"McpServers": {
"pedrogbraz-cronus-ui": {
"Transport": "http",
"Url": "https://aicronus.com/mcp"
}
}
} assistant mcp add pedrogbraz-cronus-ui -t streamable-http -u 'https://aicronus.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 10 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 9 Sept 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://aicronus.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.aicronus.com | CN=YR1,O=Let's Encrypt,C=US | 1 Sept 2026 | 30 Nov 2026 | RSA 2048 | SHA256-RSA | 69a48415f2c40b58c0788ded320ac2e84a0 |
| SANs: *.aicronus.com, aicronus.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aicronus.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aicronus.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aicronus.com/mcp | Verified | 200 | |
| http (plaintext) | http://aicronus.com/mcp | HTTPS enforced | 308 | https://aicronus.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_component Get a Cronus UI component or block ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The exact registry item name, e.g. 'button', 'data-table', or 'pricing'. |
No output schema declared.
No examples provided.
get_design_context Get Cronus UI DESIGN.md taste ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_install_command Build a Cronus UI install command ~84
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | One or more registry item names to install, e.g. ['button', 'card', 'dialog']. |
No output schema declared.
No examples provided.
list_blocks List Cronus UI blocks ~66
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_catalog List the tagged Cronus UI catalog ~96
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.).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Restrict to component, block, variant, or template cards. |
No output schema declared.
No examples provided.
list_components List Cronus UI components ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
match_catalog Match Cronus UI catalog tags ~257
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
search_registry Search the Cronus UI registry ~67
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search text matched against component and block names, e.g. 'button' or 'card'. |
No output schema declared.
No examples provided.
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.