com.hi-aisha/aisha

REMOTE · HI-AISHA.COM · SCANNED AUG 20

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

Available components

+3 this week 64 64 Trust /100

Trust breakdown (6 categories)

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 →

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 Usability73

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 794 tokens (~113/item across 7 items; 7 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management28

Stability check failed: schema churn in the 11 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · hi-aisha.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.com-hi-aisha-aisha]
url = "https://hi-aisha.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hi-aisha-aisha": {
      "type": "remote",
      "url": "https://hi-aisha.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-hi-aisha-aisha --url https://hi-aisha.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-hi-aisha-aisha:
    url: "https://hi-aisha.com/mcp"

// mcp.json

{
  "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.

Changelog

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.

20 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 24 to 28.
18 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 18 to 21.
16 Aug 26 0
- Stability: 0.20 → fail ▼ security
- A breaking change shipped without a version bump: still 1.28.1 ▼ security
- Tool “crear_reserva” rewrote its description, which is the text the model reads security
- Schema quality: 96 → 113 ▼ functional
- “crear_reserva” added a required parameter “contacto_cliente”, so existing callers break ▼ functional
14 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
12 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
11 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
10 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
9 Aug 26 59

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 20 Aug 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	30 Jul 2026	28 Oct 2026	ECDSA 256	ECDSA-SHA384	50a5743d50eadbe53feb8e002ec79e0ed79
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

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

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

MCP tools · 7 exposed · ~794 tokens

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.

Tool Tokens

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.

Input Output Examples

Name	Type	Req	Description
folio	string	yes	–
nombre_cliente	string	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

consultar_disponibilidad ~39

Consulta los horarios libres de un negocio en una fecha (AAAA-MM-DD).

Input Output Examples

Name	Type	Req	Description
fecha	string	yes	–
negocio	string	yes	–

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.

Input Output Examples

Name	Type	Req	Description
folio	string	yes	–
nombre_cliente	string	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

crear_reserva ~234

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. Devuelve el folio, la dirección, la liga de mapa y con cuántos minutos de antelación pide llegar el negocio.

Input Output Examples

Name	Type	Req	Description
contacto_cliente	string	yes	–
fecha	string	yes	–
hora	string	yes	–
negocio	string	yes	–
nombre_cliente	string	yes	–
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 Output Examples

Input schema present but exposes no named parameters.

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.

Input Output Examples

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.

Input Output Examples

Name	Type	Req	Description
negocio	string	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

9 Aug 20 Aug

Day	Score
9 Aug	59
10 Aug	60
11 Aug	60
12 Aug	61
13 Aug	61
14 Aug	62
15 Aug	62
16 Aug	62
17 Aug	62
18 Aug	63
19 Aug	63
20 Aug	64