Koskamo

Namli MCP

Checks if a project, brand, or app name already exists by searching trademarks, domains, web, GitHub, and npm. Returns a traffic-light verdict (free, similar, occupied) with evidence, links, and dates. Supports single name verification, batch checking, and name suggestion based on descriptions.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Namli MCP logo, by NamliCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Namli
MCP endpoint (Streamable HTTP)
https://namli.vercel.app/api/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

3 of 3 have a description · 3 of 3 declare behavior hints · 1 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Check if a specific project or brand name is available
  • Batch verify multiple names for domain and trademark conflicts
  • Suggest available names based on a project description

Source and maintenance

Community listingRegistry 0.1.0

Protocol and capabilities

Server
namli 0.2.0
MCP protocol negotiated in check
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Usa verificar_nombre antes de recomendar cualquier nombre de proyecto, marca o app. Para revisar varias ideas a la vez usa verificar_nombres (rápido) y luego verificar_nombre con la elegida. Responde en el idioma de la persona y muestra el semáforo y los enlaces de prueba.

Tools

3 advertised

verificar_nombre — Verificar un nombre de proyecto
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

verificar_nombre input schema
{
  "type": "object",
  "required": [
    "nombre",
    "descripcion"
  ],
  "properties": {
    "pais": {
      "type": "string",
      "description": "País principal (nombre o código de 2 letras), p. ej. «Colombia» o «CH»."
    },
    "nombre": {
      "type": "string",
      "description": "El nombre a revisar, p. ej. «LatidoPet»."
    },
    "descripcion": {
      "type": "string",
      "description": "De qué es el proyecto, en una frase. Es clave para saber qué choques importan, p. ej. «software para veterinarias en Colombia»."
    }
  }
}
verificar_nombre annotations
{
  "readOnlyHint": true,
  "openWorldHint": true
}
verificar_nombres — Revisar una lista de nombres (rápido)
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

verificar_nombres input schema
{
  "type": "object",
  "required": [
    "nombres",
    "descripcion"
  ],
  "properties": {
    "pais": {
      "type": "string"
    },
    "nombres": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 10,
      "description": "Los nombres a revisar."
    },
    "descripcion": {
      "type": "string",
      "description": "De qué es el proyecto."
    }
  }
}
verificar_nombres annotations
{
  "readOnlyHint": true,
  "openWorldHint": true
}
sugerir_nombres — Sugerir nombres libres
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

sugerir_nombres input schema
{
  "type": "object",
  "required": [
    "descripcion"
  ],
  "properties": {
    "pais": {
      "type": "string"
    },
    "cuantos": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1
    },
    "semillas": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Palabras que le gustan a la persona (opcional)."
    },
    "descripcion": {
      "type": "string",
      "description": "De qué es el proyecto."
    }
  }
}
sugerir_nombres annotations
{
  "readOnlyHint": true,
  "openWorldHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (3 of 3 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1499 ms
95th percentile latency
1499 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1499 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http namli-mcp https://namli.vercel.app/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add namli-mcp --url https://namli.vercel.app/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable namli-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "namli-mcp": {
      "url": "https://namli.vercel.app/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "namli-mcp": {
      "type": "streamableHttp",
      "url": "https://namli.vercel.app/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start namli-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "namli-mcp": {
      "type": "http",
      "url": "https://namli.vercel.app/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http namli-mcp https://namli.vercel.app/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://namli.vercel.app/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "namli-mcp": {
      "serverUrl": "https://namli.vercel.app/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Namli MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.