# mexsaas (remote · www.mexsaas.com)

Software que usan los negocios en México: busca, compara y ve alternativas, con precio en pesos.

- Trust score: 87/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-07

## Components

- remote · `www.mexsaas.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-mexsaas-mcp/www.md), [page](https://verifymcp.io/servers/com-mexsaas-mcp/www)

## Channel facts

- Endpoint: `https://www.mexsaas.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1016 tokens (~127/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the mexsaas MCP server?

mexsaas is a hosted endpoint at https://www.mexsaas.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.

### Claude

```bash
claude mcp add --transport http com-mexsaas-mcp 'https://www.mexsaas.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mexsaas-mcp": {
      "url": "https://www.mexsaas.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mexsaas-mcp": {
      "type": "http",
      "url": "https://www.mexsaas.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mexsaas-mcp]
url = "https://www.mexsaas.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-mexsaas-mcp --url 'https://www.mexsaas.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mexsaas-mcp:
    url: "https://www.mexsaas.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mexsaas-mcp": {
      "Transport": "http",
      "Url": "https://www.mexsaas.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mexsaas-mcp -t streamable-http -u 'https://www.mexsaas.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mexsaas-mcp": {
      "type": "http",
      "url": "https://www.mexsaas.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-07 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-11-06 (score 87, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 87, 0)

- [functional] Stability: pass → 0.97

### 2026-11-02 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 86, +1)

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

### 2026-10-28 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `buscar_software_mx` (~240 tokens)

Buscar software en México

Busca en el directorio de mexsaas el software que resuelve lo que necesita un negocio en México. Acepta texto libre en español y filtros opcionales. Devuelve productos con precio, plan gratis, soporte, país de origen y su ficha.

Input parameters:

- `categoria` (string): Slug de categoría (lista en categorias_mx).
- `consulta` (string): Lo que necesita el negocio en palabras normales, ej. 'facturar sin contador'. Puede ir vacío si usas filtros.
- `limite` (integer): Cuántos resultados (máx. 25).
- `negocio` (string): Tipo de negocio, ej. 'restaurantes', 'contadores', 'tienditas'.
- `origen` (string): Hecho en México o de otro país.
- `plan_gratis` (boolean): true: solo con plan gratis.
- `precio_max_mxn` (number): Precio de entrada máximo en MXN. Excluye productos sin precio publicado.
- `tarea` (string): Necesidad concreta, ej. 'facturar', 'cobrar', 'nomina', 'agendar-citas'.

### `ficha_software_mx` (~73 tokens)

Ficha de un producto

Ficha completa de un producto del directorio: qué hace, funciones, integraciones, precio, plan gratis, soporte, país, lugar en su categoría, alternativas y páginas de comparación.

Input parameters:

- `producto` (string, required): Slug o nombre del producto, ej. 'bind-erp' o 'Bind'.

### `alternativas_mx` (~77 tokens)

Alternativas a un producto

Productos que resuelven lo mismo que otro (misma categoría o mismas tareas), sin mezclar software hecho para otros giros.

Input parameters:

- `limite` (integer): Cuántos resultados (máx. 15).
- `producto` (string, required): Slug o nombre del producto, ej. 'bind-erp' o 'Bind'.

### `comparar_software_mx` (~93 tokens)

Comparar dos productos

Compara dos productos lado a lado: datos de cada uno, en qué se parecen y cuándo conviene elegir cada uno, calculado solo con datos publicados.

Input parameters:

- `producto_a` (string, required): Slug o nombre del producto, ej. 'bind-erp' o 'Bind'.
- `producto_b` (string, required): Slug o nombre del producto, ej. 'bind-erp' o 'Bind'.

### `mejores_para_negocio_mx` (~92 tokens)

Mejores software para un tipo de negocio

El kit de software para un tipo de negocio en México (abogados, restaurantes, tienditas…), agrupado por necesidad: facturar, cobrar, nómina, etc.

Input parameters:

- `negocio` (string, required): Tipo de negocio, ej. 'restaurantes', 'contadores', 'tienditas'.
- `por_tarea` (integer): Productos por necesidad (máx. 5).

### `mejores_para_tarea_mx` (~120 tokens)

Mejores software para una necesidad

Ranking de software para una necesidad concreta (facturar, cobrar, nómina, punto de venta…), opcionalmente solo lo que le sirve a un tipo de negocio.

Input parameters:

- `limite` (integer): Cuántos resultados (máx. 25).
- `negocio` (string): Tipo de negocio, ej. 'restaurantes', 'contadores', 'tienditas'.
- `tarea` (string, required): Necesidad concreta, ej. 'facturar', 'cobrar', 'nomina', 'agendar-citas'.

### `ranking_mx` (~81 tokens)

Ranking de mexsaas

Ranking orgánico de mexsaas (uso real; nadie paga por su lugar), general o de una categoría, del mes, del año o histórico.

Input parameters:

- `categoria` (string): Slug de categoría (lista en categorias_mx).
- `limite` (integer): Cuántos resultados (máx. 25).
- `periodo` (string)

### `categorias_mx` (~42 tokens)

Categorías, negocios y necesidades

Lista las categorías del directorio (con cuántos productos tiene cada una), los tipos de negocio y las necesidades que aceptan los filtros de las demás herramientas.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mexsaas-mcp/www#diagnostics

## Score history

- 2026-11-07: 87
- 2026-11-06: 87
- 2026-11-05: 87
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 87
- 2026-10-31: 86
- 2026-10-30: 86
- 2026-10-29: 85
- 2026-10-28: 85
- 2026-10-27: 84
- 2026-10-26: 84
- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 80
- 2026-10-16: 79
- 2026-10-15: 79
- 2026-10-14: 78
- 2026-10-13: 78
- 2026-10-12: 77
- 2026-10-10: 77
- 2026-10-08: 76
- 2026-10-06: 75

## Common questions

### What is the mexsaas MCP server?

mexsaas is an MCP server listed in the public MCP registry as com.mexsaas/mcp. Software que usan los negocios en México: busca, compara y ve alternativas, con precio en pesos. This page covers its hosted endpoint (https://www.mexsaas.com/mcp).

### Is the mexsaas MCP server safe to use?

mexsaas scores 87 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 mexsaas MCP server expose?

mexsaas exposes 8 tools: buscar_software_mx, ficha_software_mx, alternativas_mx, comparar_software_mx, mejores_para_negocio_mx, and 3 more. Their descriptions and schemas cost roughly 818 tokens of context every time the server is loaded.

### Does the mexsaas MCP server require authentication?

No. We connected to mexsaas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the mexsaas MCP server still maintained?

mexsaas is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the mexsaas MCP server?

VerifyMCP ran 13 checks on mexsaas, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.mexsaas.com/mcp
- Website: https://www.mexsaas.com/ia
- Changelog RSS feed: https://verifymcp.io/servers/com-mexsaas-mcp/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mexsaas-mcp/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-mexsaas-mcp/www.json
- HTML version of this page: https://verifymcp.io/servers/com-mexsaas-mcp/www