Registry MCP Server

by crucibleui Your server? Claim it

not responding

Registry is listed as active in the registry but did not answer our last check. It exposes 4 tools.

Browse and install Crucible's animated React components into shadcn-style projects.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 0%

91 days agonow

3.3%

Uptime 24h

3 of 91 checks

Tools

read from the server

406 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 October 2026. No other catalogue keeps this.

18 Oct a tool changed the parameters it asks for search_registry

Registry does not always answer

Over the last week it answered 3.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add registry --transport http https://crucibleui.com/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://crucibleui.com/api/mcp

~/.codex/config.toml

[mcp_servers.registry]
url = "https://crucibleui.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "registry": {
      "url": "https://crucibleui.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "registry": {
      "type": "http",
      "url": "https://crucibleui.com/api/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

component

get_component

Fetch the full TypeScript source of a Crucible component, ready to drop into a shadcn-style project. Pro components require an Authorization: Bearer <CRUCIBLE_TOKEN> header (get a token at https://crucibleui.com/account).

install

install_instructions

How to install a Crucible component into a project: shadcn CLI command, registry config, and npm dependencies.

registry

search_registry

Search Crucible's animated React components by keyword, category, or tier. Returns names, descriptions, and dependencies. Use get_component to fetch source.

usage

get_usage

Show how to USE a Crucible component correctly: a worked example (its demo source) plus the conventions that make it render — notably the `relative isolate` wrapper that background components require. Call this before writing integration code so the install actually renders.

Endpoints

URL	Transport	State	Latency	Checked
https://crucibleui.com/api/mcp	streamable-http	answering	67 ms	13 min ago

Alternatives to Registry

same job, measured the same way

Aicanvas

by aicanvas-me

Browse and install 75+ free animated, shadcn-compatible React components from AI Canvas.

local only

uibrik

by uibrik

Search 267 animated React components and get their props and source to install with shadcn.

4 tools answering

Wensity

by wensity

Find, plan, and install Wensity UI React components and blocks into your project.

129 installs/wk local only

Arc UI

by uiarc

React components and blocks with motion. Search docs, props and shadcn install commands.

5 tools answering

PixilUI components

by pixilui

Search and install PixilUI React components for AI product UI into your app.

6 tools answering

UpFork

by upfork

Verified lessons for your project's packages and versions, and free React components to install.

8 tools answering

UI Beats

by uibeats

MCP server for UI Beats. Let your coding agent search, read and install animated React components.

75 installs/wk local only

tealmac UI

by tealmac

Search shadcn registry items, read props and get exact install commands for React components.

11 tools answering

Registry — questions

Answers built from our own checks of this server.

What can Registry do?

It exposes 4 tools, read directly from the server on our last check. Among them: get_component, get_usage, install_instructions, search_registry. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Registry working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 3 of 91 checks got a reply (3.3%), average response time 406 ms. The bar chart above shows every period we have measured.

Is Registry still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Registry as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Registry?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Registry need an API key?

No. Registry completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Registry?

It answers our handshake in 406 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.