dns-intel
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@dns-intellookup RDAP registration for example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: Yunaq GAC MCP Server
Installation
npm install
npm run buildUsage
As MCP Server (stdio)
# Start the server
npm start
# Or with custom configuration
DNS_RESOLVER=1.1.1.1 npm startWith 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 -- --httpThis 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 |
|
| Default DNS resolver for queries |
|
| Request timeout in milliseconds |
|
| HTTP server port for health checks |
|
| 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 buildLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BUZDOLAPCI/dns-intel'
If you have feedback or need assistance with the MCP directory API, please join our Discord server