NameSniper
REMOTE · NAMESNIPER.PRO · 2 COMPONENTS · SCANNED SEP 20
Monitor taken usernames and get alerted when they drop, plus handle, domain, and trademark checks.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1984 tokens (~152/item across 13 items; 11 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the NameSniper MCP server?
NameSniper is a hosted endpoint at https://namesniper.pro/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · namesniper.pro
claude mcp add --transport http pro-namesniper-namesniper 'https://namesniper.pro/mcp'
{
"mcpServers": {
"pro-namesniper-namesniper": {
"url": "https://namesniper.pro/mcp"
}
}
} {
"servers": {
"pro-namesniper-namesniper": {
"type": "http",
"url": "https://namesniper.pro/mcp"
}
}
} [mcp_servers.pro-namesniper-namesniper] url = "https://namesniper.pro/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pro-namesniper-namesniper": {
"type": "remote",
"url": "https://namesniper.pro/mcp",
"enabled": true
}
}
} openclaw mcp add pro-namesniper-namesniper --url 'https://namesniper.pro/mcp' --transport streamable-http
mcp_servers:
pro-namesniper-namesniper:
url: "https://namesniper.pro/mcp" {
"McpServers": {
"pro-namesniper-namesniper": {
"Transport": "http",
"Url": "https://namesniper.pro/mcp"
}
}
} assistant mcp add pro-namesniper-namesniper -t streamable-http -u 'https://namesniper.pro/mcp'
{
"mcpServers": {
"pro-namesniper-namesniper": {
"type": "http",
"url": "https://namesniper.pro/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +1
- Stability: fail → pass ▲ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 88 to 91.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 81 to 84.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 71 to 74.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 64 to 68.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 58 to 61.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 51 to 54.
- 31 Aug 26 −7
- Stability: pass → fail ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://namesniper.pro/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=namesniper.pro | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | eae14bd7b888e0fc0e8f8851b313e1be |
| SANs: namesniper.pro, *.namesniper.pro | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of namesniper.pro. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 42154 | 8 | Verified |
| namesniper.pro. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://namesniper.pro/mcp | Verified | 200 | |
| http (plaintext) | http://namesniper.pro/mcp | HTTPS enforced | 301 | https://namesniper.pro/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
namesniper_alternatives ~123
Generate variations of an existing brand name using deterministic prefix, suffix, compound, and wordplay patterns. Returns JSON alternatives[] each with the name, the pattern used, a description, and a 0-100 brandability score. Use this to riff on a name the user already has; use namesniper_generate for brand-new AI ideas from a description. Free, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of alternatives to generate (1-20, default: 8) |
| name | string | yes | The base brand name |
No output schema declared.
No examples provided.
namesniper_check ~301
All-in-one brand name check: domain availability across TLDs, username availability across the major social platforms, an optional 0-100 brand score, and USPTO trademark screening. Returns JSON with per-TLD and per-platform results (each with an availability verdict and 0-1 confidence), availability summaries, brandScore, and trademark risk. Use namesniper_check_domains or namesniper_check_social instead when only one dimension is needed. Free without an API key (rate-limited; trademark is skipped and Instagram/TikTok/X return best-effort HTTP confidence); a paid key unlocks verified accuracy on those platforms plus trademark screening.
| Name | Type | Req | Description |
|---|---|---|---|
| brandScore | boolean | – | Include brand score analysis (default: true) |
| domains | array | – | TLDs to check (default: com,org,net,app,dev,tech,io,co,ai) |
| name | string | yes | The brand name to check |
| plan | string | – | Ignored - derived from your API key |
| platforms | array | – | Social platforms to check (default: the standard platform grid; excludes Telegram, pass platforms explicitly including telegram to check it) |
| trademark | boolean | – | Include trademark screening via USPTO — requires an API key and counts against the plan's monthly screening allowance; ignored for unauthenticated callers (default: true when authenticated) |
| userId | string | – | Ignored - derived from your API key |
No output schema declared.
No examples provided.
namesniper_check_domains ~203
Check whether a domain name is registered across multiple TLDs using DNS lookups with a registry-data fallback. Returns JSON with per-TLD results (available true/false with a 0-1 confidence score) and an available/taken summary. Pass details=true to add a registration record on each taken TLD (registrar, registeredAt, expiresAt, status, dropStage) read from the registry; registrant identity is usually redacted. Faster and narrower than namesniper_check when social handles are not needed. Free, rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| details | boolean | – | Attach registry registration details (registrar, dates, status, drop stage) to taken TLDs (default: false) |
| name | string | yes | The domain name to check (without TLD) |
| tlds | array | – | TLDs to check (default: com,org,net,app,dev,tech,io,co,ai) |
No output schema declared.
No examples provided.
namesniper_check_social ~183
Check username availability across the major social platforms concurrently. Returns JSON with per-platform results (status available/taken/error with a 0-1 confidence score) and an available/taken summary. Narrower than namesniper_check when domains are not needed; if a wanted handle is taken, offer namesniper_watch. Free and rate-limited without an API key (Instagram, TikTok, and X/Twitter return best-effort HTTP confidence); a paid key unlocks verified accuracy on those three.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The username to check |
| plan | string | – | Ignored - derived from your API key |
| platforms | array | – | Platforms to check (default: the standard platform grid; excludes Telegram, pass platforms explicitly including telegram to check it) |
| userId | string | – | Ignored - derived from your API key |
No output schema declared.
No examples provided.
namesniper_generate ~209
Generate new brand name ideas with AI from a business or project description, each enriched with a live .com availability check. Non-deterministic: repeated calls produce different names (identical requests are served from a 24-hour cache and flagged with cached: true). Typical latency 5-30 seconds. Returns JSON names[] with the name, an explanation, tags, a confidence score, and comAvailable. Requires an API key (paid plan) and counts against a daily generation quota. To riff on a name the user already has, use namesniper_alternatives instead (free, deterministic).
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of names to generate (default: 25, max 30) |
| description | string | yes | Business or project description to generate names for |
| style | string | – | Style: modern, classic, tech, creative, professional, playful, abstract, luxury, minimalist |
| userId | string | – | Ignored - derived from your API key |
No output schema declared.
No examples provided.
namesniper_roblox_rarity ~66
Rate the rarity of a Roblox username (Common to Legendary, 0-100 score) from measured namespace saturation data and name structure, with a live availability check. Free, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | The Roblox username to rate |
No output schema declared.
No examples provided.
namesniper_telegram_price ~71
Look up the recorded market price history of a Telegram username: peak and latest on-chain sale (in TON), live auction state, and bid activity, from public TON blockchain records. Free, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | The Telegram username to look up (without @) |
No output schema declared.
No examples provided.
namesniper_trademark ~141
Screen a brand name for US trademark conflicts against the USPTO database with similarity analysis. Returns JSON with matching marks and a summary including an overall risk rating; with includeVariations, common spelling variations are screened too (slower, more lookups). A screening aid, not legal advice. Requires an API key (paid plan); each distinct name counts against the plan's monthly screening allowance (re-screening a name is free).
| Name | Type | Req | Description |
|---|---|---|---|
| includeVariations | boolean | – | Check common variations (default: false) |
| name | string | yes | The brand name to screen |
| userId | string | – | Ignored - derived from your API key |
No output schema declared.
No examples provided.
namesniper_unwatch ~127
Stop monitoring a watched handle and free its slot. Pass the watch id from namesniper_watches, or a username (optionally narrowed to one platform) to remove all its watches. Returns JSON with the removed count and ids. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Watch id from namesniper_watches |
| platform | string | – | Limit username-based removal to one platform |
| userId | string | – | Ignored - derived from your API key |
| username | string | – | Remove watches for this username across all platforms unless platform is given |
No output schema declared.
No examples provided.
namesniper_watch ~171
Start monitoring a taken username so the user can claim it when it frees up or drops (alerts follow the plan's check schedule after two confirming checks). Creates one watch per platform against the plan's slot limit (already-watched pairs are skipped); checks then run automatically on a plan-based schedule and alerts are delivered in-app, by email, and to any configured webhooks. Returns JSON with created watch ids and the skipped count. List watches with namesniper_watches; stop one with namesniper_unwatch. Requires a paid API key (Pro or Business).
| Name | Type | Req | Description |
|---|---|---|---|
| platforms | array | – | Platforms to watch - required; each consumes one watch slot |
| userId | string | – | Ignored - derived from your API key |
| username | string | yes | The username/handle to watch |
No output schema declared.
No examples provided.
namesniper_watches ~94
List every handle the account is monitoring. Returns JSON watches[] with id, username, platform, watch status, last observed availability, last-checked and last-changed timestamps, and check count, plus slot usage {used, limit}. Use a watch id with namesniper_unwatch to stop monitoring it. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | – | Ignored - derived from your API key |
No output schema declared.
No examples provided.
What is the NameSniper MCP server?
NameSniper is an MCP server listed in the public MCP registry as pro.namesniper/namesniper. Monitor taken usernames and get alerted when they drop, plus handle, domain, and trademark checks. This page covers its hosted endpoint (https://namesniper.pro/mcp).
Is the NameSniper MCP server safe to use?
NameSniper scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the NameSniper MCP server expose?
NameSniper exposes 11 tools: namesniper_check, namesniper_check_domains, namesniper_check_social, namesniper_generate, namesniper_trademark, and 6 more. Their descriptions and schemas cost roughly 1,689 tokens of context every time the server is loaded.
Does the NameSniper MCP server require authentication?
No. We connected to NameSniper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NameSniper MCP server still maintained?
NameSniper is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.