drwho.me: free DNS, email, TLS and developer tools, and a free MCP server for AI
drwho.me: free DNS, email, TLS and developer tools, and a free MCP server for AI agents
active Production-safe Score 89/100 http no auth
At a glance
| Endpoint | https://drwho.me/mcp/mcp |
|---|---|
| Source | https://github.com/hikmahtech/drwhome |
| Transport | http |
| Tools | 29 |
| Auth | none |
| First seen | 2026-09-30 02:08:58 |
| Last checked | 2026-11-17 21:57:16 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 909 / 1502 ms |
| Last successful check | 2026-11-17 21:57:16 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (29)
dossier_summary— Run the nine DNS, email-authentication and TLS checks on a domain in parallel and return one graded line per check: DNS records, MX, SPF, DMdossier_dns— Fetch a domain's A, AAAA, NS, SOA, CAA and TXT records in one call. Use as the first step of a DNS review; prefer dns_lookup for a single redossier_mx— List a domain's MX (mail exchanger) records sorted by priority. Use to see where a domain's inbound mail goes, or before checking SPF and DMdossier_spf— Find and parse a domain's SPF record into its mechanisms. Use to check which servers may send mail for a domain, or to debug delivery failurdossier_dmarc— Find and parse the DMARC policy at _dmarc.<domain> into its tags (p, sp, pct, rua, ruf, adkim, aspf). Use to see whether spoofed mail is rejdossier_dkim— Probe a domain for DKIM public keys at <selector>._domainkey.<domain>. Pass selectors when you know them; omit to probe a built-in list of cdossier_dnssec— Check whether a domain's zone is signed with DNSSEC and validates: DS and DNSKEY records plus the resolver's AD (authenticated data) flag. Qdossier_tlsrpt— Look up a domain's SMTP TLS Reporting policy at _smtp._tls.<domain>. Use to confirm the domain receives reports about failed TLS delivery ofdossier_mta_sts— Fetch and validate a domain's MTA-STS policy (mode, mx, max_age). Use to confirm inbound mail to the domain must be delivered over TLS. Resodossier_tls— Read the TLS certificate a domain presents on port 443: subject, issuer, validity dates, days remaining, subject alternative names, SHA-256dossier_redirects— Trace the redirect chain from https://<domain>/, one entry per hop with its status code and target, up to 10 hops. Use to debug redirect loodossier_headers— Fetch https://<domain>/ and return every response header, so you can review Strict-Transport-Security, Content-Security-Policy, X-Frame-Optidossier_cors— Send a CORS preflight (OPTIONS) to https://<domain>/ and return the access-control-* headers in the answer. Use to check whether a site accedossier_web_surface— Summarise a domain's public web surface: robots.txt, sitemap.xml and the home page's title, description, OpenGraph and Twitter card tags. Usdossier_ai_crawlers— Report what a domain's robots.txt says to the major AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, meta-externalagendossier_llms_txt— Check whether a domain publishes an llms.txt, the markdown index some sites provide for AI agents. Requires a non-HTML content type and a ledossier_security_txt— Check whether a domain publishes /.well-known/security.txt (RFC 9116), the standard way to tell researchers where to report a vulnerability.dossier_whois— Look up a domain's registrar, creation date, expiry date and registry statuses. Use for an ownership or expiry check. Tries WHOIS over TCP pdossier_ct_log— List subdomains of a domain that appear in Certificate Transparency logs. Use to map what hosts a domain has exposed through the certificatedns_lookup— Resolve one DNS record type (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA or SRV) for a name and return the raw answers. Use for a quick, targetedip_lookup— Look up an IPv4 or IPv6 address: city, region, country, coordinates, timezone and the network (ASN and organisation) that announces it. Useuser_agent_parse— Parse a User-Agent header into browser, operating system, device and rendering engine. Use when reading server logs or request headers. Runsbase64_encode— Encode UTF-8 text as base64. Set url_safe for the URL-safe alphabet (- and _ in place of + and /, no padding), as used in JSON Web Tokens. Rbase64_decode— Decode base64 to UTF-8 text. Accepts the standard and the URL-safe alphabet, with or without padding or line breaks. Fails when the input isjwt_decode— Decode a JSON Web Token's header and payload. It does NOT verify the signature, so never treat the claims as trusted on the strength of thisjson_format— Validate JSON and re-print it with an indent of 2 or 4 spaces, or minified with indent 0. Use to check whether a string is valid JSON or tourl_encode— Percent-encode text for use in a URL query value or path segment (encodeURIComponent rules: everything except letters, digits and - _ . ! ~url_decode— Decode percent-encoded text. Fails on a malformed sequence such as a lone % sign. A plus sign is left as a plus; replace it with a space firuuid_generate— Generate UUIDs. Version 4 is fully random. Version 7 starts with a millisecond timestamp, so values sort by creation time, which suits datab
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:57:16 | ✓ | ✓ | 714 ms | 90 | active |
| 2026-11-17 21:26:40 | ✓ | ✓ | 879 ms | 90 | active |
| 2026-11-17 20:43:15 | ✓ | ✓ | 1026 ms | 86 | active |
| 2026-11-17 19:58:00 | ✓ | ✓ | 1224 ms | 86 | active |
| 2026-11-17 19:33:07 | ✓ | ✓ | 948 ms | 90 | active |
| 2026-11-17 18:56:50 | ✓ | ✓ | 1098 ms | 86 | active |
| 2026-11-17 18:27:03 | ✓ | ✓ | 960 ms | 90 | active |
| 2026-11-17 17:43:08 | ✓ | ✓ | 983 ms | 90 | active |
| 2026-11-17 16:57:35 | ✓ | ✓ | 949 ms | 90 | active |
| 2026-11-17 16:27:19 | ✓ | ✓ | 872 ms | 90 | active |
| 2026-11-17 15:43:57 | ✓ | ✓ | 852 ms | 90 | active |
| 2026-11-17 14:55:35 | ✓ | ✓ | 746 ms | 90 | active |
| 2026-11-17 14:25:25 | ✓ | ✓ | 1018 ms | 86 | active |
| 2026-11-17 13:40:21 | ✓ | ✓ | 1082 ms | 86 | active |
| 2026-11-17 12:56:14 | ✓ | ✓ | 875 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://drwho.me/mcp/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/drwho-me-mcp-mcp # JSON