_ registry / mcp http-sse · checked 1h ago

assembli

https://www.assembli.design

Registry code: 97e634e22a3648ea

api record

A library of React and Tailwind components. Preview them, copy the code, or install with the shadcn CLI. Built for humans and coding agents. Search with search_components, then call get_component for source and install steps. Install with the shadcn CLI command it returns. The user's systems (saved sets of components) are in list_systems and get_system; build one with create_system and edit_system. Source needs an API key: if you don't have one, call connect_account and ask the user to approve the link it returns.

endpoint
https://www.assembli.design/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 assembli live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is assembli free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does assembli have?
9 tools: get_component, connect_account, finish_connect, get_system, create_system, edit_system, search_components, list_categories, ….
Is assembli 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
100%

90 days 100%· all time 100%

latency
374ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 9 tools
2 open1 auth-required 6 never probed 3 of 9 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_components open 1h ago

    Search the Assembli component library (React + Tailwind + shadcn/ui). Returns matching components with slugs, descriptions, URLs and a thumbnail image of each (1200×900 PNG, light and dark). Use get_component with a slug for its props, source code and install command.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "tag": {
      "type": "string",
      "description": "Restrict to components with this tag."
    },
    "kind": {
      "enum": [
        "component",
        "block",
        "asset"
      ],
      "type": "string",
      "description": "'component' for UI pieces, 'block' for sections and full pages, 'asset' for 3D asset packs and icon sets."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "default": "",
      "description": "Free text, e.g. 'pricing toggle' or 'animated button'. Empty lists everything."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Skip this many results: pass the previous call's nextOffset for the next page."
    },
    "system": {
      "type": "string",
      "minLength": 1,
      "description": "Only search within this system of the user's (see list_systems)."
    },
    "category": {
      "enum": [
        "landing-pages",
        "asset-packs",
        "icons",
        "heroes",
        "features",
        "bento-grids",
        "pricing",
        "testimonials",
        "calls-to-action",
        "logos",
        "stats",
        "faqs",
        "team",
        "blog",
        "contact",
        "footers",
        "navigation",
        "backgrounds",
        "text-effects",
        "marquees",
        "timelines",
        "3d",
        "buttons",
        "inputs",
        "selects",
        "forms",
        "authentication",
        "sliders",
        "pickers",
        "cards",
        "dialogs",
        "menus",
        "tabs",
        "steppers",
        "toggles",
        "checkboxes",
        "badges",
        "chips",
        "avatars",
        "accordions",
        "tables",
        "charts",
        "numbers",
        "loaders",
        "toasts",
        "notifications",
        "alerts",
        "empty-states",
        "ai-chat",
        "sidebars",
        "carousels",
        "calendars",
        "popovers",
        "pagination",
        "media",
        "code"
      ],
      "type": "string",
      "description": "Restrict to one category slug (see list_categories)."
    },
    "subcategory": {
      "enum": [
        "saas",
        "ai",
        "product",
        "ecommerce",
        "portfolio",
        "agency",
        "home-services",
        "hospitality",
        "health",
        "finance",
        "education",
        "real-estate",
        "events",
        "nonprofit",
        "objet",
        "lumen",
        "orbit",
        "morsel",
        "jaunt",
        "tinsel",
        "sunday",
        "boo",
        "gizmo",
        "sol",
        "vitro",
        "hamlet",
        "bloop",
        "rawr",
        "flux",
        "optic",
        "runnel",
        "sheen",
        "taffy",
        "kami",
        "mote",
        "bijou",
        "plume",
        "offset",
        "argon",
        "keyline"
      ],
      "type": "string",
      "description": "Restrict to one type within a category, e.g. 'saas' or 'portfolio' landing pages (see list_categories)."
    }
  }
}
    arguments 150 lines
  • list_categories open 1h ago

    List component categories with descriptions and how many components each contains. Categories with types (landing pages: SaaS, portfolio, home services…) list them with counts.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • list_systems auth-required 1h ago

    List the user's systems: named sets of Assembli components they've saved for a project or style, e.g. 'Fintech dashboard'. Bookmarks is the default one. Systems with a `team` are shared with the user's team, and every member can edit them. Returns ids, names, descriptions and component slugs. Use get_system for details and one install command for a whole system. Without an account, call connect_account first.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "query": {
      "type": "string",
      "description": "Filter by system name or description, or by the components in it."
    }
  }
}
    arguments 10 lines
  • get_component unknown never probed

    Get one component by slug: metadata, full source code of the component and its usage demo, npm and shadcn/ui dependencies and shadcn CLI install commands. Source needs an Assembli API key (subscription) sent as `Authorization: Bearer <key>`; without one, the result has metadata only.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Component slug from search_components, e.g. 'pricing-cards'."
    }
  }
}
    arguments 13 lines
  • connect_account unknown never probed

    Start device login to get an API key without the user copying one. Returns a link and a code: show both to the user and ask them to approve, then call finish_connect with the device_code. The user signs in, approves and subscribes if needed; you never handle their login or payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "client_name": {
      "type": "string",
      "maxLength": 40,
      "description": "How the approval page names you, e.g. 'Claude Code'."
    }
  }
}
    arguments 11 lines
  • finish_connect unknown never probed

    Check whether the user approved a connect_account request. Returns the API key once approved (shown only once), or authorization_pending while waiting.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "device_code"
  ],
  "properties": {
    "device_code": {
      "type": "string",
      "description": "device_code from connect_account."
    }
  }
}
    arguments 13 lines
  • get_system unknown never probed

    Get one system: its components (summaries with slugs) and a shadcn CLI command that installs all of them at once. Call get_component for each component's source, or run the install command. Public systems shared by others are available by id.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "system"
  ],
  "properties": {
    "system": {
      "type": "string",
      "minLength": 1,
      "description": "System id, name (case-insensitive) or 'bookmarks' for the default one. See list_systems."
    }
  }
}
    arguments 14 lines
  • create_system unknown never probed

    Create a new system in the user's account, optionally with components, e.g. while picking components for a project. Needs Assembli Pro. Without an account, call connect_account first.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 60,
      "minLength": 1,
      "description": "Short name, unique among the user's systems, e.g. 'Fintech dashboard'."
    },
    "team": {
      "type": "boolean",
      "description": "True to create it as a team system, shared with everyone on the user's team."
    },
    "slugs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 500,
      "description": "Component slugs to add (from search_components)."
    },
    "description": {
      "type": "string",
      "maxLength": 500,
      "description": "What the system is for."
    }
  }
}
    arguments 32 lines
  • edit_system unknown never probed

    Add or remove components in one of the user's systems or their team's, rename it, change its description, or move it into the team. Bookmarks is editable on any account; other systems need Assembli Pro. Public links and deleting stay with the user on the website. Without an account, call connect_account first.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "system"
  ],
  "properties": {
    "add": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 500,
      "description": "Component slugs to add."
    },
    "name": {
      "type": "string",
      "maxLength": 60,
      "minLength": 1
    },
    "team": {
      "type": "boolean",
      "description": "True moves the system into the user's team; false moves a team system back out (team owner only)."
    },
    "remove": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 500,
      "description": "Component slugs to remove."
    },
    "system": {
      "type": "string",
      "minLength": 1,
      "description": "System id, name (case-insensitive) or 'bookmarks' for the default one. See list_systems."
    },
    "description": {
      "type": "string",
      "maxLength": 500
    }
  }
}
    arguments 43 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 97e634e22a3648ea.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/97e634e22a3648ea/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/97e634e22a3648ea/badge.svg)](https://brick.blue/agent/97e634e22a3648ea?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
100%

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.