Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lookproof DNS, mail and TLS security checks

REMOTE · API.LOOKPROOF.DEV · 2 COMPONENTS

SPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS and DNS checks. Free API key or pay-per-call (x402).

72 Trust /100

Last scanned (10 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2324 tokens (~110/item across 21 items; 21 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 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

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 72

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://api.lookproof.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lookproof.dev CN=YE2,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 ECDSA 256 ECDSA-SHA384 61e367e28591b88886c5dcc2ff92f341e35
SANs: *.lookproof.dev, lookproof.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.lookproof.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
lookproof.dev. No DS 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
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.lookproof.dev/mcp Verified 200
http (plaintext) http://api.lookproof.dev/mcp HTTPS enforced 301 https://api.lookproof.dev/mcp
MCP tools · 21 exposed · ~2,192 tokens

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 →

Tool Tokens
bimi ~114

Use when the user asks why a brand logo does not show in inboxes, or about BIMI. Returns the BIMI record, logo and certificate URLs and whether DMARC is enforced as BIMI requires. The logo is not downloaded. Ex: 'Is BIMI set up for example.com?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.
selectorstring–Optional BIMI selector (default: default).

No output schema declared.

No examples provided.

caa ~91

Use when the user asks which certificate authorities may issue SSL certificates for a domain, or why issuance is refused. Returns CAA issuers for normal and wildcard certificates and iodef, from parents too. Ex: 'Can Let's Encrypt issue for example.com?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

dkim ~108

Use when the user asks whether the DKIM key for a known selector is published and valid. Returns key type, size, testing and revoked flags with findings. Unknown selector: use dkim_discover. Ex: 'Check DKIM selector1 for example.com'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.
selectorstringyesThe DKIM selector, e.g. selector1.

No output schema declared.

No examples provided.

dkim_discover ~100

Use when the user asks whether a domain has DKIM but no selector is known. Tries 31 common selectors and returns each key found with type, size and flags. None found is a hint, not proof that DKIM is missing. Ex: 'Does example.com use DKIM?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

dmarc ~99

Use when the user asks about a domain's DMARC record itself, or why reports do not arrive. Returns policy, subdomain policy, pct, alignment and report addresses with findings. For a spoofing verdict use spoofable. Ex: 'What is the DMARC policy of example.com?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

dmarc_parse ~102

Use when the user pastes a DMARC record to explain or check before publishing. Returns p, sp, np, adkim, aspf, rua, ruf and unknown tags, with the same findings as dmarc. No DNS lookups. Ex: 'Explain v=DMARC1; p=none'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
recordstringyesThe DMARC record as text.

No output schema declared.

No examples provided.

dns_lookup ~158

Use when the user asks for the current public DNS records of a name, e.g. to confirm a change. Returns A, AAAA, CNAME, MX, NS, TXT, SOA, CAA or SRV records with TTL and the resolver that answered. No PTR (reverse DNS) lookups. Ex: 'Show the TXT records of example.com'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
namestringyesThe DNS name to look up, e.g. _dmarc.example.com.
typesstring–Optional record types, comma-separated: A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV (default A).

No output schema declared.

No examples provided.

dnssec ~105

Use when the user asks whether a domain's DNS is secure or DNSSEC-signed, or why it fails on validating resolvers. Returns secure, insecure, bogus or unknown with DS and DNSKEY details. For name servers see nameservers, for certificate rules caa. Ex: 'Is the DNS of example.com secure?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

mail_check ~134

Use when the user asks about mail setup or why mail goes to spam (no reputation, content or blocklist checks). Returns MX, SPF, DMARC, DKIM (your selectors) and a spoofing category. One domain per call; domain_health (needs an API key) adds DKIM discovery and MTA-STS. Ex: 'Check example.com'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
dkim_selectorsstring–Optional DKIM selectors, comma-separated (at most 5).
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

mail_provider ~94

Use when the user asks who hosts a domain's email (Google, Microsoft 365...) or which services send for it. Returns providers matched from MX hosts and SPF includes, with evidence. For raw MX records use mx. Ex: 'Who handles email for example.com?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

mta_sts ~98

Use when the user asks about MTA-STS or whether inbound mail is protected against TLS downgrade. Returns the record, the fetched policy, mode, max_age and MX coverage, plus the TLS-RPT record. Ex: 'Is MTA-STS set up for example.com?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

mx ~102

Use when the user asks which mail servers a domain uses or why it cannot receive mail. Returns MX hosts by preference with addresses, null MX and implicit MX. Provider name: mail_provider; reverse DNS of the servers: domain_health (needs an API key). Ex: 'What are the MX records of example.com?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

nameservers ~105

Use when the user asks which name servers a domain uses, who hosts its DNS (from the NS names) or whether they are redundant. Returns the NS set with addresses (up to eight); flags a single server, unresolvable ones, one network and missing glue. Ex: 'Which name servers does example.com use?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

rdap ~98

Use when the user asks for a domain's whois or registration data: when it expires, the registrar, or if it is locked. Returns registrar, creation, change and expiry dates, statuses and name servers from RDAP. No contact data. Ex: 'When does example.com expire?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

security_headers ~94

Use when the user asks which security headers a live website sends or if it forces HTTPS. Returns the redirects from http:// and https:// and HSTS, CSP, frame protection, Referrer-Policy and cookie flags. Ex: 'Which security headers does example.com miss?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

spf ~101

Use when the user asks if a domain's SPF record is valid, why a sender fails SPF or if it hits the 10-lookup limit. Returns the include tree, all qualifier and lookup counts. For the IP ranges use spf_flatten. Ex: 'Is the SPF of example.com valid?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

spf_flatten ~99

Use when the user asks which IP addresses or servers may send mail for a domain, or to flatten SPF. Returns every IPv4 and IPv6 block the record authorizes, with the include it came from. Analysis only. Ex: 'Which IPs may send mail as example.com?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

spf_parse ~95

Use when the user pastes an SPF record to explain or check before publishing. Returns mechanisms, qualifiers, syntax errors and the number of DNS-lookup terms. No DNS lookups; for a live domain use spf. Ex: 'Explain v=spf1 include:_spf.google.com ~all'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
recordstringyesThe SPF record as text.

No output schema declared.

No examples provided.

spoofable ~98

Use when the user asks whether someone can send email pretending to be a domain. Returns protected, partial, monitoring, unprotected or broken from the DMARC policy, with gaps. Describes the policy; it does not prove forged mail gets through. Ex: 'Can someone spoof example.com?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

tls_certificate ~98

Use when the user asks to check a site's SSL/TLS certificate, why HTTPS fails or when it expires. Returns trust, name match, expiry, issuer, chain, key and TLS version for port 443, with findings. Ex: 'When does the SSL certificate of example.com expire?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

tlsrpt ~99

Use when the user asks only about TLS-RPT (SMTP TLS reporting). Returns the _smtp._tls record and its report addresses, with findings. For MTA-STS use mta_sts, which includes TLS-RPT. Ex: 'Where do TLS reports for example.com go?'. Free trial without an API key: a few calls a day.

NameTypeReqDescription
domainstringyesA public domain name, e.g. example.com.

No output schema declared.

No examples provided.

Install

How do I install the Lookproof DNS, mail and TLS security checks MCP server?

Lookproof DNS, mail and TLS security checks is a hosted endpoint at https://api.lookproof.dev/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 · api.lookproof.dev

# add to Claude Code
claude mcp add --transport http lookproof-lookproof-mcp 'https://api.lookproof.dev/mcp'
Common questions

What is the Lookproof DNS, mail and TLS security checks MCP server?

Lookproof DNS, mail and TLS security checks is an MCP server listed in the public MCP registry as io.github.lookproof/lookproof-mcp. SPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS and DNS checks. Free API key or pay-per-call (x402). This page covers its hosted endpoint (https://api.lookproof.dev/mcp).

Is the Lookproof DNS, mail and TLS security checks MCP server safe to use?

Lookproof DNS, mail and TLS security checks scores 72 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 Lookproof DNS, mail and TLS security checks MCP server expose?

Lookproof DNS, mail and TLS security checks exposes 21 tools: mail_check, spf, spf_flatten, dmarc, dkim, and 16 more. Their descriptions and schemas cost roughly 2,192 tokens of context every time the server is loaded.

Does the Lookproof DNS, mail and TLS security checks MCP server require authentication?

No. We connected to Lookproof DNS, mail and TLS security checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Lookproof DNS, mail and TLS security checks MCP server still maintained?

Lookproof DNS, mail and TLS security checks is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Lookproof DNS, mail and TLS security checks MCP server?

VerifyMCP ran 12 checks on Lookproof DNS, mail and TLS security checks, covering TLS certificate, Authorization, HTTPS, HSTS header and 8 more. One item could not be completed, a gap on our side rather than a finding about Lookproof DNS, mail and TLS security checks: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.