Domainposture is a remote MCP server that gives an AI agent 22 tools, among them dns_lookup, dossier_ai_crawlers, dossier_cors. It answers at https://www.domainposture.com/mcp/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 18 October 2026, succeeded.
Remote MCP server: 19 domain-hygiene and email-auth tools (DNS, SPF, DMARC, DKIM, TLS).
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
dns_lookup | Context lookup: Resolve a single DNS record type (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA, or SRV) and return the raw answers. Use for quick, targeted lookups of one record type; prefer dossier_dns for a full multi-type DNS audit in parallel, Inputs: name, type |
dossier_ai_crawlers | Core dossier check: Report a domain's AI-crawler policy — whether robots.txt allows, blocks, or is silent on the six major AI agents (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, meta-externalagent). Use to answer "does this si Inputs: domain |
dossier_cors | Core dossier check: Send a CORS preflight OPTIONS request to https://<domain>/ and return the access-control-* response headers. Use to verify CORS policy for a specific origin-method pair, or to check whether a domain allows cross-origin r Inputs: domain, origin, method |
dossier_ct_log | Core dossier check: Discover subdomains visible in Certificate Transparency logs. Use for attack-surface mapping; prefer dossier_full when running a complete audit. Queries crt.sh first, falls back to certspotter; capped at 100 unique subdo Inputs: domain |
dossier_dkim | Core dossier check: Probe a domain's DKIM public keys by querying <selector>._domainkey.<domain> for each selector. Use to verify signing configuration or discover active selectors; supply selectors when you know the ESP's selector, or omit Inputs: domain, selectors |
dossier_dmarc | Core dossier check: Retrieve and parse a domain's DMARC policy from its _dmarc.<domain> TXT record, returning all tags. Use to audit email authentication policy, verify the p (policy) and rua (reporting) settings, or confirm alignment mode; Inputs: domain |
dossier_dns | Core dossier check: Fetch a domain's full DNS profile — A, AAAA, NS, SOA, CAA, and TXT records — all in parallel. Use as the first step of a domain audit or when you need a comprehensive DNS snapshot in one call; prefer dns_lookup for a sin Inputs: domain |
dossier_dnssec | Core dossier check: Verify DNSSEC chain-of-trust for a domain (DS, DNSKEY, AD flag). Use to confirm the zone is signed and resolvers accept the chain; prefer dossier_dns for raw record types or dossier_full for the complete audit. Fires Clo Inputs: domain |
dossier_full | Aggregate dossier check: Run all 10 Domain Dossier checks — dns, mx, spf, dmarc, dkim, tls, redirects, headers, cors, web-surface — in parallel and return all results in a single response. Use when you need a comprehensive domain health sna Inputs: domain |
dossier_headers | Core dossier check: Fetch https://<domain>/ and return all HTTP response headers, with an audit highlighting missing or misconfigured security headers. Use to review CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and P Inputs: domain |
dossier_llms_txt | Core dossier check: Detect whether a domain publishes an llms.txt at its root — the emerging convention that gives AI agents a curated markdown index of a site's content. Use in a content-posture audit to confirm a site guides (rather than Inputs: domain |
dossier_mta_sts | Core dossier check: Fetch and validate a domain's MTA-STS policy (mode, mx, max_age, policy id). Use to confirm inbound SMTP is locked to TLS for this domain. Resolves the _mta-sts TXT record, then fetches the policy from mta-sts.<domain>/. Inputs: domain |
dossier_mx | Core dossier check: Look up a domain's MX (mail exchanger) records and return them sorted ascending by priority. Use when verifying inbound-mail routing or as a precursor to SPF or DMARC checks; prefer dns_lookup with type=MX if you only ne Inputs: domain |
dossier_redirects | Core dossier check: Trace the full HTTP redirect chain starting from https://<domain>/, recording each hop's status code and destination URL. Use to debug redirect loops, verify HTTP→HTTPS upgrades, or audit link shorteners; stops at 10 hop Inputs: domain |
dossier_security_txt | Core dossier check: Verify a domain publishes a security.txt (RFC 9116) at /.well-known/security.txt — the standard machine-readable channel for reporting vulnerabilities. Use in a security audit to confirm researchers have a published disc Inputs: domain |
dossier_spf | Core dossier check: Retrieve and parse a domain's SPF record, decomposing it into mechanisms and qualifiers. Use to verify email sender policy, debug delivery failures, or check the 10-lookup limit; pair with dossier_dmarc for full email-au Inputs: domain |
dossier_tls | Core dossier check: Fetch and inspect the TLS certificate presented by a domain on port 443, returning chain details and validity period. Use to verify certificate expiry, issuer, Subject Alternative Names, or detect mismatched or self-sign Inputs: domain |
dossier_tlsrpt | Core dossier check: Look up a domain's TLS-RPT (SMTP TLS Reporting) policy. Use to confirm the domain receives reports of SMTP-TLS failures. Resolves _smtp._tls.<domain> TXT via Cloudflare DoH; 5s timeout. Returns a CheckResult; not_applica Inputs: domain |
dossier_web_surface | Core dossier check: Snapshot a domain's public web surface: robots.txt, sitemap.xml, and the home-page <head> metadata (title, description, OpenGraph, Twitter cards). Use for SEO audits, content discovery, or verifying metadata before shari Inputs: domain |
dossier_whois | Core dossier check: Look up the registrar, creation date, expiry date, and registry statuses for a domain. Use for ownership/expiry audit. Queries WHOIS over TCP/43 via the `whoiser` library; 15s timeout. Returns a CheckResult; not_applicab Inputs: domain |
ip_lookup | Context lookup: Resolve an IPv4 or IPv6 address to its geolocation, ASN, org name, and city/country. Use when you need network or location context for a raw IP address; prefer dns_lookup or dossier_dns for hostname resolution. Queries ipinf Inputs: ip |
user_agent_parse | Context lookup: Parse a User-Agent header string into structured browser, OS, device type, and rendering-engine components. Use to identify client capabilities from a raw UA string, e.g. when analysing server logs or request headers; does n Inputs: ua |
Every block below points at https://www.domainposture.com/mcp/mcp. Pick your client and copy.
claude mcp add --transport http domainposture https://www.domainposture.com/mcp/mcp
{
"mcpServers": {
"domainposture": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://www.domainposture.com/mcp/mcp"]
}
}
}{
"mcpServers": {
"domainposture": {
"url": "https://www.domainposture.com/mcp/mcp"
}
}
}{
"servers": {
"domainposture": {
"type": "http",
"url": "https://www.domainposture.com/mcp/mcp"
}
}
}{
"context_servers": {
"domainposture": {
"url": "https://www.domainposture.com/mcp/mcp"
}
}
}{
"mcpServers": {
"domainposture": {
"serverUrl": "https://www.domainposture.com/mcp/mcp"
}
}
}{
"mcpServers": {
"domainposture": {
"url": "https://www.domainposture.com/mcp/mcp"
}
}
}name: Domainposture
version: 0.0.1
schema: v1
mcpServers:
- name: Domainposture
type: streamable-http
url: https://www.domainposture.com/mcp/mcp{
"mcpServers": {
"domainposture": {
"httpUrl": "https://www.domainposture.com/mcp/mcp"
}
}
}{
"mcpServers": {
"domainposture": {
"type": "http",
"url": "https://www.domainposture.com/mcp/mcp"
}
}
}{
"mcpServers": {
"domainposture": {
"url": "https://www.domainposture.com/mcp/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwww.domainposture.com%2Fmcp%2Fmcp&type=streamable_http&id=domainposture&name=Domainposture
It answered our last check on 18 October 2026 in 904 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by domainposture.com and served from www.domainposture.com, the vendor's own domain: https://www.domainposture.com/mcp/mcp.
22, as returned by the server's own tools/list on 10 September 2026: dns_lookup, dossier_ai_crawlers, dossier_cors, dossier_ct_log, dossier_dkim, dossier_dmarc, dossier_dns, dossier_dnssec, and 14 more.
It answered our last check on 18 October 2026 in 904 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.domainposture.com/mcp/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.domainposture. Endpoint host: www.domainposture.com. ARD identifier: urn:air:com.domainposture:mcp:mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.