Nombrio Clearance Check MCP server
com.nombrio/name-checknombrio.comstreamable-httpv1.2.2Scanned
Free brand name checks: US trademark verdict, EU + UK screens, domains, handles. Plans via API key.
4 tools: 3 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Nombrio Clearance Check MCP server can do
The Nombrio Clearance Check MCP server is published by nombrio.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: check_name, check_names and start_naming_session), but cannot delete data. 1 tool only reads.
4 tools bring in text other people can write (check_name, check_names, start_naming_session and 1 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.2.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 3Claude Code: ask
check_nameRun a free Clearance Check on ONE brand, business, product or app name.Reads text others write1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "check_name" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
Description, as the server wrote it 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), count-only EU (EUIPO) and UK (UK IPO) trademark screens, 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
check_namesScreen 2-8 candidate names in ONE call and get them ranked by viability (best first).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 and UK trademark screens, 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
start_naming_sessionRequires a connected plan (API key).Reads text others writeNo findings
Why it is in this group
- The name "start_naming_session" says "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: true
Only reads 1Show 1 read-only tool
get_naming_sessionRequires a connected plan (API key).Reads text others writeNo findings
Why it is in this group
- The name "get_naming_session" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://nombrio.com/.well-known/oauth-protected-resource
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://nombrio.com/api/mcp: tools/list returned 4 tools to an anonymous client, including check_name (write), check_names (write), start_naming_session (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_name
The server marks "check_name" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:check_nameChanges thingsdescription
- Changed:check_namesChanges thingsdescription
Install
Pinned to version 1.2.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http name-check https://nombrio.com/api/mcpclaude mcp add --transport http name-check https://nombrio.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__name-check__get_naming_session"
],
"ask": [
"mcp__name-check__check_name",
"mcp__name-check__check_names",
"mcp__name-check__start_naming_session"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as name-check. Review it before you use it.
Capability tags behind 4 rules
- mcp__name-check__check_name untrusted-input
- mcp__name-check__check_names untrusted-input
- mcp__name-check__start_naming_session untrusted-input
- mcp__name-check__get_naming_session untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.nombrio/name-check/verify?hash=49d6a2b7c0e3fda3f313c15e6709e0c09bc70bb8027166b1ea709e50fae3cf09" | jq -e '.changed == false'Pinned hash 49d6a2b7c0e3, from Nov 13, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.nombrio/name-check/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.nombrio/name-check)Source: MCP Registry. Synced Nov 13, 2026, 22:17 UTC.
Nombrio Clearance Check MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Nombrio Clearance Check MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Nombrio Clearance Check MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Nombrio Clearance Check MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Nombrio Clearance Check MCP server have?
- 4 tools: 3 write, 1 read. check_name, check_names, start_naming_session and get_naming_session.
Does the Nombrio Clearance Check MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Nombrio Clearance Check MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Nombrio Clearance Check MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.