A
license-
qualityC
maintenanceGenerates startup names with live .com availability checks and screens them against US and EU trademark registers.
Last updated
108
MIT
name-check
by com.nombrio
Server Details
Live brand-name availability checks: US trademark (USPTO), domains, social handles, app stores.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.6/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no ambiguity between tools.
Naming Consistency5/5
The single tool follows the verb_noun pattern with check_name, which is consistent.
Tool Count2/5
One tool attempts to cover trademark, domain, social, and developer namespace checks, which is too few for the broad scope.
Completeness4/5
The tool covers a wide range of availability checks, leaving only minor potential gaps like additional TLDs or platforms.
Available Tools
1 toolcheck_nameCheck name availabilityARead-onlyInspect
Check whether a brand, business, product, or app name is available. Runs a real-time availability check across: the US trademark registry (USPTO — live registry data, not guesses), domain names (.com, .io, .co, .app, .dev, with registration prices), social handles (X/Twitter, Instagram, TikTok, LinkedIn), developer namespaces (npm, PyPI, crates.io, GitHub, Docker Hub), and the iOS App Store. Returns a structured verdict (clear / caution / conflict), an overall viability band, and a link to the full interactive result. Use this whenever a user is brainstorming, choosing, or validating a name for a startup, company, product, app, or project and wants to know if it is taken, trademarked, or safe to use. Call once per candidate name. Free, no API key (shared daily fair-use pool). 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. One name per call. |
Tool Definition Quality
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint and openWorldHint; description reinforces these by stating it's a real-time check on live registry data. It discloses free usage, fair-use pool, no API key, and the structured return (verdict, viability band, link). No contradictions with 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 description is a single paragraph with multiple sentences, each adding essential detail. It front-loads the main purpose and follows with scope, output, usage, and attribution. Slightly verbose but efficiently covers all key points.
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?
Despite no output schema, the description explains return type (verdict, viability band, link). It covers all context needed for a simple tool: when to use, what it checks, limitations, and attributes. No gaps given the low complexity (1 param, no nested objects).
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% for the one parameter 'name', which already describes constraints (plain name, no URL/TLD/handle, example). The tool description adds the same example and reiterates limitations, offering marginal added value 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 clearly states the verb 'check' and resource 'name availability' with explicit scope (brand, business, product, app name). It lists all registries checked (USPTO, domains, social handles, dev namespaces, iOS App Store). No sibling tools exist, so differentiation is not needed.
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?
The description provides explicit guidance: 'Use this whenever a user is brainstorming, choosing, or validating a name... Call once per candidate name.' It also specifies constraints (plain name, no URL/handle) and gives context about the tool's role in the name validation process.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAquality-maintenanceStdio-based MCP server with 12 tools for brand name availability and safety checks. Returns structured JSON for domains (with pricing), social handles, USPTO/EUIPO trademarks, app stores, package registries, safety scoring, batch comparison, and filing readiness.Last updated1218
- Alicense-qualityDmaintenanceScore brand names across domain availability, USPTO trademark conflict, social handle availability (12+ platforms), SEO strength, and AI findability (GEO) in a single call. Pay-per-call via the x402 micropayment protocol (USDC on Base + Solana) — no signup, no API keys.Last updatedMIT
- Alicense-qualityCmaintenanceProvides evidence-first product naming tools for agents and founders, including domain registry checks, namespace searches, and finalist research with sources and timestamps.Last updatedMIT