About naymme
What naymme is, who maintains it, and how the availability engine works under the hood.
naymme is a name-availability checker built for the moment every project starts with: you have a candidate name, and you need to know whether you can actually have it — as a domain, a package, a repository, a handle — before you fall in love with it.
One input fans out to 61 providers across domain TLDs, developer platforms, package registries, hosted subdomains, app stores, publishing platforms and social networks, then distills the sweep into a per-provider grid plus a deterministic brand-quality score. The point is not just 'is it free' but 'is it free where it matters, and is it any good'.
One codebase, four surfaces
Everything runs from a single strict TypeScript codebase:
- This web app — the Next.js UI you are reading, plus the JSON API under /api.
- A hosted MCP server at /api/mcp (Streamable HTTP, stateless) so AI assistants can call the checks as tools.
- An npm package — the naymme bin is a stdio MCP server for fully local use.
- A Cloudflare Worker edge deployment exposing the same tools over web-standard fetch APIs.
How the checks work
Each provider is a small adapter behind one contract: validate the name against that platform's rules before touching the network, return a uniform outcome, honor cancellation, and only claim 'available' on a verified unclaimed marker. Domains resolve through the RDAP → WHOIS → DNS nameserver fallback chain; registries and platforms check their canonical endpoints. Providers run concurrently with a 5-second timeout each, and a failure degrades to 'unknown' rather than failing the whole sweep.
The brand score is fully deterministic — punchiness, pronounceability, uniqueness and cleanliness — so the same name always earns the same grade.
Maintainer
naymme is maintained by @nandodani as an independent open-source project (MIT). It is not affiliated with, endorsed by, or associated with any of the brands, platforms or registries it checks.