mambalabsdev/mcp-domain-deliverability-checker
by Various
MCP server for the Mamba Labs Domain Deliverability Checker actor: SPF, DKIM, DMARC, MX, blacklist, catch-all, domain age. Clay-ready.
MCP
mambalabsdev/mcp-domain-deliverability-checker
Added 19 June 2026
Overview
An MCP server that checks email deliverability indicators for domains including SPF, DKIM, DMARC, MX records, blacklist status, catch-all detection, and domain age. It is designed to work with Clay (a data enrichment platform) for automated domain validation in outreach workflows.
Best for
Best for
Developers integrating domain deliverability validation into sales or marketing automation systems
Use cases
- Validate domain email deliverability before sending cold emails
- Assess domain reputation and technical setup for lead scoring
- Automate pre-contact domain checks in CRM or marketing pipelines
Notes
An MCP server that checks email deliverability indicators for domains including SPF, DKIM, DMARC, MX records, blacklist status, catch-all detection, and domain age. It is designed to work with Clay (a data enrichment platform) for automated domain validation in outreach workflows.
0 stars on GitHub. Last updated 2026-06-19. Licensed MIT.
Use cases
- Validate domain email deliverability before sending cold emails
- Assess domain reputation and technical setup for lead scoring
- Automate pre-contact domain checks in CRM or marketing pipelines
Pros
- Covers multiple key deliverability factors in one request
- Ready-to-use as an MCP server for integration with tools like Clay
- Lightweight JavaScript implementation
Cons
- No community adoption yet (0 stars) implies early stage and potential instability
- Requires self-hosting an MCP client or server environment
- Limited documentation or support beyond the basic readme
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Covers multiple key deliverability factors in one request
- Ready-to-use as an MCP server for integration with tools like Clay
- Lightweight JavaScript implementation
Cons
- No community adoption yet (0 stars) implies early stage and potential instability
- Requires self-hosting an MCP client or server environment
- Limited documentation or support beyond the basic readme
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.