Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

com.nombrio/name-check

REMOTE · NOMBRIO.COM · SCANNED AUG 3

Live brand-name availability checks: US trademark (USPTO), domains, social handles, app stores.

Available components

+4 this week 68 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 284 tokens (~284/item across 1 items; 1 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · nombrio.com

# add to Claude Code
claude mcp add --transport http com-nombrio-name-check https://nombrio.com/api/mcp
# ~/.codex/config.toml
[mcp_servers.com-nombrio-name-check]
url = "https://nombrio.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-nombrio-name-check": {
      "type": "remote",
      "url": "https://nombrio.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-nombrio-name-check --url https://nombrio.com/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-nombrio-name-check:
    url: "https://nombrio.com/api/mcp"
// mcp.json
{
  "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.

Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 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
  • 30 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 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
  • 26 Jul 26 63

    First indexed and scored.

Diagnostics

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 3 Aug 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=YR1,O=Let's Encrypt,C=US 5 Jun 2026 3 Sept 2026 RSA 2048 SHA256-RSA 5bbffe4a887ff13d06fdd57f9eb088ec5b9
SANs: *.nombrio.com, nombrio.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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
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=*
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
MCP tools — 1 exposed · ~238 tokens

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.

Tool Tokens
check_name ~238

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.

NameTypeReqDescription
namestringyesThe candidate name to check, e.g. 'Lumeo'. Plain name only — no URL, no TLD, no @handle. One name per call.

No output schema declared.

No examples provided.