Other · Remote MCP server
NameSniper
Monitor taken usernames and get alerted when they drop, plus handle, domain, and trademark checks.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
pro.namesniper/namesniper- Version
- 1.1.2
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- pro.namesniper
- Namespace
- Namespace verified by the MCP Registry via the domain namesniper.pro · how
- Website
- namesniper.pro
- Repository
- github.com/NameSniperPro/NameSniper-MCP
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://namesniper.pro/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- namesniper 1.1.2 · protocol 2025-06-18
- Tools discovered
- 11:
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 - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | namesniper-mcp | 1.1.2 | stdio |
How to connect NameSniper
NameSniper is a remote MCP server: there is nothing to install. Its endpoint is https://namesniper.pro/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: namesniper-mcp version 1.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y namesniper-mcp@1.1.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"namesniper": {
"command": "npx",
"args": [
"-y",
"namesniper-mcp@1.1.2"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| NameIntelBrand-name intelligence across 5 dimensions including AI findability. Pay-per-call via x402. | Remote · HTTPLive check: ✓ handshake |
| NamemyappBrandable business names with live domain availability + one-click buy URLs. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| NameraCheck name availability across domains, trademarks, and social handles. Score and rank candidates. | Local · stdio |
| Namesake - baby name catalog and guidesRead-only access to Namesake's baby name catalog: meaning, origin, pronunciation, popularity trend. | Remote · HTTPLive check: ✓ handshake |
| NameWheelFair random picks with the wheel in your chat: pick names, split teams, run certified draws. | Remote · HTTPLive check: ✓ handshake |
| NamewhereCompany name to domain API + MCP: official website, confidence, evidence. $5 pack; 25 free/day. | Remote · HTTPLive check: ✓ handshake |
| Nandi Proxmox MCPMCP server for Proxmox VE management (VM, LXC, nodes) | Local · stdio |
| Nanmesh MCP12 tools that let AI agents check trust scores and reviews before recommending any software tool. | Local · stdio |