Remote MCP · Endpoint

Aurora Concierge MCP server

No. Aurora Concierge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://plataforma.auroraconcierge.com.br/api/mcp

The last check completed an MCP handshake.

Registry name
br.com.auroraconcierge/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
180 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Home care in Osasco and São Paulo, Brazil: book the free nursing assessment or request a proposal.
Listing
From the official MCP registry (active).
Recent checks of Aurora Concierge
CheckedResultHandshake
1 hour agoHandshake completed180 ms
8 days agoHandshake completed167 ms
9 days agoHandshake completed140 ms
11 days agoHandshake completed274 ms
12 days agoHandshake completed171 ms
12 days agoHandshake completed225 ms
14 days agoHandshake completed480 ms
14 days agoHandshake completed145 ms
16 days agoHandshake completed160 ms
19 days agoHandshake completed146 ms
21 days agoHandshake completed280 ms
24 days agoHandshake completed213 ms
26 days agoHandshake completed170 ms
28 days agoHandshake completed927 ms

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

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 Aurora Concierge and makes no claim about it beyond what these checks measured.