Nombrio Clearance Check
REMOTE · NOMBRIO.COM · SCANNED SEP 22
Free brand-name Clearance Checks from live registries; connect a plan (API key) for full checks.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 960 tokens (~240/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Nombrio Clearance Check MCP server?
Nombrio Clearance Check is a hosted endpoint at https://nombrio.com/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 · nombrio.com
claude mcp add --transport http com-nombrio-name-check 'https://nombrio.com/api/mcp'
{
"mcpServers": {
"com-nombrio-name-check": {
"url": "https://nombrio.com/api/mcp"
}
}
} {
"servers": {
"com-nombrio-name-check": {
"type": "http",
"url": "https://nombrio.com/api/mcp"
}
}
} [mcp_servers.com-nombrio-name-check] url = "https://nombrio.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-nombrio-name-check": {
"type": "remote",
"url": "https://nombrio.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-nombrio-name-check --url 'https://nombrio.com/api/mcp' --transport streamable-http
mcp_servers:
com-nombrio-name-check:
url: "https://nombrio.com/api/mcp" {
"McpServers": {
"com-nombrio-name-check": {
"Transport": "http",
"Url": "https://nombrio.com/api/mcp"
}
}
} assistant mcp add com-nombrio-name-check -t streamable-http -u 'https://nombrio.com/api/mcp'
{
"mcpServers": {
"com-nombrio-name-check": {
"type": "http",
"url": "https://nombrio.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 30 Aug 26 −1
- Tool “check_name” rewrote its description, which is the text the model reads security
- Tool “check_names” rewrote its description, which is the text the model reads security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 23 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_name” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 67% ▼ functional
- Schema quality: 284 → 561 ▼ functional
- Schema quality: 284 → 220 ▲ functional
- Tool “check_name” now declares an output schema ▲ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- First check of Tool coverage: 100 functional
- New prompt “naming-session” functional
- Server version: 1.2.0 → 1.2.1 functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “get_naming_session” functional
- New tool “start_naming_session” functional
- New tool “check_names” functional
- “check_name” reworded the description of “name” cosmetic
- Tool “check_name” changed its title: Check name availability → Clearance Check — one name (free) cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 22 Sept 2026 · Probed https://nombrio.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.nombrio.com | CN=YR2,O=Let's Encrypt,C=US | 5 Aug 2026 | 3 Nov 2026 | RSA 2048 | SHA256-RSA | 5971f4849c8d7f2418491a7fb4f24a29f25 |
| SANs: *.nombrio.com, nombrio.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nombrio.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nombrio.com. | 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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://clerk.nombrio.com https://*.clerk.accounts.dev https://va.vercel-scripts.com https://vercel.live https://challenges.cloudflare.com https://*.hcaptcha.com https://hcaptcha.com; style-src 'self' 'unsafe-inline' https://vercel.live https://challenges.cloudflare.com https://*.hcaptcha.com https://hcaptcha.com; img-src 'self' data: blob: https://clerk.nombrio.com https://*.clerk.com https://img.clerk.com https://vercel.live https://vercel.com; font-src 'self' data: https://fonts.gstatic.com https://vercel.live; connect-src 'self' https://clerk.nombrio.com https://*.clerk.com https://*.clerk.accounts.dev https://clerk-telemetry.com https://api.nombrio.com https://api-dev.nombrio.com https://api.stripe.com https://va.vercel-scripts.com https://vitals.vercel-insights.com https://vercel.live wss://ws-us3.pusher.com https://challenges.cloudflare.com https://*.hcaptcha.com https://hcaptcha.com https://*.s3.eu-central-1.amazonaws.com; frame-src h |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self), xr-spatial-tracking=*, accelerometer=*, gyroscope=*, magnetometer=*, publickey-credentials-get=* |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nombrio.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://nombrio.com/api/mcp | HTTPS enforced | 308 | https://nombrio.com/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 →
check_name Clearance Check — one name (free) ~313
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The candidate name to check, e.g. 'Lumeo'. Plain name only — no URL, no TLD, no @handle. For several names use check_names. |
| Name | Type | Req | Description |
|---|---|---|---|
| appStore | object | – | – |
| conflicts | array | – | – |
| developer | array | yes | – |
| disclaimer | string | yes | – |
| domains | array | yes | – |
| links | object | yes | – |
| lockedInFullReport | array | yes | – |
| name | string | yes | – |
| note | string | – | Parse correction or why the check is partial. |
| plan | object | – | – |
| quota | object | – | Per-caller fair-use quota. Absent on cache hits and degraded paths. |
| registries | object | – | – |
| score | integer | – | – |
| socialHandles | array | yes | – |
| source | string | – | – |
| status | string | yes | – |
| verdict | object | yes | – |
No examples provided.
check_names Clearance screen — 2 to 8 names at once (free) ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | 2-8 candidate names, e.g. ["Lumeo", "Brewly", "Northwind"]. Plain names only — no URLs, no TLDs, no @handles. Duplicates are checked once. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked | integer | yes | Names that received a full free-tier answer. |
| disclaimer | string | yes | – |
| links | object | yes | – |
| plan | object | – | – |
| quota | – | – | Per-caller fair-use quota. Absent on cache hits and degraded paths. |
| ranking | array | yes | Names best → worst by viability band; unchecked names last. |
| requested | integer | yes | – |
| results | array | yes | – |
| summary | object | yes | – |
No examples provided.
get_naming_session Naming Session status (your plan) ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | The sessionId returned by start_naming_session. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | string | yes | – |
| links | object | yes | – |
| names | array | yes | – |
| namesCount | integer | – | – |
| note | string | – | – |
| phase | string | – | – |
| progress | number | – | – |
| sessionId | string | yes | – |
| status | string | yes | – |
No examples provided.
start_naming_session Naming Session — 8 pre-cleared names from a brief (your plan) ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| abstractionLevel | string | – | – |
| brief | string | yes | One paragraph: what the business/product/app does and for whom. |
| soundPersonality | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | string | yes | – |
| links | object | yes | – |
| note | string | – | – |
| pollAfterSeconds | integer | – | – |
| sessionId | string | – | – |
| status | string | yes | – |
No examples provided.
What is the Nombrio Clearance Check MCP server?
Nombrio Clearance Check is an MCP server listed in the public MCP registry as com.nombrio/name-check. Free brand-name Clearance Checks from live registries; connect a plan (API key) for full checks. This page covers its hosted endpoint (https://nombrio.com/api/mcp).
Is the Nombrio Clearance Check MCP server safe to use?
Nombrio Clearance Check 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 Nombrio Clearance Check MCP server expose?
Nombrio Clearance Check exposes 4 tools: check_name, check_names, start_naming_session, get_naming_session. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.
Does the Nombrio Clearance Check MCP server require authentication?
No. We connected to Nombrio Clearance Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nombrio Clearance Check MCP server still maintained?
Nombrio Clearance Check is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.