Lookproof DNS, mail and TLS security checks
PYPI · LOOKPROOF-MCP · 2 COMPONENTS
SPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS and DNS checks. Free API key or pay-per-call (x402).
Available components
Last scanned (10 hours ago)
Scores higher than 64% of PyPI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to lookproof/x402-examples). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2207 tokens (~91/item across 24 items; 24 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 7% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- 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 package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 −12
- Malware scan: pass → unverified ▼ security
- Schema quality: 52 → 91 ▼ functional
- Tool coverage: 0% → 7% ▲ functional
- Schema quality: fair → good functional
- Package version: 0.2.0 → 0.2.1 functional
- 20 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- Package version: 0.1.0 → 0.2.0 functional
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 21 Nov 2026 · Analysed pypi/lookproof-mcp@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | lookproof/x402-examples |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/lookproof/x402-examples/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.2.1 |
| Rekor log index | 4033002308 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:051d0de225214b7475b27574619890964700f74b5d1bcecdaf8b70b8b716f9dd |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
bimi ~91
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| selector | – | – | – |
No output schema declared.
No examples provided.
caa ~78
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
dkim ~85
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'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| selector | string | yes | – |
No output schema declared.
No examples provided.
dkim_discover ~87
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?'. Costs $0.02 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
dmarc ~86
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
dmarc_parse ~93
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'. Costs $0.002 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| record | string | yes | – |
No output schema declared.
No examples provided.
dns_lookup ~137
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'. Costs $0.005 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| types | – | – | Optional record types, comma-separated: A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV (default A). |
No output schema declared.
No examples provided.
dnssec ~92
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
domain_health ~107
Use when the user asks for a full email and DNS audit of a domain, or why mail is rejected or lands in spam. Returns MX, SPF, DMARC, DKIM, MTA-STS, DNSSEC, mail server reverse DNS, BIMI, CAA and provider, with findings. No blocklist or content check. Ex: 'Why does mail from example.com go to spam?'. Costs $0.08 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_spending ~27
Free. Shows payment mode, USDC spent this session, calls made and budget left.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mail_check ~113
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 adds DKIM discovery and MTA-STS. Ex: 'Check example.com'. Costs $0.03 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| dkim_selectors | – | – | Optional DKIM selectors, comma-separated (at most 5). |
| domain | string | yes | – |
No output schema declared.
No examples provided.
mail_provider ~81
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?'. Costs $0.005 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
mta_sts ~85
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?'. Costs $0.02 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
mx ~84
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. Ex: 'What are the MX records of example.com?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
nameservers ~92
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
rdap ~85
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
security_headers ~81
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
site_health ~74
Use when the user asks for a website security check in one call. Returns the SSL/TLS certificate, redirects and security headers, and domain expiry and status from RDAP, with findings. Ex: 'Is example.com set up securely?'. Costs $0.025 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
spf ~88
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
spf_flatten ~86
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
spf_parse ~87
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'. Costs $0.002 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| record | string | yes | – |
No output schema declared.
No examples provided.
spoofable ~85
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
tls_certificate ~85
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
tlsrpt ~86
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?'. Costs $0.01 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Lookproof DNS, mail and TLS security checks MCP server?
Lookproof DNS, mail and TLS security checks runs locally as a PyPI package, launched with uvx lookproof-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · lookproof-mcp
claude mcp add lookproof-lookproof-mcp -- uvx lookproof-mcp
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 PyPI package (lookproof-mcp).
Is the Lookproof DNS, mail and TLS security checks MCP server safe to use?
Lookproof DNS, mail and TLS security checks scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 24 tools: get_spending, domain_health, site_health, mail_check, spf, and 19 more. Their descriptions and schemas cost roughly 2,095 tokens of context every time the server is loaded.
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 licence is the Lookproof DNS, mail and TLS security checks MCP server under?
Lookproof DNS, mail and TLS security checks declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Lookproof DNS, mail and TLS security checks MCP server?
VerifyMCP ran 15 checks on Lookproof DNS, mail and TLS security checks, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Lookproof DNS, mail and TLS security checks: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.