com.nombrio/name-check

Est-ce que com.nombrio/name-check est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.nombrio/name-check » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 4 outils

• check_name≈ 1716 tokens

  Run a free Clearance Check on ONE brand, business, product or app name. Live registry data, not guesses: US trademark verdict (USPTO — clear / caution / conflict with a count of live registrations), a count-only EU trademark screen (EUIPO), domain availability with prices (.com .io .co .app .dev), social handles (X/Twitter, TikTok, LinkedIn, Facebook; Instagram returns a confirm-link), developer namespaces (npm, PyPI, crates.io, GitHub, Docker Hub), the iOS App Store, and an overall viability band (strong / caution / blockers / high-risk) plus a link to the full interactive result. Use it when the user asks whether a SPECIFIC name is taken, trademarked, available or safe to use — and also at everyday developer naming moments: naming a new project, app, product, repo, package, CLI or domain while scaffolding, before publishing to npm/PyPI/crates.io, or whenever a name is being chosen in passing (the namespaces it checks are exactly those). For a shortlist or comparison use check_names instead — one call, all names in parallel, ranked. Free, no API key; shared fair-use pool with a per-caller daily allowance. Not legal advice. Data by nombrio.com.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    The candidate name to check, e.g. 'Lumeo'. Plain name only — no URL, no TLD, no @handle. For several names use check_names.

  Exemple d'appel

  {"name": "check_name", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "note": "texte", "plan": {}, "links": {}, "quota": {}, "score": 1, "source": "free", "status": "ok", "domains": [], "verdict": {}, "appStore": {}, "conflicts": []}}

• check_names≈ 2109 tokens

  Screen 2-8 candidate names in ONE call and get them ranked by viability (best first). Runs the same live free Clearance Check as check_name for every name in parallel — US trademark verdict, count-only EU trademark screen, domains with prices, social handles, developer namespaces, iOS App Store — and returns a ranked summary, per-name verdicts and full-result links. Use it whenever the user is brainstorming, has a list, or asks which of several names is available or safest — including shortlists of project, package, repo, app or domain names that come up mid-development: one check_names call replaces many check_name calls and finishes in about the time of one. Each name counts as one check against the free fair-use pool (per-caller daily allowance). Not legal advice. Data by nombrio.com.

  Paramètres, retour & exemple (1)

  Paramètres

  • names · array · requis
    2-8 candidate names, e.g. ["Lumeo", "Brewly", "Northwind"]. Plain names only — no URLs, no TLDs, no @handles. Duplicates are checked once.

  Exemple d'appel

  {"name": "check_names", "arguments": {"names": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"plan": {}, "links": {}, "quota": "texte", "checked": 1, "ranking": [], "results": [], "summary": {}, "requested": 1, "disclaimer": "texte"}}

• get_naming_session≈ 484 tokens

  Requires a connected plan (API key). Polls the status of a Naming Session started with start_naming_session: pending/generating/checking/complete/failed, plus the ranked name list (score, trademark/domain/social status) once complete — pair with check_name's Clearance Check for a deeper read on the favourite. Without a key it returns instructions to connect a plan.

  Paramètres, retour & exemple (1)

  Paramètres

  • sessionId · string · requis
    The sessionId returned by start_naming_session.

  Exemple d'appel

  {"name": "get_naming_session", "arguments": {"sessionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "links": {}, "names": [], "phase": "texte", "status": "pending", "progress": 1, "sessionId": "texte", "disclaimer": "texte", "namesCount": 1}}

• start_naming_session≈ 464 tokens

  Requires a connected plan (API key). Starts a Nombrio Naming Session: from a one-paragraph brief, generates up to 8 name ideas and pre-clears each with the same Clearance Check registries as check_name (US+EU+UK trademark, domains, social handles). Asynchronous — returns a sessionId; poll get_naming_session every ~10 s; typically 1–3 minutes. Uses one Naming Session from the plan (Clearance Report 10/30 days, Pro 30/month, Premium unlimited). Without a key it returns instructions to connect a plan.

  Paramètres, retour & exemple (3)

  Paramètres

  • brief · string · requis
    One paragraph: what the business/product/app does and for whom.
  • abstractionLevel · string · optionnel · literal | suggestive | abstract
  • soundPersonality · string · optionnel · soft-trustworthy | sharp-precise | warm-playful | premium-restrained

  Exemple d'appel

  {"name": "start_naming_session", "arguments": {"brief": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "links": {}, "status": "started", "sessionId": "texte", "disclaimer": "texte", "pollAfterSeconds": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://nombrio.com/api/mcp