Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

UI Beats

NPM · @UIBEATS/MCP · SCANNED SEP 20

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

Available components

npm · @uibeats/mcp 95
+3 this week 95 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to nikhils4/ui-beats). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 27 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 428 tokens (~107/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the UI Beats MCP server?

UI Beats runs locally as an npm package, launched with npx -y @uibeats/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @uibeats/mcp

# add to Claude Code
claude mcp add com-uibeats-mcp -- npx -y @uibeats/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-uibeats-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@uibeats/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-uibeats-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@uibeats/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-uibeats-mcp -- npx -y @uibeats/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-uibeats-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@uibeats/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-uibeats-mcp --command npx --arg -y --arg @uibeats/mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-uibeats-mcp:
    command: "npx"
    args: ["-y", "@uibeats/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-uibeats-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@uibeats/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-uibeats-mcp -t stdio -c npx -a -y @uibeats/mcp
// mcp.json
{
  "mcpServers": {
    "com-uibeats-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@uibeats/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@uibeats/mcp@0.1.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo nikhils4/ui-beats
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/nikhils4/ui-beats/.github/workflows/release-mcp.yml@refs/tags/mcp-v0.1.3
Rekor log index 2570551565
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:26e7500755d273230003484bf1a553bd79a174ad27d1cf5c7aaa34bf1eca01c045921f7218118863b5c8ff8f853e43d007e5894c11dbac41b279ee93a

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~318 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_component ~72

Fetch the complete documentation for one component: description, when to use it, the full props table, a runnable usage example and the entire source file. Read this before writing code that uses a UI Beats component.

NameTypeReqDescription
namestringyesComponent name, e.g. 'flip-card' (or 'Flip Card').

No output schema declared.

No examples provided.

get_install_command ~60

Return the exact shadcn CLI command that adds a component to the current project, along with the npm packages it pulls in. Run the returned command in the project root.

NameTypeReqDescription
namestringyesComponent name, e.g. 'flip-card'.

No output schema declared.

No examples provided.

list_components ~50

List every component in the catalogue, grouped by category. Use this to see what is available before searching.

NameTypeReqDescription
categorystring–List only this category, e.g. 'card' or 'block'.

No output schema declared.

No examples provided.

search_components ~136

Search the UI Beats catalogue by intent or name, e.g. 'card that flips', 'number counting up', 'animated background', 'flip-card'. Returns ranked matches with their description, docs URL and install command. Call get_component afterwards to read the actual source and props.

NameTypeReqDescription
categorystring–Restrict results to one category, e.g. 'card' or 'block'. Omit to search everything; list_components shows the current set.
limitinteger–Maximum number of results (default 10).
querystringyesWhat the component should do, in plain words, or its exact name.

No output schema declared.

No examples provided.

Common questions

What is the UI Beats MCP server?

UI Beats is an MCP server listed in the public MCP registry as com.uibeats/mcp. MCP server for UI Beats. Let your coding agent search, read and install animated React components. This page covers its npm package (@uibeats/mcp).

Is the UI Beats MCP server safe to use?

UI Beats scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the UI Beats MCP server expose?

UI Beats exposes 4 tools: search_components, get_component, list_components, get_install_command. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.

Is the UI Beats MCP server still maintained?

UI Beats is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the UI Beats MCP server under?

UI Beats declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.