namesniper_checkLABSCO SUMMARY
Anyone can tell you a handle is taken; this one tells you when it stops being taken.
A one-time yes or no is the wrong shape for a name someone else is sitting on. Putting it under watch and being alerted the instant it frees up is the only way to claim one, and the free checks make the first pass cost nothing.
What it is
A naming service for handles and domains. It checks one name everywhere at once, suggests variations, screens for trademark conflicts, and — the part ordinary checkers lack — keeps watching a handle that is already taken so you hear when it drops.
What you get
- One name checked across domains and social platforms together, with a brand score, and trademark screening folded in when you are authenticated
- Domain availability across popular TLDs, and username availability across YouTube, Reddit, TikTok, Instagram, X, GitHub, npm, Twitch, Threads, Bluesky, Pinterest, Snapchat, Kick, Substack, Linktree and Roblox
- Variations and creative patterns to fall back on when the name you wanted is gone
- Telegram username market history read off public TON blockchain records — peak and latest sale in TON, plus the live auction state
- Roblox username rarity from measured namespace data, with live availability beside it
- Brand names generated from a description, and USPTO trademark conflict screening
- A watch placed on a taken handle, the watch list read back, and a slot freed when you give up on one
- Two resources readable directly: the pricing and per-call costs, and the supported platforms and TLDs
Requirements
Nothing for the checks: the remote server at https://namesniper.pro/mcp speaks streamable HTTP, and checking and alternatives work with no account, rate limited. Stdio-only clients bridge to it through npm as namesniper-mcp. Generation, trademark screening and handle monitoring need a NameSniper key, passed as NAMESNIPER_API_KEY or a --key flag, on a Pro or Business plan; every plan carries some watch slots, and monitoring Instagram, TikTok and X requires a paid one.
Setup effort
Paste a URL — add the endpoint to your client
USE CASES
01
Testing a brand name before you commit to it
Run the name across domains and social at once, read the brand score, and screen it for trademark conflicts before anything is printed.
02
Finding a name that is actually free
When the first choice is gone, pull variations and check the shortlist across TLDs and platforms in one pass.
03
Waiting out a handle someone is squatting
Put it under watch, review what you are already watching, and release a slot when a name stops mattering.
04
Valuing a username before you chase it
Read the Telegram sale history and live auction state from public chain records, or the measured rarity of a Roblox name.
05
Starting from a description rather than a word
Generate candidates from what the product does, then check the ones that read well.
11 tools
Listed in project docs. Your client may show a different list.
namesniper_check_domainsnamesniper_check_socialnamesniper_alternativesnamesniper_telegram_pricenamesniper_roblox_raritynamesniper_generatenamesniper_trademarknamesniper_watchnamesniper_watchesnamesniper_unwatchBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
npx on PATH
Optional
NAMESNIPER_API_KEY in your environment
Where it runs
Of the 3 documented clients, 2 run the server on your machine and 1 connects to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://namesniper.pro/mcpMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"namesniper": {
"command": "npx",
"args": [
"-y",
"namesniper-mcp"
],
"env": {
"NAMESNIPER_API_KEY": "<YOUR_NAMESNIPER_API_KEY>"
}
}
}
}<YOUR_NAMESNIPER_API_KEY> is your NameSniper API key from namesniper.pro/dashboard. No key? Delete the "env" line: checking and alternatives are free and need no account, while name generation, trademark screening and handle watching need a key (Pro or Business plan).
Any MCP client — remote
ANY MCP CLIENT — REMOTE · JSON
{
"mcpServers": {
"namesniper": {
"url": "https://namesniper.pro/mcp"
}
}
}
