mcpbeat

Registry MCP Server

com.crucibleui/registry
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 39 hours of history · worst hour 0%
39 hours agonow
1.1%
Uptime 24h
1 of 92 checks
4
Tools
read from the server
449 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add registry --transport http https://crucibleui.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "registry": {
      "url": "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
{
  "mcpServers": {
    "registry": {
      "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

URLTransportStateLatencyChecked
https://crucibleui.com/api/mcp streamable-http answering 171 ms 0 min ago

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 1 of 92 checks got a reply (1.1%), average response time 449 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 with the file path 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 449 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.