Domainintel Mcp

io.github.Bishop81Published by GitHub account Bishop81v1.0.2Updated Oct 24, 2026

Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.

VerifiedSTDIODesktop onlyWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that gives an assistant live domain intelligence: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains and email header analysis.

What you can do
Look up WHOIS registration details, dates, registrant country and nameservers for a domain, and read DNS records with SPF/DMARC checks and misconfiguration warnings. Inspect SSL/TLS certificates for validity, issuer, expiry and protocol, and score HTTP security headers such as HSTS and CSP with recommendations. Check domain reputation against DNSBL and Spamhaus blocklists, and discover subdomains through Certificate Transparency logs and prefix probing. Run every analyzer at once for a full report with an overall A+ to F security score. Parse a pasted raw email header block for SPF/DKIM/DMARC results, the Received delivery path and a From-versus-Return-Path spoofing flag.
When to use it
Useful when checking a domain before trusting or contacting it, auditing a site's DNS, certificate and security header posture, investigating email deliverability or spoofing, or enumerating subdomains during reconnaissance.
Requirements
Runs locally over stdio as the npm package @domainintel/mcp, launched with npx; needs Node.js 18 or newer. No accounts, API keys or environment variables are declared. Network access is needed for the live lookups.
Before you install
Queries are sent to third-party services (WHOIS, DNS, Certificate Transparency, blocklists) for each domain analyzed, so the domains you check are disclosed to those parties. Email header blocks can contain addresses and routing details; avoid pasting sensitive headers. Tools are read-only lookups.

Installation

In SourceWeft

  1. Open Domainintel Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@domainintel/mcp

An MCP server that gives AI agents live domain intelligence: WHOIS, DNS, SSL/TLS, HTTP security headers, reputation, and subdomain discovery for any domain. It is the same analysis engine that powers DomainIntel.app.

Tools

ToolReturns
whois_lookupRegistrar, creation/expiry/updated dates, registrant country, privacy status, nameservers
dns_recordsA, AAAA, MX, TXT, NS, CNAME, CAA records + SPF/DMARC presence + misconfiguration warnings
ssl_certificateValidity, issuer, expiration, days remaining, protocol, warnings
security_headersHSTS, CSP, X-Frame-Options and others, scored with recommendations
domain_reputationDNSBL / Spamhaus blocklist checks and a reputation score
subdomain_discoverySubdomains via Certificate Transparency logs and common-prefix probing
full_domain_reportEvery analyzer at once plus an overall A+ to F security score
analyze_email_headersParses a raw email header block: SPF/DKIM/DMARC results, the Received delivery path with timing, key envelope fields, and a From-vs-Return-Path spoofing flag

Every tool except analyze_email_headers takes a single domain argument; protocol, www., and paths are stripped automatically. analyze_email_headers takes a headers string (a pasted raw header block) instead.

Requirements

  • Node.js 18 or newer

Install

Claude Code

bash
claude mcp add domainintel -- npx -y @domainintel/mcp

Claude Desktop

Add to claude_desktop_config.json (Settings → Developer → Edit Config):

json
{  "mcpServers": {    "domainintel": {      "command": "npx",      "args": ["-y", "@domainintel/mcp"]    }  }}

Any other MCP client

The server speaks MCP over stdio:

bash
npx -y @domainintel/mcp

Example prompts

  • "Run a full domain report on stripe.com"
  • "What are the MX records for github.com, and does it have DMARC?"
  • "Is the SSL certificate for example.org close to expiring?"

Development

Run from source (no build needed):

bash
git clone <repo> && cd domainintel.appnpm installnpm run mcp        # node mcp/server.mjs

Building & publishing

The published package is a single self-contained bundle (the analyzers and all JS dependencies are bundled with esbuild; Node built-ins resolve at runtime).

bash
npm run build:mcp          # from repo root -> mcp/dist/server.mjscd mcp && npm publish       # prepublishOnly rebuilds the bundle

License

MIT

Source: README.md at commit 6e396b5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts