cronus-ui-mcp

MCPcommunitylive

v0.7.6CronusMITUpdated 2d agonpm GitHub

Model Context Protocol server for Cronus UI — lets MCP-compatible AI agents discover and fetch Cronus UI components and blocks from the registry.

Endpoint healthlive

checked 2h ago · 279ms

100% of the last 1 check reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

835Downloads/wk

1GitHub stars

2d agoLast update

Package

AuthorCronus

LicenseMIT

Version0.7.6

Sourcenpm+mcp-registry

npmcronus-ui-mcp

GitHubpedrogbraz/cronus-ui

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface14 tools · 2 privileged

Security scan✓ Cleanv0.7.6 · todayHow well does this scan work?

EvalsNone

IndexedSep 12, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

14 tools · 2 privileged

Statically extracted from the published packagev0.7.6 · 2h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

list_componentsList the installable Cronus UI components (registry items of type 'registry:ui').

List the installable Cronus UI components (registry items of type 'registry:ui').

No input schema was published for this tool.

list_blocksList the installable Cronus UI blocks (registry items of type 'registry:block') —

List the installable Cronus UI blocks (registry items of type 'registry:block') —

No input schema was published for this tool.

list_catalogReturn compact Hydra-ready cards for every component, block, variant, and template:

Return compact Hydra-ready cards for every component, block, variant, and template:

No input schema was published for this tool.

match_catalogTwo-query catalog match for low-context agents. Pass a free-text `query`

Two-query catalog match for low-context agents. Pass a free-text `query`

No input schema was published for this tool.

search_registryFuzzy-search Cronus UI components and blocks by name (case-insensitive substring match).

Fuzzy-search Cronus UI components and blocks by name (case-insensitive substring match).

No input schema was published for this tool.

get_design_contextReturn the Cronus UI visual taste file (DESIGN.md) for a theme × look.

Return the Cronus UI visual taste file (DESIGN.md) for a theme × look.

No input schema was published for this tool.

get_componentFetch the full detail for a single Cronus UI component or block by name: its source

Fetch the full detail for a single Cronus UI component or block by name: its source

No input schema was published for this tool.

get_install_commandprivilegedBuild the `npx cronus-ui add ...` command for one or more components/blocks. The CLI

Build the `npx cronus-ui add ...` command for one or more components/blocks. The CLI

No input schema was published for this tool.

install_componentprivilegedMODIFIES THE FILESYSTEM. Install one or more Cronus UI components/blocks into the

MODIFIES THE FILESYSTEM. Install one or more Cronus UI components/blocks into the

No input schema was published for this tool.

upgrade_componentsMODIFIES THE FILESYSTEM. Upgrade installed Cronus UI components and composed pages/layouts

MODIFIES THE FILESYSTEM. Upgrade installed Cronus UI components and composed pages/layouts

No input schema was published for this tool.

apply_themeMODIFIES THE FILESYSTEM. Apply a theme built in the Cronus UI Create Studio to the

MODIFIES THE FILESYSTEM. Apply a theme built in the Cronus UI Create Studio to the

No input schema was published for this tool.

compose_appMODIFIES THE FILESYSTEM. Generate a full multi-page app from a validated Cronus UI

MODIFIES THE FILESYSTEM. Generate a full multi-page app from a validated Cronus UI

No input schema was published for this tool.

add_pageMODIFIES THE FILESYSTEM. Grow an already-composed app by one page: install the

MODIFIES THE FILESYSTEM. Grow an already-composed app by one page: install the

No input schema was published for this tool.

set_themeMODIFIES THE FILESYSTEM. Switch the baked-in Cronus UI theme preset (and optionally

MODIFIES THE FILESYSTEM. Switch the baked-in Cronus UI theme preset (and optionally

No input schema was published for this tool.

14 of 14 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Model Context Protocol server for Cronus UI — lets MCP-compatible AI agents discover and fetch Cronus UI components and blocks from the registry.

Keywords

cronuscomponentsdesign-systemregistrymcpmodel-context-protocolshadcntailwindui

Alternatives

Comparing tool surfaces…

Tools exposed

14 tools · 2 privileged · observed 2026-09-12 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-12 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.6.2
@cronus-ui/tokens0.7.6
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.7
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.2shown above
- cors2.8.6+1 not drawn1 dependency
  - object-assign4.1.1
- hono4.13.7
- jose6.2.12
- express5.2.1+27 not drawn1 dependency
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 49
below the depth cap: 5

wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in design tools

nextlevelbuilder/ui-ux-pro-max-skillAn AI SKILL that provide design intelligence for building professional UI/UX multiple plat
nexu-io/open-design🎨 Local-first, open-source Claude Design alternative. 🖥️ Native desktop app. ⚡ 259+ Skil
Leonxlnx/taste-skillTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop
Donchitos/Claude-Code-Game-StudiosTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a com
GLips/Figma-Context-MCPMCP server to provide Figma layout information to AI coding agents like Cursor
grab/cursor-talk-to-figma-mcpTalkToFigma: MCP integration between AI Agent (Cursor, Claude Code) and Figma, allowing Ag
nexu-io/html-anything✨ The agentic HTML editor — your local AI agent writes the HTML, you ship it. 🚀 75 Skills
figma-developer-mcpGive your coding agent access to your Figma data. Implement designs in any framework in on