com.hi-aisha/aisha
REMOTE · HI-AISHA.COM · SCANNED OCT 4
Verified local businesses, bookable by AI agents: services, prices, availability and appointments.
Available components
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 Security57
- 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 7 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 950 tokens (~135/item across 7 items; 7 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.hi-aisha/aisha MCP server?
com.hi-aisha/aisha is a hosted endpoint at https://hi-aisha.com/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 · hi-aisha.com
claude mcp add --transport http com-hi-aisha-aisha 'https://hi-aisha.com/mcp'
{
"mcpServers": {
"com-hi-aisha-aisha": {
"url": "https://hi-aisha.com/mcp"
}
}
} {
"servers": {
"com-hi-aisha-aisha": {
"type": "http",
"url": "https://hi-aisha.com/mcp"
}
}
} [mcp_servers.com-hi-aisha-aisha] url = "https://hi-aisha.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-hi-aisha-aisha": {
"type": "remote",
"url": "https://hi-aisha.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-hi-aisha-aisha --url 'https://hi-aisha.com/mcp' --transport streamable-http
mcp_servers:
com-hi-aisha-aisha:
url: "https://hi-aisha.com/mcp" {
"McpServers": {
"com-hi-aisha-aisha": {
"Transport": "http",
"Url": "https://hi-aisha.com/mcp"
}
}
} assistant mcp add com-hi-aisha-aisha -t streamable-http -u 'https://hi-aisha.com/mcp'
{
"mcpServers": {
"com-hi-aisha-aisha": {
"type": "http",
"url": "https://hi-aisha.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 +2
- Stability: fail → pass ▲ security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 84 to 88.
- 30 Aug 26 0
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool “consultar_disponibilidad” rewrote its description, which is the text the model reads security
- Tool “crear_reserva” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- “consultar_disponibilidad” added an optional parameter “persona” cosmetic
- “crear_reserva” added an optional parameter “persona” cosmetic
- 29 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 8 Oct 2026 · Probed https://hi-aisha.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hi-aisha.com | CN=YE2,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 639b10db7d4cceb71e59f80595de59c9a52 |
| SANs: hi-aisha.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hi-aisha.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hi-aisha.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hi-aisha.com/mcp | Verified | 200 | |
| http (plaintext) | http://hi-aisha.com/mcp | HTTPS enforced | 301 | https://hi-aisha.com/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 →
abrir_horas ~92
Para el DUEÑO: volver a abrir horas que había cerrado. Lo contrario de cerrar_horas. Úsala con "ya puedo el jueves", "ábreme la tarde otra vez" o "quita el bloqueo".
| Name | Type | Req | Description |
|---|---|---|---|
| clave | string | yes | – |
| desde | string | yes | – |
| fecha | string | yes | – |
| hasta | string | – | – |
| negocio | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
agendar_yo_mismo ~211
Para el DUEÑO: meter en Aisha una cita que le llegó por fuera. Esta es la importante. Cuando a un negocio le hablan por teléfono, le escriben por WhatsApp o le llega alguien de la calle, esa cita debe entrar aquí igual que las de Aisha — si no, la agenda que ven los asistentes de IA está incompleta y pueden ofrecer una hora que ya está vendida. A diferencia de crear_reserva, el contacto del cliente es OPCIONAL: el dueño lo tiene enfrente o acaba de hablar con él. Pero pídeselo si lo tiene a la mano, porque sirve para avisarle de cualquier cambio.
| Name | Type | Req | Description |
|---|---|---|---|
| clave | string | yes | – |
| contacto_cliente | string | – | – |
| fecha | string | yes | – |
| hora | string | yes | – |
| negocio | string | yes | – |
| nombre_cliente | string | yes | – |
| persona | string | – | – |
| servicio | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cancelar_cita_mia ~147
Para el DUEÑO: cancelar una cita de su propio negocio. Se puede por folio, o por nombre del cliente y fecha. Si hay más de una coincidencia NO cancela ninguna: devuelve la lista para que el dueño diga cuál. Cancelar es irreversible desde aquí, así que nunca se adivina. Al confirmar, recuérdale al dueño que le avise al cliente — Aisha no le escribe a la persona por él.
| Name | Type | Req | Description |
|---|---|---|---|
| clave | string | yes | – |
| fecha | string | – | – |
| folio | string | – | – |
| negocio | string | yes | – |
| nombre_cliente | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cancelar_reserva ~106
Cancela una reserva existente en Aisha y libera la hora al instante. Requiere el folio Y el nombre con el que se hizo la reserva; ambos deben coincidir. IMPORTANTE: confirma con la persona antes de cancelar — es una acción definitiva. Si quiere cambiar de hora, primero cancela con esta herramienta y luego crea la nueva con crear_reserva.
| Name | Type | Req | Description |
|---|---|---|---|
| folio | string | yes | – |
| nombre_cliente | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cerrar_horas ~172
Para el DUEÑO: cerrar horas para que nadie se las pueda agendar. Úsala cuando diga cosas como "tápame mañana de 2 a 4", "no voy a estar el jueves" o "bloquéame la tarde". 'desde' y 'hasta' en formato 24h (14:00). Sin 'hasta', cierra solo esa hora. Para un día completo, usa el horario de apertura y cierre del negocio. No afecta las citas que ya existen: si hay una agendada ahí, avísale al dueño para que decida si la cancela.
| Name | Type | Req | Description |
|---|---|---|---|
| clave | string | yes | – |
| desde | string | yes | – |
| fecha | string | yes | – |
| hasta | string | – | – |
| negocio | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
consultar_disponibilidad ~103
Consulta los horarios libres de un negocio en una fecha (AAAA-MM-DD). Si el negocio tiene varias personas atendiendo y a tu humano le importa una en particular ("quiero con Carlos"), pasa su nombre en 'persona' y te devuelve solo las horas de esa persona. Sin ese dato, devuelve las horas en que queda alguien libre.
| Name | Type | Req | Description |
|---|---|---|---|
| fecha | string | yes | – |
| negocio | string | yes | – |
| persona | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
consultar_reserva ~109
Consulta el estado de una reserva existente en Aisha. Requiere el folio (por ejemplo FILOSALO-0003) Y el nombre con el que se hizo la reserva. Ambos deben coincidir: es la protección para que nadie consulte citas ajenas. Úsala cuando la persona pregunte "¿sigue en pie mi cita?" o quiera confirmar fecha, hora o dirección.
| Name | Type | Req | Description |
|---|---|---|---|
| folio | string | yes | – |
| nombre_cliente | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
crear_reserva ~326
Crea una reserva en un negocio. Requiere negocio (id o nombre), nombre completo del cliente, fecha (AAAA-MM-DD), hora (ej. 17:00), servicio, y contacto_cliente: el teléfono o WhatsApp de quien asistirá. IMPORTANTE sobre contacto_cliente: pídeselo a la persona antes de agendar y explícale para qué es — el negocio lo necesita para avisarle si surge algún imprevisto, un cambio de horario o para confirmar. No lo inventes ni pongas datos falsos: una cita sin forma de contactar al cliente es un riesgo para el negocio. Si la persona no quiere darlo, dile que entonces reserve por teléfono directamente con el negocio. Sobre 'persona': en barberías, salones y spas la gente suele querer a alguien en concreto ("un corte con Carlos"). Si tu humano menciona un nombre, pásalo aquí. Si no dice nada, no lo inventes: déjalo vacío y el negocio asigna a quien esté libre. Los nombres de quienes atienden salen en ver_servicios. Devuelve el folio, con quién quedó la cita, la dirección, la liga de mapa y con cuántos minutos de antelación pide llegar el negocio.
| Name | Type | Req | Description |
|---|---|---|---|
| contacto_cliente | string | yes | – |
| fecha | string | yes | – |
| hora | string | yes | – |
| negocio | string | yes | – |
| nombre_cliente | string | yes | – |
| persona | string | – | – |
| servicio | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
listar_negocios ~30
Lista todos los negocios conectados a Aisha, con su giro, ciudad y estado de verificación.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
mi_agenda ~98
Para el DUEÑO de un negocio: ver cómo va su día en Aisha. Requiere la clave de su panel (la del enlace de su agenda). Devuelve las citas de ese día con quién viene, qué servicio y a qué hora, más las horas que quedan libres. Sin fecha, muestra hoy.
| Name | Type | Req | Description |
|---|---|---|---|
| clave | string | yes | – |
| fecha | string | – | – |
| negocio | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
solicitar_alta ~234
Registra la solicitud de un negocio que quiere aparecer en Aisha y ser reservable por asistentes de IA. Úsala cuando el dueño de un negocio pida darse de alta, aparecer o hacerse visible en Aisha / hi-aisha. Pide al dueño estos datos antes de llamarla: nombre comercial, giro (barbería, estética, salón, spa), ciudad, dirección, teléfono de contacto, nombre del responsable, lista de servicios con precio y duración, y horarios de atención. IMPORTANTE: esta herramienta NO publica el negocio. Solo registra la solicitud; el negocio se publica después de que Aisha verifique su identidad con una persona. Explícale eso al dueño al confirmarle el registro.
| Name | Type | Req | Description |
|---|---|---|---|
| ciudad | string | yes | – |
| direccion | string | yes | – |
| giro | string | yes | – |
| horarios_texto | string | yes | – |
| nombre_negocio | string | yes | – |
| nombre_responsable | string | yes | – |
| notas | string | – | – |
| servicios_texto | string | yes | – |
| telefono_contacto | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ver_servicios ~42
Muestra los servicios, precios, horario, dirección y cómo llegar a un negocio. Acepta el id o parte del nombre.
| Name | Type | Req | Description |
|---|---|---|---|
| negocio | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the com.hi-aisha/aisha MCP server?
com.hi-aisha/aisha is an MCP server listed in the public MCP registry as com.hi-aisha/aisha. Verified local businesses, bookable by AI agents: services, prices, availability and appointments. This page covers its hosted endpoint (https://hi-aisha.com/mcp).
Is the com.hi-aisha/aisha MCP server safe to use?
com.hi-aisha/aisha 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 com.hi-aisha/aisha MCP server expose?
com.hi-aisha/aisha exposes 12 tools: listar_negocios, ver_servicios, consultar_disponibilidad, crear_reserva, consultar_reserva, and 7 more. Their descriptions and schemas cost roughly 1,670 tokens of context every time the server is loaded.
Does the com.hi-aisha/aisha MCP server require authentication?
No. We connected to com.hi-aisha/aisha without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.hi-aisha/aisha MCP server still maintained?
com.hi-aisha/aisha is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.