Cronus UI
NPM · CRONUS-UI-MCP · 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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- 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
- Context-footprint check failed: tool/resource definitions use about 2498 tokens (~156/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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 runs locally as an npm package, launched with npx -y cronus-ui-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cronus-ui-mcp
claude mcp add pedrogbraz-cronus-ui -- npx -y cronus-ui-mcp
{
"mcpServers": {
"pedrogbraz-cronus-ui": {
"command": "npx",
"args": [
"-y",
"cronus-ui-mcp"
]
}
}
} {
"servers": {
"pedrogbraz-cronus-ui": {
"command": "npx",
"args": [
"-y",
"cronus-ui-mcp"
]
}
}
} codex mcp add pedrogbraz-cronus-ui -- npx -y cronus-ui-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pedrogbraz-cronus-ui": {
"type": "local",
"command": [
"npx",
"-y",
"cronus-ui-mcp"
],
"enabled": true
}
}
} openclaw mcp add pedrogbraz-cronus-ui --command npx --arg -y --arg cronus-ui-mcp
mcp_servers:
pedrogbraz-cronus-ui:
command: "npx"
args: ["-y", "cronus-ui-mcp"] {
"McpServers": {
"pedrogbraz-cronus-ui": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"cronus-ui-mcp"
]
}
}
} assistant mcp add pedrogbraz-cronus-ui -t stdio -c npx -a -y cronus-ui-mcp
{
"mcpServers": {
"pedrogbraz-cronus-ui": {
"command": "npx",
"args": [
"-y",
"cronus-ui-mcp"
]
}
}
} 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 +4
- Stability: unverified → 0.30 ▲ functional
- 9 Sept 26 72
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 · Analysed npm/cronus-ui-mcp@0.7.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_page Add a page to a composed Cronus UI app ~358
MODIFIES THE FILESYSTEM. Grow an already-composed app by one page: install the named blocks, write a generated page that stacks them in <main>, and update the chrome nav + composed record. Runs the version-pinned `cronus-ui add-page` CLI at the detected project root. Use after `compose_app` when the user wants a new route. Set `dryRun` to preview without writing. Pass `app` (`--app`) when the project has more than one composed app. Pass `manifest` when the app was composed from a custom `--manifest`.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Composed app key (`--app`). Required when the project has more than one composed app. |
| blocks | string | yes | Comma-separated block slugs to stack, e.g. 'pricing,cta'. Variant syntax 'login=split' is allowed. |
| chrome | string | – | Chrome group for the page (default: the app's first group). |
| dryRun | boolean | – | Preview the plan without writing any files. |
| manifest | string | – | Path to the compose manifest file (`--manifest`). Required when the app was composed from a custom `--manifest` whose name collides with a bundled template (or is not a bundled template). |
| nav | string | – | Nav label; adds the page to the chrome nav. |
| overwrite | boolean | – | Replace the page if the route already exists (`--overwrite`). |
| route | string | yes | Route to add, starting with '/', e.g. '/pricing'. |
| skipInstall | boolean | – | Write the files but skip the package-manager install of npm dependencies. |
| title | string | – | Page <title> (default: title-cased route). |
No output schema declared.
No examples provided.
apply_theme Apply a Cronus UI theme to the project ~169
MODIFIES THE FILESYSTEM. Apply a theme built in the Cronus UI Create Studio to the current project by running the version-pinned `cronus-ui theme add` CLI at the detected project root. It updates the app layout's theme attributes, writes the theme override block into the global stylesheet (replacing any previous one), and records the theme in cronus-ui.json. Use this when the user provides a Create Studio permalink or an exported theme JSON file and wants it applied. Set `dryRun` to preview the changes without writing anything.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Preview what would change without writing any files. |
| source | string | yes | The theme to apply: a Create Studio permalink URL, a bare `c=` payload, or a path to an exported theme JSON file. |
No output schema declared.
No examples provided.
compose_app Compose a Cronus UI app from a template ~315
MODIFIES THE FILESYSTEM. Generate a full multi-page app from a validated Cronus UI template (saas, store, landing, landing-*, mail, chat, finance) by running the version-pinned `cronus-ui compose` CLI at the detected project root. Prefer this over hand-writing pages: it installs the template's blocks, writes route files that only stack those blocks in <main>, and records the app in cronus-ui.json. Use when the user wants a full product, not a single primitive. Set `dryRun` to preview without writing. Requires a project initialised with `npx cronus-ui init` — this does not scaffold a new app (use `npx create-cronus-app` for greenfield).
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Brand wordmark baked into chrome/hero. Ignored when empty. |
| dryRun | boolean | – | Preview the validated plan without writing any files. |
| overwrite | boolean | – | Overwrite files that already exist (`--overwrite`). |
| skipInstall | boolean | – | Write the files but skip the package-manager install of npm dependencies. |
| template | string | yes | Bundled app template (saas, store, landing, landing-*, mail, chat, finance). |
| variant | array | – | Block variant selections as slug=id tokens, e.g. ['login=split']. Each becomes `--variant <token>`. |
| yes | boolean | – | Pass `-y` (non-interactive). Defaults to true so agents never hang. |
No output schema declared.
No examples provided.
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.
install_component Install Cronus UI components into the project ~232
MODIFIES THE FILESYSTEM. Install one or more Cronus UI components/blocks into the current project by running the version-pinned `cronus-ui add` CLI at the detected project root (nearest directory with cronus-ui.json, else package.json). It writes the component source files, pulls in their registry dependencies, and installs their npm packages with the project's package manager. Use this — not a shell command — whenever the user asks to add/install a Cronus UI component or block. Existing files are skipped unless `overwrite` is true (overwrite discards local edits to those files). Requires a project initialised with `npx cronus-ui init`.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Registry item names to install, e.g. ['button', 'card'] or ['pricing']. Registry dependencies are resolved automatically. |
| overwrite | boolean | – | Overwrite files that already exist in the project (destroys local edits to those files). Default: existing files are skipped. |
| skipInstall | boolean | – | Write the source files but skip the package-manager install of npm dependencies; the result then lists them as pending. |
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.
set_theme Set the Cronus UI theme preset ~137
MODIFIES THE FILESYSTEM. Switch the baked-in Cronus UI theme preset (and optionally the color mode) by running the version-pinned `cronus-ui theme set` CLI at the detected project root. Use this for aurora / neutral / midnight / sunset / emerald. For Create Studio permalinks or exported JSON, use `apply_theme` instead.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Color mode to pin ('dark' or 'light'). Omitting leaves the current mode. |
| name | string | yes | Baked-in preset: 'aurora', 'neutral', 'midnight', 'sunset', or 'emerald'. |
No output schema declared.
No examples provided.
upgrade_components Upgrade installed Cronus UI components and composed pages ~315
MODIFIES THE FILESYSTEM. Upgrade installed Cronus UI components and composed pages/layouts to the current registry release by running the version-pinned `cronus-ui upgrade` CLI at the detected project root. 3-way merge of installed items AND composed pages/layouts so local edits survive. Prefer this over install_component overwrite and over compose --overwrite. dryRun first is recommended. Defaults to `--all` when `names` is omitted (the usual "pull latest" request). Pass `manifest` for custom compose apps. Requires a project initialised with `npx cronus-ui init`.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Upgrade every installed component and composed pages/layouts (`--all`). Default when `names` is empty. Set false only when passing `names`. |
| dryRun | boolean | – | Preview the per-file plan (fast-forward / merge / conflict) without writing. |
| manifest | string | – | Path to the compose manifest file (`--manifest`). Required when the app was composed from a custom `--manifest` whose name collides with a bundled template (or is not a bundled template). |
| names | array | – | Registry item names to upgrade, e.g. ['button', 'card']. Omit (and leave `all` unset or true) to upgrade every installed component and composed pages/layouts. Named upgrades do not touch pages. |
| yes | boolean | – | Pass `-y`: write conflict markers and confirmed overwrites without asking. Unlike compose_app, this does not default to true. |
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 npm package (cronus-ui-mcp).
Is the Cronus UI MCP server safe to use?
Cronus UI scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 14 tools: list_components, list_blocks, list_catalog, match_catalog, search_registry, and 9 more. Their descriptions and schemas cost roughly 2,393 tokens of context every time the server is loaded.
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.
What licence is the Cronus UI MCP server under?
Cronus UI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.