Skip to main content
Glama
Sign In
UI Kit Aggregator MCP

UI Kit Aggregator MCP

by Faixiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check a proposed use

check_compliance
Read-only

Check whether a proposed use of a chosen UI or motion source is allowed before fetching. Returns allowed, needs_token, or blocked, so you know if a token or license applies.

Instructions

Decide whether a proposed use is allowed for a chosen source. Specialties: MotionSites (motionsites): AI website prompt library for conceptual sites such as landing pages, SaaS marketing pages, and portfolios. Choose this for full-page design prompts, not drop-in components. React Bits (react-bits): React animation components: text effects, backgrounds, and UI micro-interactions, in JavaScript or TypeScript with CSS or Tailwind. Choose this for copy-and-paste React components. Uiverse (uiverse): Community HTML, CSS, Tailwind, and React snippets, including hover effects, buttons, and cards. Choose this for small, standalone UI widgets. Anime.js (anime): Lightweight JavaScript animation engine for timelines, easing, and animating DOM, CSS, or SVG elements. Choose this when you need an animation library or its official docs and examples, not a component kit. Aceternity UI (aceternity): React and Tailwind component library with advanced visual effects, including 3D, parallax, spotlight, aurora, glow, and shader-based visuals. Choose this for polished, cinematic UI blocks. Motion Prompt (motion-prompt): Motion vocabulary and prompt library for describing animations, camera moves, and page transitions to AI. Choose this for named effect terms, copyable prompts, and motion demos, not drop-in UI components. Cult UI (cult-ui): Distinctive React / shadcn-style UI components from the official Cult UI registry. Choose this for copy-and-paste Cult components, not a general animation engine. Magic UI (magic-ui): Free React and Tailwind animated components (official free / MIT catalog only). Choose this for copy-and-paste Magic UI free blocks; do not use this source for Magic UI Pro. End products (a client marketing site, an app, a website) are treated differently from republishing the kit as a component library, template pack, or marketplace product. Does not return source. This tool judges the proposed use, not a missing token. When a source or item requires a token or license key that is not configured, the result status is "needs_token" (not "blocked" and not "allowed"). Do not treat that as a quiet failure. Tell the user that this specific content needs a token, name the product (for example Aceternity All-Access or React Bits Pro) and the environment variable (for example ACETERNITY_PRO_TOKEN or REACTBITS_LICENSE_KEY), point them to the official register URLs in the result, and ask whether to configure/add the token or skip this item. Only retry or fetch after the user confirms and the token is in place; if they skip, stop and do not fetch. This server does not collect the secret in the tool call. If the required token is already configured, fetch proceeds when the license otherwise allows it. Hard compliance blocks stay "blocked" with the body omitted: unclear licenses, disallowed scrape or prompt types, MotionSites prompt bodies, Magic UI Pro and other paid catalogs this server does not support, and redistribution the license forbids. Magic UI Pro is not a missing-token case and must not be offered as "add a token". There is no skip_license_check.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>",
      "proposedUse": "<proposedUse>"
    },
    "name": "check_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdNo
sourceYesLimit to these source ids. Default: all eight. motionsites: AI website prompts for landing pages, SaaS, and portfolios; react-bits: React animation components, text effects, and micro-interactions; uiverse: community HTML/CSS/Tailwind/React snippets such as hover effects, buttons, and cards; anime: lightweight JS animation engine for timelines, easing, and any-element animation; aceternity: React/Tailwind components with advanced 3D, parallax, spotlight, aurora, glow, and shader effects; motion-prompt: motion vocabulary and copyable prompts for describing animations, camera moves, and page transitions to AI, not drop-in UI components; cult-ui: distinctive React / shadcn-style UI components from the official Cult UI registry, for copy-and-paste Cult components, not a general animation engine; magic-ui: free React and Tailwind animated components from the official Magic UI MIT catalog only, not Magic UI Pro.
proposedUseYesHow the material would be used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With only readOnlyHint declared and no output schema, the description carries the burden well: it names the result statuses ("allowed", "blocked", "needs_token"), states the body is omitted on hard blocks, and lists what counts as a hard block. It also specifies that no secret is collected in the tool call and that "there is no skip_license_check", which prevents a plausible misuse. Nothing contradicts the readOnly annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose statement and the token/block policy are front-loaded and valuable, but the middle is dominated by eight source descriptions that duplicate the enum descriptions almost verbatim (including the same "not drop-in components" and "not Magic UI Pro" caveats). Removing that block would lose little and roughly halve the length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read-only judgment tool with no output schema, the definition covers status semantics, token remediation, and hard-block behavior thoroughly. The one missing piece is any explanation of itemId and how it narrows the judgment to a specific item rather than the source as a whole.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 67% schema coverage, the source enum already documents the eight source ids in detail, so the long per-source blurbs in the description largely restate structured data with little added meaning. proposedUse is covered by the schema description, and itemId is undocumented in both the schema and the description, which is a real gap for an optional selector parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: "Decide whether a proposed use is allowed for a chosen source." That is clear and distinguishable from siblings like get_license or search_ui_kits. The remaining bulk is per-source catalog copy rather than more precision about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing guidance per source ("Choose this for full-page design prompts, not drop-in components", "Choose this for copy-and-paste React components"), plus exclusions such as Magic UI Pro being unsupported. It also implicitly separates itself from license/token tooling with "This tool judges the proposed use, not a missing token," though it never names the sibling tool an agent should call instead for token or license status.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools