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.

Aura UI

REMOTE · AURA-UI.COM · SCANNED SEP 22

Discover and install Aura UI Blade components for Laravel, Livewire and Tailwind CSS 4.

Available components

0 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 547 tokens (~109/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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 Aura UI MCP server?

Aura UI is a hosted endpoint at https://aura-ui.com/mcp/aura, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · aura-ui.com

# add to Claude Code
claude mcp add --transport http bluestarsystem-aura-ui 'https://aura-ui.com/mcp/aura'
// .cursor/mcp.json
{
  "mcpServers": {
    "bluestarsystem-aura-ui": {
      "url": "https://aura-ui.com/mcp/aura"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "bluestarsystem-aura-ui": {
      "type": "http",
      "url": "https://aura-ui.com/mcp/aura"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.bluestarsystem-aura-ui]
url = "https://aura-ui.com/mcp/aura"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bluestarsystem-aura-ui": {
      "type": "remote",
      "url": "https://aura-ui.com/mcp/aura",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bluestarsystem-aura-ui --url 'https://aura-ui.com/mcp/aura' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  bluestarsystem-aura-ui:
    url: "https://aura-ui.com/mcp/aura"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "bluestarsystem-aura-ui": {
      "Transport": "http",
      "Url": "https://aura-ui.com/mcp/aura"
    }
  }
}
# add to Vellum
assistant mcp add bluestarsystem-aura-ui -t streamable-http -u 'https://aura-ui.com/mcp/aura'
// mcp.json
{
  "mcpServers": {
    "bluestarsystem-aura-ui": {
      "type": "http",
      "url": "https://aura-ui.com/mcp/aura"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 2 Sept 26 0
    • Stability: 0.97 → pass security
  • 1 Sept 26 +1

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

  • 30 Aug 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.

  • 28 Aug 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.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • Tool “get-component-tool” rewrote its description, which is the text the model reads security
    • “add-component-tool” reworded the description of “name” cosmetic
    • “get-component-tool” reworded the description of “name” cosmetic
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 22 Sept 2026 · Probed https://aura-ui.com/mcp/aura

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aura-ui.com CN=WE1,O=Google Trust Services,C=US 11 Aug 2026 9 Nov 2026 ECDSA 256 ECDSA-SHA256 d21aff14b55aad820e0ea52774f8dfa7
SANs: aura-ui.com, *.aura-ui.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aura-ui.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
aura-ui.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google-analytics.com https://js.stripe.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com https://analytics.elju.it; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https://www.google-analytics.com https://*.stripe.com; connect-src 'self' https://www.google-analytics.com https://*.google-analytics.com https://analytics.google.com https://api.stripe.com https://fonts.googleapis.com https://fonts.gstatic.com https://cloudflareinsights.com https://static.cloudflareinsights.com https://analytics.elju.it; frame-src 'self' https://js.stripe.com https://demo.aura-ui.com https://www.openstreetmap.org; object-src 'none'; base-uri 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aura-ui.com/mcp/aura Verified 200
http (plaintext) http://aura-ui.com/mcp/aura HTTPS enforced 301 https://aura-ui.com/mcp/aura
MCP tools · 5 exposed · ~444 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
add-component-tool ~119

Get everything needed to install an Aura UI component or block into a Laravel project: the `php artisan aura:add` command, the resolved transitive dependency tree, the file list, and (optionally) the Blade source of each file. Call this when you are ready to install a component you found via list/search/get.

NameTypeReqDescription
namestringyesThe component or block name, e.g. "button", "date-picker", "hero-split".
with_sourcebooleanInclude the Blade source of each file (default true).

No output schema declared.

No examples provided.

filament-theme-tool ~99

Describe the Aura Filament theme: the design presets available for a Filament v4/v5 admin panel, plus the documentation topics covering install, layout modes, custom form fields, table columns, dashboard widgets and email theming. Use this when the user is theming or building a Filament panel.

NameTypeReqDescription
topicstringOptional. A Filament documentation topic name, e.g. "presets", "widgets", "table-columns".

No output schema declared.

No examples provided.

get-component-tool ~87

Get full details for a single Aura UI component by name (e.g. "button", "date-picker"): its Blade tag, tier, a copy-pasteable usage example, and the complete Markdown documentation including all props. Call this before generating Aura markup for a component.

NameTypeReqDescription
namestringyesThe component name, e.g. "button", "modal", "date-picker".

No output schema declared.

No examples provided.

list-components-tool ~65

List all available Aura UI components (free and Pro), with their Blade tag, tier, and a one-line description. Use this to discover what UI components exist before writing markup.

NameTypeReqDescription
tierstringOptional. Filter components by tier: "free" or "pro".

No output schema declared.

No examples provided.

search-components-tool ~74

Search Aura UI components by keyword (matches name, title and description). Returns matching components with their Blade tag and tier. Use this when you need a component for a purpose, e.g. "date", "table", "notification".

NameTypeReqDescription
querystringyesKeyword(s) to search for across component names and descriptions.

No output schema declared.

No examples provided.

Common questions

What is the Aura UI MCP server?

Aura UI is an MCP server listed in the public MCP registry as io.github.BlueStarSystem/aura-ui. Discover and install Aura UI Blade components for Laravel, Livewire and Tailwind CSS 4. This page covers its hosted endpoint (https://aura-ui.com/mcp/aura).

Is the Aura UI MCP server safe to use?

Aura UI scores 82 out of 100 on VerifyMCP. 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 Aura UI MCP server expose?

Aura UI exposes 5 tools: list-components-tool, search-components-tool, get-component-tool, add-component-tool, filament-theme-tool. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.

Does the Aura UI MCP server require authentication?

No. We connected to Aura UI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Aura UI MCP server still maintained?

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