mcp-registry/io.github.bluestarsystem/aura-ui · v1.0.0
Also listed as github/bluestarsystem/aura-ui
As of 2026-10-26 18:10 UTC, the Bluestarsystem Aura Ui MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 7 minutes.
Discover and install Aura UI Blade components for Laravel, Livewire and Tailwind CSS 4.
Point your MCP client at this streamable-http endpoint: https://aura-ui.com/mcp/aura
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.bluestarsystem%2Faura-ui/fixes
{
"name": "add-component-tool",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "The component or block name, e.g. \"button\", \"date-picker\", \"hero-split\"."
},
"with_source": {
"type": "boolean",
"description": "Include the Blade source of each file (default true)."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Add Component Tool"
}{
"name": "get-component-tool",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "The component name, e.g. \"button\", \"modal\", \"date-picker\"."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Component Tool"
}{
"name": "list-components-tool",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"tier": {
"enum": [
"free",
"pro"
],
"type": "string",
"description": "Optional. Filter components by tier: \"free\" or \"pro\"."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "List Components Tool"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.bluestarsystem/aura-ui"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.bluestarsystem/aura-ui"}) over MCP.
add-component-tool ~180 tokensfilament-theme-tool ~147 tokensget-component-tool ~134 tokenssearch-components-tool ~127 tokenslist-components-tool ~110 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.bluestarsystem%2Faura-ui?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.bluestarsystem%2Faura-ui?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bluestarsystem%2Faura-ui.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bluestarsystem%2Faura-ui.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.bluestarsystem%2Faura-ui?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c2c3ef8203203c0d…, first seen 2026-10-17, included at leaf 5268 of 74,609. Version history · verify what your client received.
Compare: most reliable code servers · most reliable knowledge servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:10 UTC, the Bluestarsystem Aura Ui MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 7 minutes.
Bluestarsystem Aura Ui MCP server advertises 5 tools, including add-component-tool, filament-theme-tool, get-component-tool, list-components-tool, search-components-tool.
Point your MCP client at this streamable-http endpoint: https://aura-ui.com/mcp/aura
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.