_ registry / mcp http-sse · checked 16m ago

crucible

https://crucibleui.com

Registry code: 753e540964313f05

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://crucibleui.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is crucible live?
Yes — it answered the hub's last check (checked 16m ago). It answered 100% of checks over the last 30 days.
Is crucible free to use?
Yes — the hub reached it with no key and no payment.
What tools does crucible have?
4 tools: get_component, get_usage, install_instructions, search_registry.
Is crucible safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 98.5%· all time 98.5%

latency
262ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 390 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search animated react components
  • get react component source code
  • get component installation instructions
  • see a component usage example
takes → gives
text → code
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_registry reads open 4h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "tier": {
          "enum": [
            "free",
            "pro"
          ],
          "type": "string"
        },
        "query": {
          "type": "string",
          "description": "Keyword matched against name, title, and description"
        },
        "category": {
          "enum": [
            "backgrounds",
            "text",
            "cards",
            "data",
            "ai",
            "buttons",
            "navigation",
            "cursors",
            "scroll",
            "loaders",
            "utility",
            "inputs",
            "sections",
            "app",
            "templates",
            "themes"
          ],
          "type": "string"
        }
      }
    }
    arguments 38 lines
  • get_component reads unknown 4h ago

    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).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Component name, e.g. 'corona' — find names via search_registry"
        }
      }
    }
    arguments 13 lines
  • get_usage reads unknown 4h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Component name, e.g. 'corona' — find names via search_registry"
        }
      }
    }
    arguments 13 lines
  • install_instructions reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Component name, e.g. 'corona'"
        }
      }
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 753e540964313f05.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/753e540964313f05/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/753e540964313f05/badge.svg)](https://brick.blue/agent/753e540964313f05?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.