Lookproof DNS, mail and TLS security checks MCP server
io.github.lookproof/lookproof-mcplookproofstreamable-httpv0.2.1Scanned
SPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS and DNS checks. Free API key or pay-per-call (x402).
21 tools: 20 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 19
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
20 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Lookproof DNS, mail and TLS security checks MCP server can do
The Lookproof DNS, mail and TLS security checks MCP server is published by the GitHub account lookproof. It has 21 tools. It can create or change data (20 tools: mail_check, spf, spf_flatten, dmarc and 16 more), but cannot delete data. 1 tool only reads.
19 tools bring in text other people can write (mail_check, spf, spf_flatten and 16 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 0.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
21 tools
Changes things 20Claude Code: ask
bimiUse when the user asks why a brand logo does not show in inboxes, or about BIMI.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: BIMI record check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
caaUse when the user asks which certificate authorities may issue SSL certificates for a domain, or why issuance is refused.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: CAA record check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
dkimUse when the user asks whether the DKIM key for a known selector is published and valid.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: DKIM record check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
dkim_discoverUse when the user asks whether a domain has DKIM but no selector is known.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: DKIM selector finder
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
dmarcUse when the user asks about a domain's DMARC record itself, or why reports do not arrive.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: DMARC check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
dmarc_parseUse when the user pastes a DMARC record to explain or check before publishing.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: DMARC record parser
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
dnssecUse when the user asks whether a domain's DNS is secure or DNSSEC-signed, or why it fails on validating resolvers.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: DNSSEC check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
mail_checkUse when the user asks about mail setup or why mail goes to spam (no reputation, content or blocklist checks).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Mail configuration check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
mail_providerUse when the user asks who hosts a domain's email (Google, Microsoft 365...) or which services send for it.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Mail provider detection
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
mta_stsUse when the user asks about MTA-STS or whether inbound mail is protected against TLS downgrade.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: MTA-STS and TLS-RPT check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
mxUse when the user asks which mail servers a domain uses or why it cannot receive mail.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: MX lookup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
nameserversUse when the user asks which name servers a domain uses, who hosts its DNS (from the NS names) or whether they are redundant.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Name server check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
rdapUse when the user asks for a domain's whois or registration data: when it expires, the registrar, or if it is locked.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: RDAP domain lookup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
security_headersUse when the user asks which security headers a live website sends or if it forces HTTPS.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Security headers check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
spfUse 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: SPF check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
spf_flattenUse when the user asks which IP addresses or servers may send mail for a domain, or to flatten SPF.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: SPF flattening check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
spf_parseUse when the user pastes an SPF record to explain or check before publishing.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: SPF record parser
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
spoofableUse when the user asks whether someone can send email pretending to be a domain.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Email spoofing check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tls_certificateUse when the user asks to check a site's SSL/TLS certificate, why HTTPS fails or when it expires.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: TLS certificate check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tlsrptUse when the user asks only about TLS-RPT (SMTP TLS reporting).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: TLS-RPT check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
dns_lookupUse when the user asks for the current public DNS records of a name, e.g.Reads text others writeNo findings
Why it is in this group
- The name "dns_lookup" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: DNS lookup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write19
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:19 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 21
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 21 tools that change things (21 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.lookproof.dev/mcp: tools/list returned 22 tools to an anonymous client, including mail_check (write), spf (write), spf_flatten (write), dmarc (write), dkim (write) and 16 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http lookproof https://api.lookproof.dev/mcpclaude mcp add --transport http lookproof https://api.lookproof.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lookproof__dns_lookup"
],
"ask": [
"mcp__lookproof__mail_check",
"mcp__lookproof__spf",
"mcp__lookproof__spf_flatten",
"mcp__lookproof__dmarc",
"mcp__lookproof__dkim",
"mcp__lookproof__dkim_discover",
"mcp__lookproof__mta_sts",
"mcp__lookproof__tlsrpt",
"mcp__lookproof__mx",
"mcp__lookproof__spoofable",
"mcp__lookproof__bimi",
"mcp__lookproof__mail_provider",
"mcp__lookproof__spf_parse",
"mcp__lookproof__dmarc_parse",
"mcp__lookproof__dnssec",
"mcp__lookproof__caa",
"mcp__lookproof__nameservers",
"mcp__lookproof__rdap",
"mcp__lookproof__tls_certificate",
"mcp__lookproof__security_headers"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lookproof. Review it before you use it.
Capability tags behind 19 rules
- mcp__lookproof__mail_check untrusted-input
- mcp__lookproof__spf untrusted-input
- mcp__lookproof__spf_flatten untrusted-input
- mcp__lookproof__dmarc untrusted-input
- mcp__lookproof__dkim untrusted-input
- mcp__lookproof__dkim_discover untrusted-input
- mcp__lookproof__mta_sts untrusted-input
- mcp__lookproof__tlsrpt untrusted-input
- mcp__lookproof__mx untrusted-input
- mcp__lookproof__spoofable untrusted-input
- mcp__lookproof__bimi untrusted-input
- mcp__lookproof__mail_provider untrusted-input
- mcp__lookproof__dns_lookup untrusted-input
- mcp__lookproof__dnssec untrusted-input
- mcp__lookproof__caa untrusted-input
- mcp__lookproof__nameservers untrusted-input
- mcp__lookproof__rdap untrusted-input
- mcp__lookproof__tls_certificate untrusted-input
- mcp__lookproof__security_headers untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.lookproof/lookproof-mcp/verify?hash=989e54becb0d64c504724ea88b900f2053811b71d749693ae675963feb1da7c3" | jq -e '.changed == false'Pinned hash 989e54becb0d, from Nov 21, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.lookproof/lookproof-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.lookproof/lookproof-mcp)Source: MCP Registry · repository. Synced Nov 21, 2026, 13:17 UTC.
Lookproof DNS, mail and TLS security checks MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Lookproof DNS, mail and TLS security checks MCP server safe?
- No scan can promise that. What its definitions show: 21 tools, 20 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Lookproof DNS, mail and TLS security checks MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Lookproof DNS, mail and TLS security checks MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Lookproof DNS, mail and TLS security checks MCP server have?
- 21 tools: 20 write, 1 read. mail_check, spf, spf_flatten, dmarc, dkim, dkim_discover, mta_sts, tlsrpt and 13 more.
Does the Lookproof DNS, mail and TLS security checks MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Lookproof DNS, mail and TLS security checks MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Lookproof DNS, mail and TLS security checks MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.