mcp

Name: mcp
Author: com.domainposture

MCP serverMCP

Remote MCP server: 19 domain-hygiene and email-auth tools (DNS, SPF, DMARC, DKIM, TLS).

by com.domainposturehomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"com-domainposture-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability108/109 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	733 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools
12 h ago	mcp initialize	ok	200	952 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools
19 h ago	mcp initialize	ok	200	1812 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools
26 h ago	mcp initialize	ok	200	770 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools
33 h ago	mcp initialize	ok	200	797 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools
2 d ago	mcp initialize	ok	200	831 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools
2 d ago	mcp initialize	ok	200	1011 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools
2 d ago	mcp initialize	ok	200	1954 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools
2 d ago	mcp initialize	ok	200	754 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools
3 d ago	mcp initialize	ok	200	767 ms	server domainposture.com 0.1.0 · protocol 2025-06-18 · 22 tools

Tools observed via MCP handshake

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
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
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 whe
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
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 f
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
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 disco
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 certific
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 redir
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 r
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
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 c
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
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 do
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. R
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
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 TC
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 au
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-
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'
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 vulne
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 r

mcp

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from