Developer · Local MCP server
Domain Security
Audit a domain's email and web security: SPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS, WHOIS. No API keys.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.OrtaMarco/domain-security-mcp-server- Version
- 1.2.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-14
- Updated
- 2026-09-14
- Publisher
- OrtaMarco (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/OrtaMarco) · how
- Listed under
- Email MCP servers
- Repository
- github.com/OrtaMarco/domain-security-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | domain-security-mcp-server | 1.2.1 | stdio |
How to connect Domain Security
Domain Security runs locally from a Node.js package published to the npm registry: domain-security-mcp-server version 1.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y domain-security-mcp-server@1.2.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"domain-security-mcp-server": {
"command": "npx",
"args": [
"-y",
"domain-security-mcp-server@1.2.1"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from OrtaMarco (GitHub)
| Server | Runs |
|---|---|
| Mexican Tax & BankingValidate RFC, CURP, CLABE and NSS, read CFDI 4.0 invoices and check their SAT status. No keys. | Local · stdio |
| SEO & GEOAudit a page's SEO and its readiness for AI answer engines: meta, schema, robots, sitemaps, AI bots. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Domain IntelligenceDomain overviews for security and sales: registration, infrastructure, and risk signals. | Remote · HTTPLive check: ✓ handshake |
| Domain Intelligence APIWHOIS, DNS records, SSL certificate data for any domain in one call. x402. | Remote · SSELive check: ✗ no handshake |
| Domain Intelligence MCP ServerWHOIS, DNS, SSL, IP geo for security forensics and OSINT - separate from SEO. | Remote · HTTPLive check: sign-in required |
| Domain LivenessIs this business's website still there? Checks apex and www, and DNS separately from HTTP. | Remote · HTTPLive check: ✓ handshake |
| DomainDNATech stack, email security (SPF, DMARC, MX provider) and domain age API + MCP. 25 free domains/day. | Remote · HTTPLive check: ✓ handshake |
| DomainDNA: Tech Stack Detector, WHOIS & Domain Age APIDomainDNA: a domain's tech stack, email security (MX/SPF/DMARC), TLS expiry and age in one record. | Remote · HTTPLive check: sign-in required |
| DomainDNA: Tech Stack Detector, WHOIS & Domain Age APIDomainDNA: a domain's tech stack, email security (MX/SPF/DMARC), TLS expiry and age in one record. | Remote · HTTPLive check: sign-in required |
| DomaindriftSigned internet telemetry, read-only: DNS, TLS, WHOIS, reachability. Every record Ed25519-signed. | Remote · HTTPLive check: ✓ handshake |