Skip to content

Name.ai MCP Server

ai.name/nameai-mcpname.aistreamable-httpv1.0.1Scanned

Domain availability search, WHOIS lookup, TLD pricing and registry rules from name.ai. Read-only.

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Name.ai MCP Server can do

The Name.ai MCP Server is published by name.ai, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

4 tools bring in text other people can write (search_domain, whois_lookup, tld_registration_price and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Only reads 4Show 4 read-only tools
  • search_domainCheck whether a domain is available and, for the same label, whether its common alternate TLDs are too (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "search_domain" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check whether a domain is available and, for the same label, whether its common alternate TLDs are too (e.g. querying "acme.com" also returns "acme.ai", "acme.io", ...). Backed by POST /api/domain/search — public, no auth required. Buy-now (aftermarket/marketplace) prices are hidden unless you're authenticated (see AUTH.md at name.ai for how to get a token) — an unauthenticated call only sees new-registration pricing for a domain that's simply unregistered. Pass a valid OAuth access token as this call's Authorization header and it's forwarded automatically. Args: domain: A domain name to check, e.g. "example.ai". include_alternates: When true (default), also return sibling TLDs for the same label. When false, only the exact domain is returned.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • tld_registration_priceGet the current USD price for a domain-lifecycle operation on a TLD (new registration, transfer-in, renewal, or restore from redemption).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Get the current USD price for a domain-lifecycle operation on a TLD (new registration, transfer-in, renewal, or restore from redemption). Backed by GET /api/pricing/tld — public, no auth required. This is name.ai's own registration pricing, not an aftermarket/marketplace price, so it is never gated by sign-in status. Args: tld: The TLD without a leading dot, e.g. "ai" or "com". operation: One of "register", "transfer", "renew", "restore".

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • tld_requirementsGet registration requirements for a TLD: allowed registration period range, whether an organization is required, allowed registrant countries, nameserver rules, and similar registr…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Get registration requirements for a TLD: allowed registration period range, whether an organization is required, allowed registrant countries, nameserver rules, and similar registry policy. Backed by GET /api/tlds/{tld}/metadata — public, no auth required. Args: tld: The TLD without a leading dot, e.g. "ai" or "io".

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • whois_lookupLook up WHOIS/RDAP registration details for a domain: registrar, registrant, creation/expiration dates, nameservers.Reads text others writeNo findings

    Why it is in this group

    • The name "whois_lookup" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Look up WHOIS/RDAP registration details for a domain: registrar, registrant, creation/expiration dates, nameservers. Backed by POST /api/tools/whois — public, no auth required, but rate limited by name.ai to 10 lookups per day per caller IP. Since every MCP call shares this server's egress IP, that quota is pooled across all of this MCP server's callers, not per end user. Args: domain: A domain name to look up, e.g. "example.com".

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.name.ai/.well-known/oauth-protected-resource
Authorization servers
https://name.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http nameai https://mcp.name.ai/mcp
claude mcp add --transport http nameai https://mcp.name.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nameai__search_domain",
      "mcp__nameai__whois_lookup",
      "mcp__nameai__tld_registration_price",
      "mcp__nameai__tld_requirements"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nameai. Review it before you use it.

Capability tags behind 4 rules
  • mcp__nameai__search_domain untrusted-input
  • mcp__nameai__whois_lookup untrusted-input
  • mcp__nameai__tld_registration_price untrusted-input
  • mcp__nameai__tld_requirements untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.name/nameai-mcp/verify?hash=bc0741a3345995820f6db8a824ab7239e942d429eaf8b25c5c73269e16881793" | jq -e '.changed == false'

Pinned hash bc0741a33459, from Nov 10, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.name/nameai-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.name/nameai-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.name/nameai-mcp.svg)](https://radar.anlyon.com/servers/ai.name/nameai-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:42 UTC.

Name.ai MCP Server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Name.ai MCP Server safe?

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Name.ai MCP Server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Name.ai MCP Server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Name.ai MCP Server have?

4 tools: 4 read. search_domain, whois_lookup, tld_registration_price and tld_requirements.

Does the Name.ai MCP Server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Name.ai MCP Server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Name.ai MCP Server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.