Is the Namesniper MCP server down?

mcp-registry/pro.namesniper/namesniper · v1.1.2

healthy
Last checked 2026-10-27 07:03 UTC · handshake 1.1s

As of 2026-10-27 07:03 UTC, the Namesniper MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 213 outages in 90 days, with a median recovery of 10 minutes.

uptime (30d checks)
100%
checks observed
5,003
outages (90d)
213
tools
11

Monitor taken usernames and get alerted when they drop, plus handle, domain, and trademark checks.

Point your MCP client at this streamable-http endpoint: https://namesniper.pro/mcp

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 2 warning(s) across 11 tool(s); ~2,648 tokens of tool definitions.
Scores higher than 42% of 15,776 MCP servers Glimind has audited.
Its tool list costs an agent ~2,648 tokens per session — more than 50% of servers.
84 → 84 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (3)

11 of 11 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: namesniper_alternatives, namesniper_check, namesniper_check_domains, namesniper_check_social, namesniper_generate and 6 more

Handshake + tools/list takes ~2,280 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fpro.namesniper%2Fnamesniper/fixes

namesniper_check 1 change
{
  "name": "namesniper_check",
  "description": "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 skipp",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "The brand name to check"
      },
      "plan": {
        "type": "string",
        "description": "Ignored - derived from your API key"
      },
      "userId": {
        "type": "string",
        "description": "Ignored - derived from your API key"
      },
      "domains": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "TLDs to check (default: com,org,net,app,dev,tech,io,co,ai)"
      },
      "platforms": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Social platforms to check (default: the standard platform grid; excludes Telegram, pass platforms explicitly including telegram to check it)"
      },
      "trademark": {
        "type": "boolean",
        "description": "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)"
      },
      "brandScore": {
        "type": "boolean",
        "description": "Include brand score analysis (default: true)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
namesniper_check_domains 1 change
{
  "name": "namesniper_check_domains",
  "description": "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, r",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "The domain name to check (without TLD)"
      },
      "tlds": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "TLDs to check (default: com,org,net,app,dev,tech,io,co,ai)"
      },
      "details": {
        "type": "boolean",
        "description": "Attach registry registration details (registrar, dates, status, drop stage) to taken TLDs (default: false)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
namesniper_check_social 1 change
{
  "name": "namesniper_check_social",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "The username to check"
      },
      "plan": {
        "type": "string",
        "description": "Ignored - derived from your API key"
      },
      "userId": {
        "type": "string",
        "description": "Ignored - derived from your API key"
      },
      "platforms": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Platforms to check (default: the standard platform grid; excludes Telegram, pass platforms explicitly including telegram to check it)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/pro.namesniper/namesniper"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/pro.namesniper/namesniper"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fpro.namesniper%2Fnamesniper.svg)](https://glimind.com/server/mcp-registry%2Fpro.namesniper%2Fnamesniper?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fpro.namesniper%2Fnamesniper?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fpro.namesniper%2Fnamesniper.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fpro.namesniper%2Fnamesniper.svg
   :target: https://glimind.com/server/mcp-registry%2Fpro.namesniper%2Fnamesniper?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6df9f3c78c8432cf…, first seen 2026-10-17, included at leaf 5488 of 77,980. Version history · verify what your client received.

Tools (11)

Compare: most reliable other servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Namesniper MCP server down right now?

As of 2026-10-27 07:03 UTC, the Namesniper MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 213 outages in 90 days, with a median recovery of 10 minutes.

How many tools does Namesniper MCP server provide?

Namesniper MCP server advertises 11 tools, including namesniper_alternatives, namesniper_check, namesniper_check_domains, namesniper_check_social, namesniper_generate.

How do I install Namesniper MCP server?

Point your MCP client at this streamable-http endpoint: https://namesniper.pro/mcp

Is the Namesniper MCP server safe to connect to an AI agent?

Glimind scanned all 11 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Namesniper MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve