Domain & Company Intel MCP
Server Details
Domain intel for AI agents: RDAP registration, DNS, email deliverability, tech stack.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- datakoot/domain-intel-mcp
- GitHub Stars
- 0
- Server Listing
- domain-intel-mcp
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 5 of 5 tools scored.
Each tool targets a distinct aspect of domain intelligence: DNS records, registration details, email deliverability, subdomain discovery, and technology stack. There is no functional overlap, making it clear for an agent which tool to use for a given task.
All tool names follow a consistent lowercase snake_case pattern with a verb_noun structure (e.g., dns_lookup, domain_intel, email_deliverability). This predictability aids agent selection and understanding.
Five tools is an ideal number for a domain intelligence server—comprehensive enough to cover key areas (DNS, registration, email, subdomains, tech stack) without being overwhelming or sparse.
The tool set covers the essential lifecycle of domain investigation: registration (domain_intel), DNS resolution (dns_lookup), email authentication (email_deliverability), attack surface mapping (subdomains), and technology profiling (tech_stack). There are no obvious gaps for the stated purpose of lead enrichment and competitive research.
Available Tools
6 toolsdns_lookupInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| types | No | Optional subset of record types, e.g. ["MX","TXT"]. Defaults to all common types. | |
| domain | Yes | Domain name, e.g. stripe.com |
domain_intelInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. stripe.com (no scheme) |
domain_reportInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. stripe.com |
email_deliverabilityInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_or_email | Yes | A domain (stripe.com) or an email address (a@stripe.com) |
subdomainsInspect
Discover subdomains of a domain from public Certificate Transparency logs (crt.sh). Useful for mapping a company's public surface (app., api., staging., etc.). Best-effort: crt.sh can be slow; returns a note if unavailable.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Registrable domain, e.g. stripe.com |
tech_stackInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain or full URL, e.g. shopify.com |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- -license-qualityCmaintenanceDomain intelligence for DNS, WHOIS/RDAP, SSL/TLS, subdomain discovery, availability, valuation, email security, and typosquatting and brand protection.Last updated
- Alicense-qualityDmaintenanceEnables AI agents to perform real-time WHOIS and RDAP lookups, domain availability checks, and TLD infrastructure exploration using native protocols without API keys.Last updatedMIT
- Alicense-qualityBmaintenanceDomain -> company intelligence for AI agents. Look up company name, country, contacts, and social profiles from any MCP-compatible client.Last updated5MIT
- AlicenseAqualityAmaintenanceDomain security reconnaissance for AI agents — 13 tools (DNS+DNSSEC, SSL/TLS, HTTP security headers, SPF/DKIM/DMARC email auth, port scan, ASN, RDAP/WHOIS) plus a one-shot security_scan returning a 0–100 Health Score (A–F). Free, no API key.Last updated13461MIT
Your Connectors
Sign in to create a connector for this server.