Skip to content

aisha MCP server

com.hi-aisha/aishahi-aisha.comstreamable-httpv1.0.0Scanned

Verified local businesses, bookable by AI agents: services, prices, availability and appointments.

12 tools: 1 do something that can't be undone and 11 change things.

Tools: 0 delete, 1 irreversible, 11 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 aisha MCP server can do

The aisha MCP server is published by hi-aisha.com, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (cancelar_cita_mia) and create or change data (11 tools: listar_negocios, ver_servicios, consultar_disponibilidad, crear_reserva and 7 more), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 13, 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.

12 tools

Can't be undone 1Claude Code: ask
  • cancelar_cita_miaPara el DUEÑO: cancelar una cita de su propio negocio.No findings

    Why it is in this group

    • The description says "irreversible".
    Description, as the server wrote it
    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.
Changes things 11Claude Code: ask
  • abrir_horasPara el DUEÑO: volver a abrir horas que había cerrado.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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".
  • agendar_yo_mismoPara el DUEÑO: meter en Aisha una cita que le llegó por fuera.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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. MUY IMPORTANTE — de quién es la cita: quien te está hablando es el DUEÑO del negocio, NO el cliente. Si no te dijo a nombre de quién va la cita, PREGÚNTASELO. No pongas el nombre de la persona con la que estás hablando, ni el del titular de la cuenta, ni ningún nombre que hayas deducido del contexto. Una cita a nombre equivocado es peor que no tenerla: el negocio llama a quien no es y pierde al que sí venía.
  • cancelar_reservaCancela una reserva existente en Aisha y libera la hora al instante.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • cerrar_horasPara el DUEÑO: cerrar horas para que nadie se las pueda agendar.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • consultar_disponibilidadConsulta los horarios libres de un negocio en una fecha (AAAA-MM-DD).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • consultar_reservaConsulta el estado de una reserva existente en Aisha.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • crear_reservaCrea una reserva en un negocio.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • listar_negociosLista todos los negocios conectados a Aisha, con su giro, ciudad y estado de verificación.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Lista todos los negocios conectados a Aisha, con su giro, ciudad y estado de verificación.
  • mi_agendaPara el DUEÑO de un negocio: ver cómo va su día en Aisha.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • solicitar_altaRegistra la solicitud de un negocio que quiere aparecer en Aisha y ser reservable por asistentes de IA.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • ver_serviciosMuestra los servicios, precios, horario, dirección y cómo llegar a un negocio.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Muestra los servicios, precios, horario, dirección y cómo llegar a un negocio. Acepta el id o parte del nombre.

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 private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:40 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
12
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (1 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://hi-aisha.com/mcp: tools/list returned 12 tools to an anonymous client, including cancelar_cita_mia (irreversible), listar_negocios (write), ver_servicios (write), consultar_disponibilidad (write), crear_reserva (write) and 7 more

    What this check looks for

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.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http aisha https://hi-aisha.com/mcp
claude mcp add --transport http aisha https://hi-aisha.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__aisha__listar_negocios",
      "mcp__aisha__ver_servicios",
      "mcp__aisha__consultar_disponibilidad",
      "mcp__aisha__crear_reserva",
      "mcp__aisha__consultar_reserva",
      "mcp__aisha__cancelar_reserva",
      "mcp__aisha__solicitar_alta",
      "mcp__aisha__mi_agenda",
      "mcp__aisha__cerrar_horas",
      "mcp__aisha__abrir_horas",
      "mcp__aisha__agendar_yo_mismo",
      "mcp__aisha__cancelar_cita_mia"
    ],
    "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 aisha. Review it before you use it.

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/com.hi-aisha/aisha/verify?hash=cbd291af2c9d0ffdd5217b6e8a397acbb7b638ec3667f64dac45c01c5e639a8e" | jq -e '.changed == false'

Pinned hash cbd291af2c9d, from Nov 13, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.hi-aisha/aisha/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.hi-aisha/aisha
[![Anlyon Radar](https://radar.anlyon.com/badge/com.hi-aisha/aisha.svg)](https://radar.anlyon.com/servers/com.hi-aisha/aisha)

Source: MCP Registry. Synced Oct 21, 2026, 17:56 UTC.

aisha MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the aisha MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 12 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 aisha MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the aisha MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: cancelar_cita_mia.

What tools does the aisha MCP server have?

12 tools: 1 irreversible, 11 write. cancelar_cita_mia, listar_negocios, ver_servicios, consultar_disponibilidad, crear_reserva, consultar_reserva, cancelar_reserva, solicitar_alta and 4 more.

Does the aisha MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the aisha MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the aisha MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.