nameinsight
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI_MODEL | No | Claude model used for suggestions | claude-opus-5-5 |
| API_HOST | No | Address the server binds to. Set `0.0.0.0` to serve other machines (e.g. in a container) | 127.0.0.1 |
| API_PORT | No | Port the server listens on | 8080 |
| APP_NAME | No | API title shown in Swagger UI | NameInsight |
| AI_EFFORT | No | Effort level for suggestions (`low`, `medium`, `high`) | medium |
| DNS_SERVERS | No | Comma-separated DNS server IPs, e.g. `1.1.1.1,8.8.8.8`. Default is the system resolvers. Set this when the host's resolver also answers for internal zones | |
| CORS_ORIGINS | No | Comma-separated origins allowed to call the API from a browser, e.g. `https://app.example.com`. Empty means no cross-origin access | |
| LOG_REQUESTS | No | Set to `false` to turn off the per-request access log | true |
| ALLOWED_HOSTS | No | Comma-separated Host headers the server accepts (DNS-rebinding protection). Empty: localhost names only on a loopback bind, any host otherwise (with a startup warning). `MCP_ALLOWED_HOSTS` is an older alias | |
| DNS_TIMEOUT_MS | No | DNS query timeout | 5000 |
| MAX_BODY_BYTES | No | Maximum JSON / form body size | 16384 |
| RATE_LIMIT_MAX | No | Requests allowed per client IP per window on `/api/*` | 30 |
| RDAP_TIMEOUT_MS | No | Hard deadline per RDAP request | 5000 |
| MAX_UPLOAD_BYTES | No | Maximum uploaded file size | 65536 |
| TRUST_PROXY_HOPS | No | Number of reverse proxies in front of the service. Set this behind a load balancer so rate limiting uses the real client IP | 0 |
| WHOIS_TIMEOUT_MS | No | Hard deadline per WHOIS server (a lookup can follow up to 2 referrals) | 10000 |
| ANTHROPIC_API_KEY | No | Secret. Enables REST AI suggestions (and the MCP fallback). Set only in the environment; never commit | |
| LOOKUP_BUDGET_MAX | No | Domains each client IP may look up per window (a bulk request costs one per domain) | 200 |
| LOOKUP_CONCURRENCY | No | Domains looked up at the same time within one request | 5 |
| MAX_QUEUED_LOOKUPS | No | Lookups allowed to wait for a slot; beyond this, requests get `503` + `Retry-After` | 100 |
| SHUTDOWN_TIMEOUT_MS | No | On SIGTERM/SIGINT, how long in-flight requests may finish before connections are force-closed | 10000 |
| PING_TIMEOUT_SECONDS | No | Ping reply timeout | 2 |
| RATE_LIMIT_WINDOW_MS | No | Rate-limit window in milliseconds | 60000 |
| WEB_CHECK_TIMEOUT_MS | No | Hard deadline for the `insights` HTTPS check | 5000 |
| MAX_CONCURRENT_LOOKUPS | No | Domains looked up at the same time across all requests | 20 |
| SUGGEST_RATE_LIMIT_MAX | No | Suggestion requests per client IP per rate-limit window (REST and MCP combined) | 5 |
| LOOKUP_BUDGET_WINDOW_MS | No | Lookup-budget window in milliseconds | 60000 |
| MAX_CONCURRENT_AI_CALLS | No | Claude API calls in flight at once | 2 |
| MAX_DOMAINS_PER_REQUEST | No | Maximum domains in one bulk request | 50 |
| MAX_RDAP_RESPONSE_BYTES | No | Larger RDAP responses are discarded | 262144 |
| MAX_WHOIS_RESPONSE_BYTES | No | WHOIS responses longer than this are truncated | 131072 |
| GLOBAL_SUGGEST_MAX_PER_HOUR | No | Claude API suggestion calls per hour for the whole process (caps spend on the server key) | 100 |
| MAX_CONCURRENT_REQUESTS_PER_CLIENT | No | Requests one client IP may have in flight on `/api` and `/mcp` | 2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domainA | Checks one domain name: registration status (from the registry via RDAP or WHOIS), expiry, registrar, DNS and reachability. Set insights=true for nameservers, email setup (MX/SPF/DMARC) and an HTTPS/TLS check. |
| check_domainsA | Checks up to 50 domain names at once and returns one result per unique name, in order. |
| check_name_across_tldsA | Checks one name (without extension, e.g. "nameinsight") across several TLDs and lists which are available. Defaults to .com, .net, .org, .io, .ai, .dev, .app, .co. |
| suggest_domainsA | Brainstorms brandable names for a business or project, then checks each across TLDs and ranks them by real availability. Uses your own model through MCP sampling when supported, otherwise the server's Claude API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools have largely distinct purposes: single-domain check, bulk check, cross-TLD availability for one base name, and name suggestions. The singular/plural pair check_domain vs check_domains and the overlap between check_domains and check_name_across_tlds could cause brief hesitation, but descriptions clarify the boundaries.
All tools follow a consistent snake_case verb-first pattern: check_domain, check_domains, check_name_across_tlds, suggest_domains. The singular/plural distinction is predictable and readable.
Four tools is well-scoped for a domain/name insight server, with each tool covering a distinct workflow: single lookup, bulk lookup, TLD sweep, and brainstorming with availability.
The surface covers the main domain-checking lifecycle: individual checks, bulk checks, cross-TLD availability, and suggestions. Minor gaps exist, such as no bulk insights option or ongoing monitoring, but core workflows are covered.