com.mambabuilt/mcp-domain-deliverability-checker
NPM · @MAMBALABSDEV/MCP-DOMAIN-DELIVERABILITY-CHECKER
Audit a domain email deliverability via Apify: SPF, DKIM, DMARC, MX, blacklist, catch-all, age.
Available components
Last scanned (23 hours ago)
Scores higher than 53% of npm servers
Category Marketing and SEO
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 423 tokens (~423/item across 1 items; 1 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 Management50
- Stability check failed: the tool surface changed between 1.0.1 and 1.2.0: 0 tool removals, 1 breaking changes, 0 additions. See how to fix → Fail
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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.
- 24 Oct 26 0
- Package version: 1.1.1 → 1.2.0 functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47.
- 16 Oct 26 0
- Schema quality: 370 → 423 ▼ functional
- Package version: 1.1.1 → 1.2.0 functional
- 15 Oct 26 +37
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Schema quality: 205 → 370 ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Security disclosure: unverified → pass ▲ functional
- Package version: 1.0.1 → 1.1.1 functional
- 14 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- Package version: 1.0.1 → 1.1.1 functional
- 11 Oct 26 −48
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: pass → unverified ▼ functional
- Package version: 1.0.1 → 1.1.1 functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
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 4 Nov 2026 · Analysed npm/@mambalabsdev/mcp-domain-deliverability-checker@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
check_domain_deliverability Check Domain Deliverability ~423
Audit the email deliverability and DNS health of one domain or a list of domains before sending cold email from it or to it. Returns one flat, Clay-ready JSON row per domain: SPF, DKIM, and DMARC records with the DMARC policy, MX records and mail provider, DNS blacklist status, catch-all status, domain age, and a 0 to 100 health score. Results are cached for 24 hours per domain; set skipCache to force a fresh audit. It reads public DNS only: it sends no email and does not verify individual mailboxes, so use an email verifier for that. A run that does not succeed is returned as an error with its run ID and status. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
| Name | Type | Req | Description |
|---|---|---|---|
| attempt_catch_all | boolean | – | Set true to run the SMTP catch-all probe. The Apify platform blocks outbound port 25, so on Apify the probe returns unknown; leave it off unless you run the actor where port 25 is open. Default: fals… |
| batchSize | integer | – | How many domains from the list are audited at the same time. Higher finishes a long list sooner. 1 to 10. Default: 5. |
| domain | string | – | One bare domain to audit, without https:// or a path, e.g. stripe.com. Provide this or domains. |
| domains | array | – | A list of bare domains audited in one run, one row per domain, e.g. ["stripe.com", "notion.so"]. When set, domain is ignored. |
| max_charge_usd | number | – | Optional. The run stops before the next result that would take this run's charges over this amount, and keeps every result already charged. Leave empty to rely only on the maximum cost per run you se… |
| skipCache | boolean | – | Set true to ignore the 24 hour result cache and audit the domain again now, for example right after a DNS change. Default: false. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-domain-deliverability-checker server?
com.mambabuilt/mcp-domain-deliverability-checker runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-domain-deliverability-checker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-domain-deliverability-checker
claude mcp add com-mambabuilt-mcp-domain-deliverability-checker -- npx -y @mambalabsdev/mcp-domain-deliverability-checker
What is the com.mambabuilt/mcp-domain-deliverability-checker server?
com.mambabuilt/mcp-domain-deliverability-checker is listed in the public MCP registry as com.mambabuilt/mcp-domain-deliverability-checker. Audit a domain email deliverability via Apify: SPF, DKIM, DMARC, MX, blacklist, catch-all, age. This page covers its npm package (@mambalabsdev/mcp-domain-deliverability-checker).
Is the com.mambabuilt/mcp-domain-deliverability-checker server safe to use?
com.mambabuilt/mcp-domain-deliverability-checker scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 com.mambabuilt/mcp-domain-deliverability-checker server expose?
com.mambabuilt/mcp-domain-deliverability-checker exposes 1 tool: check_domain_deliverability. Their descriptions and schemas cost roughly 423 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-domain-deliverability-checker server still maintained?
com.mambabuilt/mcp-domain-deliverability-checker is still listed as active in the MCP registry. We last reached this channel on 4 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 com.mambabuilt/mcp-domain-deliverability-checker server under?
com.mambabuilt/mcp-domain-deliverability-checker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.