Aura UI MCP server
io.github.BlueStarSystem/aura-uiBlueStarSystemstreamable-httpv1.0.0Scanned
Discover and install Aura UI Blade components for Laravel, Livewire and Tailwind CSS 4.
5 tools: 1 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Aura UI MCP server can do
The Aura UI MCP server is published by the GitHub account BlueStarSystem. It has 5 tools. It can create or change data (1 tool: add-component-tool), but cannot delete data. 4 tools only read.
1 tool reads private data (filament-theme-tool); 1 tool brings in text other people can write (filament-theme-tool).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
add-component-toolGet 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, a…No findings
Why it is in this group
- The name "add-component-tool" says "add": a word for a change.
Description, as the server wrote it 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.
Only reads 4Show 4 read-only tools
filament-theme-toolDescribe 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, t…Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "describe": a word for reading.
What it can reach
- private-dataThe description's first sentence says "describe" and "table": it reads databases.
- untrusted-inputThe description's first sentence says "describe" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
get-component-toolGet full details for a single Aura UI component by name (e.g.No findings
Why it is in this group
- The name "get-component-tool" says "get": a word for reading.
Description, as the server wrote it 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.
list-components-toolList all available Aura UI components (free and Pro), with their Blade tag, tier, and a one-line description.No findings
Why it is in this group
- The name "list-components-tool" says "list": a word for reading.
Description, as the server wrote it 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.
search-components-toolSearch Aura UI components by keyword (matches name, title and description).No findings
Why it is in this group
- The name "search-components-tool" says "search": a word for reading.
Description, as the server wrote it 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".
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:56 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://aura-ui.com/mcp/aura: tools/list returned 5 tools to an anonymous client, including add-component-tool (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http aura-ui https://aura-ui.com/mcp/auraclaude mcp add --transport http aura-ui https://aura-ui.com/mcp/auraRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__aura-ui__list-components-tool",
"mcp__aura-ui__search-components-tool",
"mcp__aura-ui__get-component-tool",
"mcp__aura-ui__filament-theme-tool"
],
"ask": [
"mcp__aura-ui__add-component-tool"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as aura-ui. Review it before you use it.
Capability tags behind 1 rule
- mcp__aura-ui__filament-theme-tool private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.BlueStarSystem/aura-ui/verify?hash=409edaad0703148c6d5903b33d03f33e40b0b72938d1a4b8692cec08cbaa82f3" | jq -e '.changed == false'Pinned hash 409edaad0703, from Nov 15, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.BlueStarSystem/aura-ui/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.BlueStarSystem/aura-ui)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:14 UTC.
Aura UI MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Aura UI MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Aura UI MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Aura UI MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Aura UI MCP server have?
- 5 tools: 1 write, 4 read. add-component-tool, list-components-tool, search-components-tool, get-component-tool and filament-theme-tool.
Does the Aura UI MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Aura UI MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Aura UI MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.