drwho.me network and developer tools
REMOTE · DRWHO.ME
29 free tools: DNS, email auth (SPF, DKIM, DMARC), TLS, headers, WHOIS, dev utils.
Available components
Last scanned (3 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4468 tokens (~154/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "dossier_cors" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 83. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 77. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 67. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://drwho.me/mcp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=drwho.me | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 84bb692354e034a00eb98e22a38b3839 |
| SANs: drwho.me, *.drwho.me | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of drwho.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| drwho.me. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'none'; script-src 'self' https://static.cloudflareinsights.com https://www.googletagmanager.com; style-src 'self'; font-src 'self'; img-src 'self' data: https://www.googletagmanager.com; connect-src 'self' https://cloudflare-dns.com https://cloudflareinsights.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; form-action 'self'; base-uri 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), clipboard-write=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://drwho.me/mcp/mcp | Verified | 200 | |
| http (plaintext) | http://drwho.me/mcp/mcp | HTTPS enforced | 301 | https://drwho.me/mcp/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
base64_decode Base64 decode ~76
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 is not valid base64 or does not decode to text (binary data is not returned). Runs locally.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Base64 or base64url string. |
No output schema declared.
No examples provided.
base64_encode Base64 encode ~82
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. Runs locally. Returns the encoded string.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to encode. |
| url_safe | boolean | – | Use the URL-safe alphabet without padding. Default false. |
No output schema declared.
No examples provided.
dns_lookup DNS lookup ~150
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, targeted lookup, including on subdomains and names such as _dmarc.example.com; prefer dossier_dns for a domain's main records in one call. Queries Cloudflare DNS-over-HTTPS. Returns a JSON array of {name, type, TTL, data}; an empty array means the name exists but has no record of that type.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name to resolve, e.g. example.com or mail.example.com. |
| type | string | yes | Record type to query. |
No output schema declared.
No examples provided.
dossier_ai_crawlers AI-crawler policy ~197
Report what a domain's robots.txt says to the major AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, meta-externalagent): allowed, blocked or unspecified for each. Use to answer whether a site lets AI models train on or retrieve its content. A missing robots.txt is data, not an error: every crawler is then unspecified. One fetch, 10 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_cors CORS checker ~211
Send a CORS preflight (OPTIONS) to https://<domain>/ and return the access-control-* headers in the answer. Use to check whether a site accepts cross-origin requests from a given origin and method. One request, 5 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
| method | string | – | Access-Control-Request-Method to send, e.g. POST. Defaults to GET. |
| origin | string | – | Origin header to send, e.g. https://app.example.com. Defaults to https://domainposture.com. |
No output schema declared.
No examples provided.
dossier_ct_log Certificate log lookup ~174
List subdomains of a domain that appear in Certificate Transparency logs. Use to map what hosts a domain has exposed through the certificates issued for it. Queries crt.sh, then certspotter if crt.sh fails; capped at 100 unique names, 10 s timeout. A name in the log is not proof the host still exists. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_dkim DKIM lookup ~231
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 common selectors used by large mail providers. A selector not on the list will not be found, so an empty result does not prove the domain has no DKIM. Distinguishes a selector that is absent from one that could not be resolved. Parallel Cloudflare DNS-over-HTTPS TXT queries. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
| selectors | array | – | DKIM selector names to probe, e.g. ["google", "s1"]. Omit to use the built-in list. |
No output schema declared.
No examples provided.
dossier_dmarc DMARC checker ~173
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 rejected, quarantined or only reported. Queries Cloudflare DNS-over-HTTPS, 5 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_dns DNS records ~175
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 record type or for MX, CNAME and SRV. Sends six Cloudflare DNS-over-HTTPS queries in parallel, 5 s timeout each. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_dnssec DNSSEC checker ~154
Check whether a domain's zone is signed with DNSSEC and validates: DS and DNSKEY records plus the resolver's AD (authenticated data) flag. Queries Cloudflare DNS-over-HTTPS with DO=1, 8 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_headers Security headers ~186
Fetch https://<domain>/ and return every response header, so you can review Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy. Returns the final URL after redirects and the headers as served. One GET, 5 s timeout. For the redirect hops themselves use dossier_redirects. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_llms_txt llms.txt checker ~164
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 leading markdown heading, so a catch-all page that answers 200 with HTML does not count. One fetch, 10 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_mta_sts MTA-STS checker ~179
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. Resolves the _mta-sts TXT record, then fetches https://mta-sts.<domain>/.well-known/mta-sts.txt, 10 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_mx MX lookup ~153
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 DMARC. Queries Cloudflare DNS-over-HTTPS, 5 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_redirects Redirect chain ~158
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 loops or confirm an HTTP to HTTPS or apex to www redirect. 5 s per hop. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_security_txt security.txt checker ~163
Check whether a domain publishes /.well-known/security.txt (RFC 9116), the standard way to tell researchers where to report a vulnerability. Returns the Contact and Expires fields. Requires a non-HTML content type and a Contact field. One fetch, 10 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_spf SPF checker ~216
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 failures; pair with dossier_dmarc and dossier_dkim for the whole email-authentication picture. Reads TXT records over Cloudflare DNS-over-HTTPS. Reports records that contain v=spf1 but do not start with it (for example behind a hidden byte-order mark) as lookalikes that receivers discard, and treats more than one SPF record as an error, as RFC 7208 requires. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_summary Domain summary (9 checks) ~287
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, DMARC, DKIM, DNSSEC, TLS-RPT, MTA-STS and the TLS certificate. Use it first when asked how a domain is set up or whether its email can be spoofed; then call the single dossier_* tool for any check you need the raw data for. Each line has the check id, its status, a severity (info, low, medium, high, critical) and a one-line reason, graded by the same rules as Domain Posture. It does not return raw records or fix instructions, and it leaves out the nine web and discovery checks; the full 18-check graded report is linked in the result. Returns JSON {domain, checks:[{id, status, severity, reason}], worst}. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_tls TLS certificate ~176
Read the TLS certificate a domain presents on port 443: subject, issuer, validity dates, days remaining, subject alternative names, SHA-256 fingerprint and whether the chain validated. Use to check expiry or a name mismatch. It does not test cipher suites or protocol versions. One TLS handshake from the drwho.me server, 5 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_tlsrpt TLS-RPT checker ~149
Look up a domain's SMTP TLS Reporting policy at _smtp._tls.<domain>. Use to confirm the domain receives reports about failed TLS delivery of its inbound mail. Queries Cloudflare DNS-over-HTTPS. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_web_surface Web surface ~160
Summarise a domain's public web surface: robots.txt, sitemap.xml and the home page's title, description, OpenGraph and Twitter card tags. Use for a quick SEO or link-preview review. Three parallel HTTPS fetches capped at 64 KB each. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
dossier_whois WHOIS lookup ~174
Look up a domain's registrar, creation date, expiry date and registry statuses. Use for an ownership or expiry check. Tries WHOIS over TCP port 43, then RDAP over HTTPS when the registry refuses; returns not_applicable when neither answers, which is common for some country-code domains. 15 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected. |
No output schema declared.
No examples provided.
ip_lookup IP lookup ~129
Look up an IPv4 or IPv6 address: city, region, country, coordinates, timezone and the network (ASN and organisation) that announces it. Use when you need location or ownership context for an address; it does not accept hostnames, so resolve those with dns_lookup first. Data comes from ipinfo.io and location is approximate. Returns JSON {ip, city, region, country, loc, org, timezone}.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 or IPv6 address, e.g. 1.1.1.1 or 2606:4700::1111. |
No output schema declared.
No examples provided.
json_format JSON formatter ~97
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 to make it readable. Runs locally. Returns the formatted JSON, or the parser's error message.
| Name | Type | Req | Description |
|---|---|---|---|
| indent | – | – | Spaces per level: 0 (minify), 2 or 4. Default 2. |
| text | string | yes | The JSON text. |
No output schema declared.
No examples provided.
jwt_decode JWT decoder ~92
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 this tool. Use to inspect claims such as exp, iss and aud while debugging. Runs locally; the token is not stored or sent anywhere. Returns JSON {header, payload, signature}.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The JWT: three base64url parts separated by dots. |
No output schema declared.
No examples provided.
url_decode URL decode ~65
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 first if the text came from an HTML form. Runs locally.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Percent-encoded text. |
No output schema declared.
No examples provided.
url_encode URL encode ~63
Percent-encode text for use in a URL query value or path segment (encodeURIComponent rules: everything except letters, digits and - _ . ! ~ * ' ( ) is encoded). Runs locally. Returns the encoded string.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to encode. |
No output schema declared.
No examples provided.
user_agent_parse User agent parser ~88
Parse a User-Agent header into browser, operating system, device and rendering engine. Use when reading server logs or request headers. Runs locally with no network call. Returns JSON {browser:{name,version}, os:{name,version}, device:{type,vendor,model}, engine:{name}}; unknown fields are empty strings.
| Name | Type | Req | Description |
|---|---|---|---|
| ua | string | yes | The full User-Agent header value. |
No output schema declared.
No examples provided.
uuid_generate UUID generator ~95
Generate UUIDs. Version 4 is fully random. Version 7 starts with a millisecond timestamp, so values sort by creation time, which suits database keys. Runs locally with a cryptographic random source. Returns a JSON array of strings.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many to generate, 1 to 100. Default 1. |
| version | – | – | UUID version: 4 or 7. Default 4. |
No output schema declared.
No examples provided.
How do I install the drwho.me network and developer tools MCP server?
drwho.me network and developer tools is a hosted endpoint at https://drwho.me/mcp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · drwho.me
claude mcp add --transport http me-drwho-tools 'https://drwho.me/mcp/mcp'
What is the drwho.me network and developer tools MCP server?
drwho.me network and developer tools is an MCP server listed in the public MCP registry as me.drwho/tools. 29 free tools: DNS, email auth (SPF, DKIM, DMARC), TLS, headers, WHOIS, dev utils. This page covers its hosted endpoint (https://drwho.me/mcp/mcp).
Is the drwho.me network and developer tools MCP server safe to use?
drwho.me network and developer tools scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the drwho.me network and developer tools MCP server expose?
drwho.me network and developer tools exposes 29 tools: dossier_summary, dossier_dns, dossier_mx, dossier_spf, dossier_dmarc, and 24 more. Their descriptions and schemas cost roughly 4,417 tokens of context every time the server is loaded.
Does the drwho.me network and developer tools MCP server require authentication?
No. We connected to drwho.me network and developer tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the drwho.me network and developer tools MCP server still maintained?
drwho.me network and developer tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.