Nombrio Clearance Check

Server Details

Free brand-name Clearance Checks from live registries; connect a plan (API key) for full checks.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-09-15 23:55
Transport: Streamable HTTP
URL

TDQS

A4.6/5.0

Scored 2026-09-10 23:12 across 4 tools

Disambiguation5/5

Each tool has a clearly distinct role: check_name covers a single name, check_names covers batches, start_naming_session initiates an async workflow, and get_naming_session retrieves its results. The singular/plural distinction and start/get lifecycle make misselection unlikely.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: check_name, check_names, start_naming_session, get_naming_session. Verbs are specific and nouns clearly describe the resource or action.

Tool Count5/5

Four tools is well-scoped for this server's purpose: two clearance-check entry points and two naming-session lifecycle operations. Each tool earns its place with no redundant bulk.

Completeness5/5

The tool surface covers the full intended workflow: single-name checks, multi-name screening, starting an async naming session, and polling/results retrieval. There are no obvious dead ends for the stated domain.

Available Tools

4 tools

check_nameClearance Check — one name (free)A

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	The candidate name to check, e.g. 'Lumeo'. Plain name only — no URL, no TLD, no @handle. For several names use check_names.

Output Schema

ParametersJSON Schema

Name	Required	Description
`name`	Yes
`note`	No	Parse correction or why the check is partial.
`plan`	No
`links`	Yes
`quota`	No	Per-caller fair-use quota. Absent on cache hits and degraded paths.
`score`	No
`source`	No
`status`	Yes
`domains`	Yes
`verdict`	Yes
`appStore`	No
`conflicts`	No
`developer`	Yes
`disclaimer`	Yes
`registries`	No
`socialHandles`	Yes
`lockedInFullReport`	Yes

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely useful operational context: live registry data, free/no API key, shared fair-use pool with per-caller daily allowance, Instagram returning a confirm-link, and 'Not legal advice.' These are behavioral details beyond the annotations and schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every segment adds value — scope, result contents, usage triggers, alternative routing, cost/access caveats, and data source. It is front-loaded with the core action and the one-name limitation, and the later sentences deepen rather than repeat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required parameter and an output schema present, the description still covers the full decision context: what the check covers, what the output includes, when this tool is appropriate, when to use check_names, access constraints, and non-legal caveat. Nothing an agent needs to correctly select or invoke it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already instructs 'Plain name only — no URL, no TLD, no @handle' and to use check_names for multiple names. The description reinforces that this checks a single name but does not add much parameter-level meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Run a free Clearance Check on ONE brand, business, product or app name.' It enumerates the exact checks performed (USPTO, EUIPO, domains, social handles, developer namespaces, iOS App Store) and explicitly contrasts itself with check_names, so an agent can distinguish it without inspecting other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: 'Use it when the user asks whether a SPECIFIC name is taken...' and covers everyday naming moments. It also names the alternative for shortlists: 'For a shortlist or comparison use check_names instead' — clear routing to the sibling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

check_namesClearance screen — 2 to 8 names at once (free)A

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`names`	Yes	2-8 candidate names, e.g. ["Lumeo", "Brewly", "Northwind"]. Plain names only — no URLs, no TLDs, no @handles. Duplicates are checked once.

Output Schema

ParametersJSON Schema

Name	Required	Description
`plan`	No
`links`	Yes
`quota`	No	Per-caller fair-use quota. Absent on cache hits and degraded paths.
`checked`	Yes	Names that received a full free-tier answer.
`ranking`	Yes	Names best → worst by viability band; unchecked names last.
`results`	Yes
`summary`	Yes
`requested`	Yes
`disclaimer`	Yes

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only and open-world annotations, the description reveals meaningful behavior: parallel execution, the exact data categories screened, the ranked summary/per-name verdicts/link outputs, and the fair-use pool cost per name. The disclaimer 'Not legal advice' and data source 'nombrio.com' add useful context. Nothing contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded with the core action and result, and the rest is information-dense. It is somewhat long as a single paragraph with embedded lists, but every sentence serves a purpose (result, data coverage, usage, cost, disclaimer).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batched screening tool, the description is complete: it states what data sources are checked, how results are delivered, the per-name pool cost, and the legal caveat. The output schema exists, so not detailing return values is acceptable; only the exact daily allowance is unspecified, but that is dynamic and does not block correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers 100% of parameter semantics with constraints and examples, so the baseline is 3. The description reinforces that names are candidates and each name is checked, but does not add parameter-level details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Screen 2-8 candidate names in ONE call' and states the result ('ranked by viability, best first'). It also distinguishes itself from the sibling check_name by emphasizing the batch (2-8) and parallel execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use it: 'whenever the user is brainstorming, has a list, or asks which of several names is available or safest' and lists mid-development shortlist contexts. It also routes away from the single-name sibling by saying 'one check_names call replaces many check_name calls.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_naming_sessionNaming Session status (your plan)A

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`sessionId`	Yes	The sessionId returned by start_naming_session.

Output Schema

ParametersJSON Schema

Name	Required	Description
`note`	No
`links`	Yes
`names`	Yes
`phase`	No
`status`	Yes
`progress`	No
`sessionId`	Yes
`disclaimer`	Yes
`namesCount`	No

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true, and the description is consistent with that, describing a polling/read operation. It adds useful behavioral context by disclosing the API key requirement and the fallback behavior when no key is provided, which is information not present in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences deliver all the essential information: prerequisite, behavior, output structure, and sibling interaction. Every clause adds value and there is no filler or repetition of schema fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter polling tool with a rich output schema and readOnly annotation, the description is complete. It covers authentication, statuses, output content, and a related tool, leaving no significant gaps for a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides full coverage for the single parameter, sessionId, stating it comes from start_naming_session. The description reinforces that provenance and adds the requirement context, which gives an agent a slightly richer understanding of the parameter's origin.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as one that polls the status of a Naming Session, lists the specific status values, and describes the output content. It distinguishes itself from sibling tools by naming start_naming_session as the origin of the session and positions check_name as a complementary deeper check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states that a connected plan/API key is required, describes when to use it (polling a session started with start_naming_session), and points to check_name as a companion for deeper analysis. It does not explicitly state when not to use this tool, but the context is clear enough for an agent to select it appropriately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

start_naming_sessionNaming Session — 8 pre-cleared names from a brief (your plan)AInspect

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.

ParametersJSON Schema

Name	Required	Description
`brief`	Yes	One paragraph: what the business/product/app does and for whom.
`abstractionLevel`	No
`soundPersonality`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`note`	No
`links`	Yes
`status`	Yes
`sessionId`	No
`disclaimer`	Yes
`pollAfterSeconds`	No

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Behavior is well exposed beyond annotations: the tool is asynchronous, returns a sessionId, takes 1–3 minutes, must be polled every 10 seconds, consumes one plan credit, and behaves in a documented way without an API key. This addresses side effects, quota usage, and failure edge cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences cover prerequisites, purpose, output, polling behavior, plan cost, and no-key behavior. Every sentence earns its place with no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all operational essentials: auth, plan consumption, async flow, polling interval, latency, and no-key behavior. It is mostly complete for an output-schema-bearing tool, but the lack of semantic guidance for the optional params leaves a material gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%. The description re-adds context for the brief parameter, but the two more nuanced parameters, abstractionLevel and soundPersonality, have no descriptions beyond their enum names. The tool description does not compensate for this gap or explain how to choose those values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it starts a Nombrio Naming Session, generates up to 8 name ideas from a brief, and pre-clears them. It also distinguishes itself from siblings by naming get_naming_session as the polling tool and comparing its registries to check_name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear use context: it requires a connected plan, consumes one Naming Session credit, is asynchronous, and should be polled via get_naming_session. It does not explicitly state when to prefer this over the sibling check tools, so it stops short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesAug 29, 2026

Changedcheck_name3 fields changed

addedOutput schema / properties / conflicts / items / properties / classLabels

Added value: +{
+  "description": "Human-readable Nice Classification labels ('9 Electronics & Software'), aligned index-for-index with the numeric class array.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / verdict / properties / conflictClassLabels

Added value: +{
+  "description": "Human-readable Nice Classification labels ('9 Electronics & Software'), aligned index-for-index with the numeric class array.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / verdict / properties / euConflictClassLabels

Added value: +{
+  "description": "Human-readable Nice Classification labels ('9 Electronics & Software'), aligned index-for-index with the numeric class array.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changedcheck_names3 fields changed

addedOutput schema / properties / results / items / properties / conflicts / items / properties / classLabels

Added value: +{
+  "description": "Human-readable Nice Classification labels ('9 Electronics & Software'), aligned index-for-index with the numeric class array.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / verdict / properties / conflictClassLabels

Added value: +{
+  "description": "Human-readable Nice Classification labels ('9 Electronics & Software'), aligned index-for-index with the numeric class array.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / verdict / properties / euConflictClassLabels

Added value: +{
+  "description": "Human-readable Nice Classification labels ('9 Electronics & Software'), aligned index-for-index with the numeric class array.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

2 tool updatesAug 27, 2026

Changedcheck_name1 field changed

addedOutput schema / properties / links / properties / apiAccess

Added value: +{
+  "description": "Connect a plan (API key) — checks then run on the caller's own plan quota, independent of the free pools. Present when this check was capped.",
+  "type": "string"
+}

Changedcheck_names1 field changed

addedOutput schema / properties / results / items / properties / links / properties / apiAccess

Added value: +{
+  "description": "Connect a plan (API key) — checks then run on the caller's own plan quota, independent of the free pools. Present when this check was capped.",
+  "type": "string"
+}

4 tool updatesAug 23, 2026

Changedcheck_name11 fields changed

addedOutput schema / properties / conflicts

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "classes": {
+        "items": {
+          "type": "integer"
+        },
+        "type": "array"
+      },
+      "name": {
+        "type": "string"
+      },
+      "owner": {
+        "type": "string"
+      },
+      "registries": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "similarity": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "name",
+      "registries",
+      "similarity"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / links / properties / report

Added value: +{
+  "description": "Full interactive result on the caller's plan.",
+  "type": "string"
+}

addedOutput schema / properties / links / properties / upgrade

Added value: +{
+  "description": "Where to get a plan (pricing).",
+  "type": "string"
+}

addedOutput schema / properties / plan

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "checksLimit": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksRemaining": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksUsed": {
+      "type": "integer"
+    },
+    "resetsAt": {
+      "type": "string"
+    },
+    "tier": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tier"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / registries

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "eu": {
+      "$ref": "#/properties/registries/properties/us"
+    },
+    "uk": {
+      "$ref": "#/properties/registries/properties/us"
+    },
+    "us": {
+      "additionalProperties": false,
+      "properties": {
+        "matches": {
+          "type": "integer"
+        },
+        "reason": {
+          "type": "string"
+        },
+        "status": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "matches"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "us",
+    "eu",
+    "uk"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / score

Added value: +{
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / source

Added value: +{
+  "enum": [
+    "free",
+    "plan"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / verdict / properties / confidence / const
```
Removed value: -"low"
```
addedOutput schema / properties / verdict / properties / confidence / enum
```
Added value: +[
+  "low",
+  "high"
+]
```

changedOutput schema / properties / verdict / properties / coverage / enum

Previous value: -[
-  "US",
-  "US+EU"
-]New value: +[
+  "US",
+  "US+EU",
+  "US+EU+UK"
+]

changedOutput schema / properties / verdict / required

Previous value: -[
-  "coverage",
-  "confidence",
-  "capped"
-]New value: +[
+  "confidence",
+  "capped"
+]

Changedcheck_names14 fields changed

changedOutput schema / properties / links / properties / apiAccess / description

Previous value: -"Higher limits for agents/products (request access)."New value: +"Connect your plan for higher limits and EU/UK data."

addedOutput schema / properties / links / properties / apiKeys

Added value: +{
+  "description": "Manage/create API keys to connect a plan.",
+  "type": "string"
+}

addedOutput schema / properties / plan

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "checksLimit": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksRemaining": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksUsed": {
+      "type": "integer"
+    },
+    "resetsAt": {
+      "type": "string"
+    },
+    "tier": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tier"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / conflicts

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "classes": {
+        "items": {
+          "type": "integer"
+        },
+        "type": "array"
+      },
+      "name": {
+        "type": "string"
+      },
+      "owner": {
+        "type": "string"
+      },
+      "registries": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "similarity": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "name",
+      "registries",
+      "similarity"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / links / properties / report

Added value: +{
+  "description": "Full interactive result on the caller's plan.",
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / links / properties / upgrade

Added value: +{
+  "description": "Where to get a plan (pricing).",
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / plan

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "checksLimit": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksRemaining": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksUsed": {
+      "type": "integer"
+    },
+    "resetsAt": {
+      "type": "string"
+    },
+    "tier": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tier"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / registries

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "eu": {
+      "$ref": "#/properties/results/items/properties/registries/properties/us"
+    },
+    "uk": {
+      "$ref": "#/properties/results/items/properties/registries/properties/us"
+    },
+    "us": {
+      "additionalProperties": false,
+      "properties": {
+        "matches": {
+          "type": "integer"
+        },
+        "reason": {
+          "type": "string"
+        },
+        "status": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "matches"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "us",
+    "eu",
+    "uk"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / score

Added value: +{
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / results / items / properties / source

Added value: +{
+  "enum": [
+    "free",
+    "plan"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / results / items / properties / verdict / properties / confidence / const
```
Removed value: -"low"
```
addedOutput schema / properties / results / items / properties / verdict / properties / confidence / enum
```
Added value: +[
+  "low",
+  "high"
+]
```
changedOutput schema / properties / results / items / properties / verdict / properties / coverage / enum
```
Previous value: -[
-  "US",
-  "US+EU"
-]New value: +[
+  "US",
+  "US+EU",
+  "US+EU+UK"
+]
```

changedOutput schema / properties / results / items / properties / verdict / required

Previous value: -[
-  "coverage",
-  "confidence",
-  "capped"
-]New value: +[
+  "confidence",
+  "capped"
+]

Addedget_naming_session
Addedstart_naming_session

2 tool updatesAug 23, 2026

Changedcheck_name2 fields changed

changedInput schema / properties / name / description

Previous value: -"The candidate name to check, e.g. 'Lumeo'. Plain name only — no URL, no TLD, no @handle. One name per call."New value: +"The candidate name to check, e.g. 'Lumeo'. Plain name only — no URL, no TLD, no @handle. For several names use check_names."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "appStore": {
+      "additionalProperties": false,
+      "properties": {
+        "matchCount": {
+          "type": "integer"
+        },
+        "verdict": {
+          "enum": [
+            "clear",
+            "similar",
+            "conflict",
+            "unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "verdict",
+        "matchCount"
+      ],
+      "type": "object"
+    },
+    "developer": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "available": {
+            "type": "boolean"
+          },
+          "namespace": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "namespace",
+          "available"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "disclaimer": {
+      "const": "Not legal advice.",
+      "type": "string"
+    },
+    "domains": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "available": {
+            "type": "boolean"
+          },
+          "priceUsd": {
+            "type": "number"
+          },
+          "tld": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "tld",
+          "available"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "links": {
+      "additionalProperties": false,
+      "properties": {
+        "fullResult": {
+          "description": "Full interactive result (free).",
+          "type": "string"
+        }
+      },
+      "required": [
+        "fullResult"
+      ],
+      "type": "object"
+    },
+    "lockedInFullReport": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "description": "Parse correction or why the check is partial.",
+      "type": "string"
+    },
+    "quota": {
+      "additionalProperties": false,
+      "description": "Per-caller fair-use quota. Absent on cache hits and degraded paths.",
+      "properties": {
+        "limit": {
+          "description": "Free checks per caller per UTC day.",
+          "type": "integer"
+        },
+        "resetsAt": {
+          "description": "ISO timestamp of the next UTC midnight reset.",
+          "type": "string"
+        },
+        "used": {
+          "description": "Free checks this caller has used today (UTC).",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "used",
+        "limit",
+        "resetsAt"
+      ],
+      "type": "object"
+    },
+    "socialHandles": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "available": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "confirmUrl": {
+            "type": "string"
+          },
+          "platform": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "platform",
+          "available"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "enum": [
+        "ok",
+        "capped",
+        "invalid",
+        "error"
+      ],
+      "type": "string"
+    },
+    "verdict": {
+      "additionalProperties": false,
+      "properties": {
+        "capped": {
+          "type": "boolean"
+        },
+        "confidence": {
+          "const": "low",
+          "type": "string"
+        },
+        "conflictClasses": {
+          "items": {
+            "type": "integer"
+          },
+          "type": "array"
+        },
+        "conflictCount": {
+          "type": "integer"
+        },
+        "coverage": {
+          "enum": [
+            "US",
+            "US+EU"
+          ],
+          "type": "string"
+        },
+        "euConflictClasses": {
+          "items": {
+            "type": "integer"
+          },
+          "type": "array"
+        },
+        "euConflictCount": {
+          "type": "integer"
+        },
+        "euTrademarkRisk": {
+          "enum": [
+            "clear",
+            "conflict"
+          ],
+          "type": "string"
+        },
+        "trademarkRisk": {
+          "enum": [
+            "clear",
+            "caution",
+            "conflict"
+          ],
+          "type": "string"
+        },
+        "viabilityBand": {
+          "enum": [
+            "strong",
+            "caution",
+            "blockers",
+            "high-risk"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "coverage",
+        "confidence",
+        "capped"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "name",
+    "status",
+    "verdict",
+    "domains",
+    "socialHandles",
+    "developer",
+    "links",
+    "lockedInFullReport",
+    "disclaimer"
+  ],
+  "type": "object"
+}

Addedcheck_names

1 tool updateJul 9, 2026
- First observedcheck_name

Related MCP Connectors

Domain Finder A
io.github.Sra1Phani
Check if a brand name is free across domains, GitHub, npm and PyPI, and suggest available names.
Search Developer Tools
22
name-tools
com.startupnamegenerator
Generate startup names with an available .com, checked live, then screen US and EU trademarks.
Marketing Legal & Compliance Web Scraping
2
DomainCheckr A
io.github.nach-dakwale
Check domain name availability via RDAP. Single, bulk, and smart suggestions. No API key needed.
Search Web Scraping
32
snooze A
domains.snooze
Watch domains and forecast when they drop; check a name's domain, handles, and trademark.
Networking & Infrastructure Monitoring
52

Related MCP Servers

ip-free-mcp
Legal & Compliance Open Data Government Data
AI-AlexBaum
A
license
A
quality
B
maintenance
Enables trademark clearance and research across EU and Benelux registers, plus company, group-structure, and EU VAT lookups, all through free public sources without API keys.
Updated 19 days ago (2026-08-28 03:24 UTC)
14
MIT
Domain Checker
Search Developer Tools
nach-dakwale
A
license
Not graded
quality
F
maintenance
Check domain name availability via RDAP. Single lookups, bulk checks (up to 50), and smart name suggestions with registration links. No API key needed.
Updated 6 months ago (2026-03-13 23:30 UTC)
MIT
io.github.siddmax/namera
Marketing Legal & Compliance
solozerolabs
A
license
Not graded
quality
A
maintenance
Enables AI agents to check and rank startup name candidates by domain availability, trademark conflicts, and social handle availability, with optional name generation and scoring profiles.
Updated 12 days ago (2026-09-03 20:37 UTC)
4
MIT
Startup Name Generator MCPofficial
Marketing Legal & Compliance
startupnamegenerator
A
license
Not graded
quality
C
maintenance
Generates startup names with live .com availability checks and screens them against US and EU trademark registers.
Updated 3 months ago (2026-06-26 13:38 UTC)
65 npm
MIT