Remote MCP · Endpoint

Aura UI MCP server

No. Aura UI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aura-ui.com/mcp/aura

The last check completed an MCP handshake.

Registry name
io.github.BlueStarSystem/aura-ui
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
448 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Discover and install Aura UI Blade components for Laravel, Livewire and Tailwind CSS 4.
Listing
From the official MCP registry (active).
Recent checks of Aura UI
CheckedResultHandshake
1 hour agoHandshake completed448 ms
2 days agoHandshake completed487 ms
4 days agoHandshake completed232 ms
5 days agoHandshake completed253 ms
7 days agoHandshake completed299 ms
8 days agoHandshake completed509 ms
9 days agoHandshake completed254 ms
12 days agoHandshake completed222 ms
13 days agoHandshake completed1.89 s
15 days agoHandshake completed330 ms
16 days agoHandshake completed916 ms
18 days agoHandshake completed237 ms
19 days agoHandshake completed250 ms
20 days agoHandshake completed301 ms
20 days agoHandshake completed618 ms
21 days agoHandshake completed345 ms
22 days agoHandshake completed1.31 s

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Aura UI and makes no claim about it beyond what these checks measured.