domain-intel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVER_API_KEY | No | Optional API key to gate access to the server when self-hosting. Passed as 'Authorization: Bearer <key>'. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| domain_reportA | One-call full dossier on a domain: registration (RDAP), DNS records, email deliverability, and website tech stack, combined into a single report. Use for fast lead qualification, company research, or recon without four separate calls. |
| domain_intelA | Registration intelligence for a domain via RDAP (the modern WHOIS). Returns registrar, creation/expiration/last-changed dates, domain age in years, EPP status codes, nameservers, DNSSEC state, and abuse contact. Use to vet a company, assess a lead, or judge how established a domain is. |
| dns_lookupA | Look up DNS records for a domain via Cloudflare DNS-over-HTTPS. Returns A, AAAA, MX, NS, TXT, CNAME, and SOA records. Use to see where a domain is hosted, who runs its mail and DNS, and what verification/policy TXT records it publishes. |
| email_deliverabilityA | Assess whether a domain (or the domain of an email address) can receive mail and how strong its sender authentication is. Returns MX presence, SPF and DMARC policy, whether it's a free consumer provider (gmail, etc.) or a known disposable/temp-mail provider, and an overall verdict. Use to qualify leads and flag throwaway signups. |
| tech_stackA | Fingerprint the technology behind a website by fetching its homepage. Detects web server, CMS/framework (WordPress, Shopify, Next.js, etc.), CDN, analytics, and returns the page title, final URL after redirects, and key response headers. Use for competitive research and lead enrichment. |
| subdomainsA | Discover a domain's public subdomains (app., api., staging., and so on) from Certificate Transparency logs, querying crt.sh and Cert Spotter in parallel and returning whichever answers first. Useful for mapping a company's public attack surface or infrastructure. If both sources are down the call returns an error rather than an empty list. |
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 6 tools
Each tool has a clearly stated focus (registration, DNS, email, tech stack, subdomains, aggregate report). There is some output overlap: dns_lookup returns MX/TXT that email_deliverability interprets, and domain_report duplicates the outputs of the other tools. Descriptions make the boundaries clear enough, but misselection is still possible when a user just wants raw DNS.
All names are lowercase snake_case and resource-oriented, which is consistent and readable. However, the set mixes noun phrases (domain_intel, domain_report), noun_verb pairs (dns_lookup), and a bare plural (subdomains), with no single verb_noun pattern. Minor deviation from a perfect convention.
Six tools is well-scoped for a domain-intelligence server. Each tool covers a distinct investigative angle and the aggregate domain_report conveniently bundles them without bloating the surface.
The core lifecycle of domain intel is covered: registration, DNS, email authentication, technology fingerprinting, subdomain discovery, and a combined report. Minor gaps remain around IP/hosting resolution, TLS certificate inspection, and reputation/blacklist checks, but agents can work around these.