MCP server list / NameSniper
Check domain and social handle availability, and monitor taken handles to grab them when they drop.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 1,809.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 1,910 ms.
- Address
- https://namesniper.pro/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- pro.namesniper/
namesniper - Transport
- streamable HTTP
streamable-http - Host
namesniper.pro
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- namesniper
- Version:
- 1.1.1
- MCP features it lists:
- tools, resources
- Tool names:
namesniper_checknamesniper_check_domainsnamesniper_check_socialnamesniper_generatenamesniper_trademarknamesniper_alternativesnamesniper_watchnamesniper_watchesnamesniper_unwatchnamesniper_telegram_pricenamesniper_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 na…
Reported Aug 17, 2026, 05:06 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 1,709 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 1,932 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 971 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 1,910 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.