dns-intel
Enables domain intelligence lookups including RDAP registration data, DNS records, and Certificate Transparency searches.
README
DNS Intel MCP Server
Domain intelligence MCP server providing RDAP lookups, DNS queries, and Certificate Transparency log searches.
Features
- RDAP Lookup: Query domain registration information (registrar, dates, nameservers, status)
- DNS Query: Perform DNS queries for A, AAAA, CNAME, TXT, MX, NS, and SOA records
- CT Search: Search Certificate Transparency logs for certificates issued for a domain
Installation
npm install
npm run build
Usage
As MCP Server (stdio)
# Start the server
npm start
# Or with custom configuration
DNS_RESOLVER=1.1.1.1 npm start
With Claude Desktop
Add to your Claude Desktop configuration (~/.config/claude/claude_desktop_config.json):
{
"mcpServers": {
"dns-intel": {
"command": "node",
"args": ["/path/to/dns-intel/dist/cli.js"]
}
}
}
With HTTP Health Checks
For containerized deployments, enable the HTTP health check server:
npm start -- --http
This exposes:
GET /health- Health check endpointGET /ready- Readiness probe
Tools
rdap_lookup
Query RDAP for domain registration information.
Input:
{
"domain": "example.com"
}
Output:
{
"ok": true,
"data": {
"domain": "example.com",
"registrar": "Example Registrar Inc.",
"creation_date": "1995-08-14T04:00:00Z",
"expiration_date": "2025-08-13T04:00:00Z",
"updated_date": "2024-08-14T07:01:34Z",
"status": ["clientDeleteProhibited", "clientTransferProhibited"],
"nameservers": ["a.iana-servers.net", "b.iana-servers.net"]
},
"meta": {
"source": "rdap-bootstrap.iana.org",
"retrieved_at": "2024-01-15T10:30:00Z"
}
}
dns_query
Perform DNS queries for various record types.
Input:
{
"name": "example.com",
"type": "MX",
"resolver": "8.8.8.8"
}
Output:
{
"ok": true,
"data": {
"name": "example.com",
"type": "MX",
"resolver": "8.8.8.8",
"records": [
{
"name": "example.com",
"type": "MX",
"ttl": 300,
"data": {
"priority": 10,
"exchange": "mail.example.com"
}
}
]
},
"meta": {
"source": "https://dns.google/resolve",
"retrieved_at": "2024-01-15T10:30:00Z"
}
}
Supported Record Types:
A- IPv4 addressAAAA- IPv6 addressCNAME- Canonical nameTXT- Text recordsMX- Mail exchangeNS- NameserverSOA- Start of authority
ct_search
Search Certificate Transparency logs for certificates.
Input:
{
"domain": "example.com",
"limit": 100,
"cursor": null
}
Output:
{
"ok": true,
"data": {
"domain": "example.com",
"certificates": [
{
"id": 12345678,
"issuer_ca_id": 16418,
"issuer_name": "C=US, O=Let's Encrypt, CN=R3",
"common_name": "*.example.com",
"name_value": "example.com\n*.example.com",
"not_before": "2024-01-01T00:00:00",
"not_after": "2024-04-01T00:00:00",
"serial_number": "abc123...",
"entry_timestamp": "2024-01-01T00:00:01"
}
],
"total_returned": 1
},
"meta": {
"source": "crt.sh",
"retrieved_at": "2024-01-15T10:30:00Z",
"pagination": {
"next_cursor": "eyJvZmZzZXQiOjEwMH0="
}
}
}
Configuration
Environment variables:
| Variable | Default | Description |
|---|---|---|
DNS_RESOLVER |
8.8.8.8 |
Default DNS resolver for queries |
REQUEST_TIMEOUT_MS |
10000 |
Request timeout in milliseconds |
HTTP_PORT |
3000 |
HTTP server port for health checks |
LOG_LEVEL |
info |
Log level (debug, info, warn, error) |
Response Format
All tools return a standard response envelope:
Success Response
{
"ok": true,
"data": { ... },
"meta": {
"source": "...",
"retrieved_at": "2024-01-15T10:30:00Z",
"pagination": { "next_cursor": null },
"warnings": []
}
}
Error Response
{
"ok": false,
"error": {
"code": "UPSTREAM_ERROR",
"message": "Human readable error message",
"details": { ... }
},
"meta": {
"retrieved_at": "2024-01-15T10:30:00Z"
}
}
Error Codes:
INVALID_INPUT- Invalid input parametersUPSTREAM_ERROR- Error from upstream serviceRATE_LIMITED- Rate limit exceededTIMEOUT- Request timed outPARSE_ERROR- Failed to parse responseINTERNAL_ERROR- Internal server error
Development
# Install dependencies
npm install
# Run in development mode
npm run dev
# Run tests
npm test
# Run tests with coverage
npm run test:coverage
# Type check
npm run typecheck
# Build
npm run build
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.