Namli
REMOTE · NAMLI.VERCEL.APP
Checks if a project, brand or app name already exists: trademarks, domains, web and GitHub.
Available components
Last scanned (11 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Search and Retrieval
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 14 Oct 26 +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.
- 12 Oct 26 +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.
- 10 Oct 26 +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.
- 7 Oct 26 +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.
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 24 Oct 2026 · Probed https://namli.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of namli.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://namli.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://namli.vercel.app/api/mcp | HTTPS enforced | 308 | https://namli.vercel.app/api/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 →
sugerir_nombres Sugerir nombres libres ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cuantos | integer | – | – |
| descripcion | string | yes | De qué es el proyecto. |
| pais | string | – | – |
| semillas | array | – | Palabras que le gustan a la persona (opcional). |
No output schema declared.
No examples provided.
verificar_nombre Verificar un nombre de proyecto ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| descripcion | string | yes | De qué es el proyecto, en una frase. Es clave para saber qué choques importan, p. ej. «software para veterinarias en Colombia». |
| nombre | string | yes | El nombre a revisar, p. ej. «LatidoPet». |
| pais | string | – | País principal (nombre o código de 2 letras), p. ej. «Colombia» o «CH». |
No output schema declared.
No examples provided.
verificar_nombres Revisar una lista de nombres (rápido) ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| descripcion | string | yes | De qué es el proyecto. |
| nombres | array | yes | Los nombres a revisar. |
| pais | string | – | – |
No output schema declared.
No examples provided.
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.
remote · namli.vercel.app
claude mcp add --transport http astrolions93-namli 'https://namli.vercel.app/api/mcp'
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.