Aurora Concierge
REMOTE · PLATAFORMA.AURORACONCIERGE.COM.BR
Home care in Osasco and São Paulo, Brazil: book the free nursing assessment or request a proposal.
Available components
Last scanned (43 minutes ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1167 tokens (~291/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://plataforma.auroraconcierge.com.br/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.auroraconcierge.com.br | CN=YR2,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | RSA 2048 | SHA256-RSA | 58858e375ef81fbdaf527c9675880a45310 |
| SANs: *.auroraconcierge.com.br, auroraconcierge.com.br | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of plataforma.auroraconcierge.com.br. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| br. | present | 38298 | 13 | Verified |
| com.br. | present | 50930 | 13 | Verified |
| auroraconcierge.com.br. | 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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://plataforma.auroraconcierge.com.br/api/mcp | Verified | 200 | |
| http (plaintext) | http://plataforma.auroraconcierge.com.br/api/mcp | HTTPS enforced | 308 | https://plataforma.auroraconcierge.com.br/api/mcp |
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 →
agendar_avaliacao ~229
Marca a avaliação gratuita (uma chamada de vídeo com a equipe de enfermagem) em um horário livre, em nome da família. Use o inicio de um horário devolvido por consultar_horarios, copiado como veio. Exige nome, telefone e e-mail da família e o consentimento dela com a política de privacidade (a versão está nas instructions do servidor). A confirmação, com o link da chamada, chega por e-mail à família. Se o horário não estiver livre, o resultado traz os horários livres em horarios.
| Name | Type | Req | Description |
|---|---|---|---|
| consentimento | object | yes | O aceito da família à política de privacidade, depois de ela ler a política |
| string | yes | E-mail da família: a confirmação com o link da chamada chega nele | |
| inicio | string | yes | O inicio de um horário de consultar_horarios: ISO 8601 com fuso, no futuro |
| nome | string | yes | Nome de quem pede a avaliação, da família |
| telefone | string | yes | Telefone com DDD, de preferência em E.164 (+55...) |
No output schema declared.
No examples provided.
consultar_horarios ~86
Lista os horários livres da avaliação gratuita (uma chamada de vídeo com a equipe de enfermagem) nos próximos 7 dias, agrupados por dia, no fuso indicado em fuso. Cada horário traz inicio (instante ISO 8601) e rotulo (a hora local, como dizer à família). Lista vazia significa nenhuma vaga nesta semana. Não recebe argumentos.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
consultar_proposta ~113
Consulta a proposta pedida por solicitar_proposta, com o protocolo que ela devolveu. Enquanto a equipe não envia a proposta, a situacao é em_preparo. Depois do envio por e-mail à família, devolve a situacao (enviada, aceita ou recusada) e a proposta como foi enviada: serviços, quantidades, valores, validade e pagamento. Consulte no máximo uma vez por hora.
| Name | Type | Req | Description |
|---|---|---|---|
| protocolo | string | yes | O protocolo devolvido por solicitar_proposta, copiado como veio |
No output schema declared.
No examples provided.
solicitar_proposta ~568
Pede à equipe uma proposta de cuidado domiciliar para a família: a equipe monta a proposta e a envia por e-mail dentro do prazo informado na resposta. Nenhum preço é informado por esta ferramenta: não estime valores. Quando a proposta já sai montada, a resposta traz um protocolo, e os valores só vêm por consultar_proposta com esse protocolo, depois que a equipe enviar a proposta por e-mail. Exige nome e e-mail da família, o tipo de cuidado, o período ou as horas por dia, os dias por semana (ou, quando os horários mudam de um dia para o outro, a jornada, que substitui período, horas e dias) e o consentimento dela com a política de privacidade (a versão está nas instructions do servidor). O telefone, a idade de quem recebe o cuidado, a cidade e uma observação curta são opcionais. Se faltar algum dado, o resultado traz os nomes em campos.
| Name | Type | Req | Description |
|---|---|---|---|
| cidade | string | – | Cidade (ou bairro) onde o cuidado acontece. Opcional |
| consentimento | object | yes | O aceito da família à política de privacidade, depois de ela ler a política |
| dias_por_semana | integer | – | Dias de cuidado por semana, de 1 a 7. Informe os dias ou a jornada |
| string | yes | E-mail da família: a proposta chega nele | |
| horas_por_dia | integer | – | Horas de cuidado por dia, de 1 a 24. Informe o período ou as horas |
| jornada | array | – | Os dias e horários, quando variam de um dia para o outro (ex.: domingo das 12 às 18 e segunda das 9 às 18): um item por dia da semana, em horas cheias. Quando vem, horas_por_dia e dias_por_semana sae… |
| nome | string | yes | Nome de quem pede a proposta, da família |
| observacoes | string | – | Observação curta para a equipe sobre o cuidado, sem nomes de pessoas. Opcional |
| paciente_idade | integer | – | Idade em anos de quem vai receber o cuidado. Opcional |
| periodo | string | – | diurno, noturno ou integral (dia e noite). Informe o período ou horas_por_dia |
| telefone | string | – | Telefone com DDD, de preferência em E.164 (+55...). Opcional |
| tipo_cuidado | string | yes | cuidador = companhia e atividades do dia a dia; enfermagem = procedimentos técnicos; fisioterapia; pos_operatorio = recuperação de cirurgia; acompanhamento_24h; outro |
No output schema declared.
No examples provided.
How do I install the Aurora Concierge MCP server?
Aurora Concierge is a hosted endpoint at https://plataforma.auroraconcierge.com.br/api/mcp, 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 · plataforma.auroraconcierge.com.br
claude mcp add --transport http br-com-auroraconcierge-mcp 'https://plataforma.auroraconcierge.com.br/api/mcp'
What is the Aurora Concierge MCP server?
Aurora Concierge is an MCP server listed in the public MCP registry as br.com.auroraconcierge/mcp. Home care in Osasco and São Paulo, Brazil: book the free nursing assessment or request a proposal. This page covers its hosted endpoint (https://plataforma.auroraconcierge.com.br/api/mcp).
Is the Aurora Concierge MCP server safe to use?
Aurora Concierge scores 75 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 Aurora Concierge MCP server expose?
Aurora Concierge exposes 4 tools: consultar_horarios, agendar_avaliacao, solicitar_proposta, consultar_proposta. Their descriptions and schemas cost roughly 996 tokens of context every time the server is loaded.
Does the Aurora Concierge MCP server require authentication?
No. We connected to Aurora Concierge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Aurora Concierge MCP server still maintained?
Aurora Concierge is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.