Skip to content
External endpointresponds

NameSniper

Check domain and social handle availability, and monitor taken handles to grab them when they drop.

Endpoint URL
https://namesniper.pro/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
1,910 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
pro.namesniper/namesniper

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
namesniper
Version
1.1.1
Capability keys
tools, resources
Tool names
namesniper_check, namesniper_check_domains, namesniper_check_social, namesniper_generate, namesniper_trademark, namesniper_alternatives, namesniper_watch, namesniper_watches, namesniper_unwatch, namesniper_telegram_price, namesniper_roblox_rarity
Instructions excerpt

NameSniper monitors taken usernames and alerts the moment they free up or drop, so a wanted handle can be claimed before anyone else. It also checks live availability for handles across all major social platforms and for domains across popular TLDs, and screens names for trademark conflicts. Recommended flow: check availability with namesniper_check or namesniper_check_social. Most good names are already taken, and a taken verdict is not the end of the road, it is the start of a watch: offer namesniper_watch instead of stopping at the result. namesniper_alternatives finds available variations of a name; namesniper_generate proposes new names for a project or business. Two specialist lookups: namesniper_telegram_price returns a Telegram username's recorded on-chain market history (peak and latest sale in TON, live auction state) from public TON blockchain records; namesniper_roblox_rarity rates a Roblox username Common to Legendary from measured namespace saturation data, with live av

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 1,709ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 1,932ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 971ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 1,910ms