# Namli (remote · namli.vercel.app)

Checks if a project, brand or app name already exists: trademarks, domains, web and GitHub.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `namli.vercel.app`: 80/100 (this document), [markdown](https://verifymcp.io/servers/astrolions93-namli/api-mcp.md), [page](https://verifymcp.io/servers/astrolions93-namli/api-mcp)

## Channel facts

- Endpoint: `https://namli.vercel.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-10-24.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 541 tokens (~180/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 70% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

Namli is a hosted endpoint at https://namli.vercel.app/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.

### Claude

```bash
claude mcp add --transport http astrolions93-namli 'https://namli.vercel.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "astrolions93-namli": {
      "url": "https://namli.vercel.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "astrolions93-namli": {
      "type": "http",
      "url": "https://namli.vercel.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.astrolions93-namli]
url = "https://namli.vercel.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "astrolions93-namli": {
      "type": "remote",
      "url": "https://namli.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add astrolions93-namli --url 'https://namli.vercel.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  astrolions93-namli:
    url: "https://namli.vercel.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "astrolions93-namli": {
      "Transport": "http",
      "Url": "https://namli.vercel.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add astrolions93-namli -t streamable-http -u 'https://namli.vercel.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "astrolions93-namli": {
      "type": "http",
      "url": "https://namli.vercel.app/api/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-10-22 (score 80, +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.

### 2026-10-20 (score 79, +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.

### 2026-10-18 (score 78, +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.

### 2026-10-16 (score 77, +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.

### 2026-10-14 (score 76, +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.

### 2026-10-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 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.

### 2026-10-10 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 27. That category is still filling its 30-day observation window: 5 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.

### 2026-10-07 (score 73, +2)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 17. That category is still filling its 30-day observation window: 2 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.

## MCP tools (3)

### `verificar_nombre` (~273 tokens)

Verificar un nombre de proyecto

Revisa si un nombre de proyecto, marca, app o empresa YA EXISTE o se parece mucho a otro en la misma industria. Busca en marcas registradas (SIC Colombia y, si está configurada, EUIPO), dominios (.com, .co, .app, .io, .net y el del país, más variantes con palabras del rubro como «nombre+vet»), la web, GitHub y npm. Devuelve un veredicto (libre 🟢 / parecido 🟡 / ocupado 🔴) con pruebas, enlaces y fechas. ÚSALA SIEMPRE antes de recomendar un nombre a una persona. Si el veredicto es «ocupado», no lo recomiendes: propone otro y verifícalo. Tarda de 10 a 40 segundos porque consulta registros oficiales. No es un concepto jurídico.

Input parameters:

- `descripcion` (string, required): De qué es el proyecto, en una frase. Es clave para saber qué choques importan, p. ej. «software para veterinarias en Colombia».
- `nombre` (string, required): El nombre a revisar, p. ej. «LatidoPet».
- `pais` (string): País principal (nombre o código de 2 letras), p. ej. «Colombia» o «CH».

### `verificar_nombres` (~98 tokens)

Revisar una lista de nombres (rápido)

Revisión RÁPIDA de varios nombres a la vez (hasta 10): dominios, web y npm, sin marcas registradas. Úsala para filtrar una lista de ideas que tú mismo generaste; luego pasa el o los mejores por verificar_nombre para la revisión completa.

Input parameters:

- `descripcion` (string, required): De qué es el proyecto.
- `nombres` (array, required): Los nombres a revisar.
- `pais` (string)

### `sugerir_nombres` (~107 tokens)

Sugerir nombres libres

Propone nombres para un proyecto a partir de su descripción (y de palabras semilla opcionales) y devuelve primero los que están libres. Es un respaldo: si puedes, genera tus propias ideas y revísalas con verificar_nombres, que da mejores nombres.

Input parameters:

- `cuantos` (integer)
- `descripcion` (string, required): De qué es el proyecto.
- `pais` (string)
- `semillas` (array): Palabras que le gustan a la persona (opcional).

## Diagnostics

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

## Score history

- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-10: 74
- 2026-10-07: 73
- 2026-10-04: 71
- 2026-10-03: 71
- 2026-10-02: 70

## Common questions

### What is the Namli MCP server?

Namli is an MCP server listed in the public MCP registry as io.github.Astrolions93/namli. Checks if a project, brand or app name already exists: trademarks, domains, web and GitHub. This page covers its hosted endpoint (https://namli.vercel.app/api/mcp).

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

Namli scores 80 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 Namli MCP server expose?

Namli exposes 3 tools: verificar_nombre, verificar_nombres, sugerir_nombres. Their descriptions and schemas cost roughly 478 tokens of context every time the server is loaded.

### Does the Namli MCP server require authentication?

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

### Is the Namli MCP server still maintained?

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

## Links

- Remote endpoint: https://namli.vercel.app/api/mcp
- Website: https://namli.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/astrolions93-namli/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/astrolions93-namli/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/astrolions93-namli/api-mcp