Is io.github.Br0ski777/email-deliverability safe to use?

io.github.Br0ski777/email-deliverability has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.Br0ski777/email-deliverability?

io.github.Br0ski777/email-deliverability supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.Br0ski777/email-deliverability?

io.github.Br0ski777/email-deliverability is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is io.github.Br0ski777/email-deliverability actively maintained?

io.github.Br0ski777/email-deliverability is actively maintained — last commit was 2 days ago.

io.github.Br0ski777/email-deliverability

Audit email domain deliverability: SPF, DKIM, DMARC, MX. Score 0-100. x402.

GitHub

No known CVEs

No license

Actively maintained

Last commit 2d ago

Works with most clients

Transport:

0 tools

Grade F

MCPpedia last refreshed this data 1d ago

Edit this pageView history

Communication

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "email-deliverability": {
      "url": "https://email-deliverability.api.klymax402.com/mcp"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-br0ski777-email-deliverability-br0ski777)](https://mcppedia.org/s/io-github-br0ski777-email-deliverability-br0ski777)

Read me

What io.github.Br0ski777/email-deliverability does

Email deliverability audit for any domain. SPF, DKIM, DMARC, MX validation with score 0-100 and fix recommendations. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

18/100across 5 weighted dimensions

How we score →

0255075100

−82

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.Br0ski777/email-deliverability safe to use?: io.github.Br0ski777/email-deliverability has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.Br0ski777/email-deliverability?: io.github.Br0ski777/email-deliverability supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.Br0ski777/email-deliverability?: io.github.Br0ski777/email-deliverability is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.Br0ski777/email-deliverability actively maintained?: io.github.Br0ski777/email-deliverability is actively maintained — last commit was 2 days ago.

Similar servers

Others in communication

View all →

Mcp_agent_mail94

Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite

2.0k 6

Ms 365 Mcp Server91

A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API

862 22

Server90

PubNub Model Context Protocol MCP Server for Cursor and Claude

32 2

io.github.codefuturist/email-mcp88

IMAP/SMTP email MCP server — 47 tools, IMAP IDLE push, multi-account, AI triage.

77 2

MCP Security Weekly

Get CVE alerts and security updates for io.github.Br0ski777/email-deliverability and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Communication

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "email-deliverability": {
      "url": "https://email-deliverability.api.klymax402.com/mcp"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-br0ski777-email-deliverability-br0ski777)](https://mcppedia.org/s/io-github-br0ski777-email-deliverability-br0ski777)

Read me

What io.github.Br0ski777/email-deliverability does

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

Email Deliverability Audit API

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "email-deliverability": {
      "url": "https://email-deliverability.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl "https://email-deliverability.api.klymax402.com/api/audit?domain=..."
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

Tool	Method	Path	Price	Description
`email_audit_deliverability`	GET	`/api/audit`	$0.012	Audit email deliverability for a domain — checks SPF, DKIM, DMARC, MX records
`email_audit_deliverability`	POST	`/api/audit`	$0.012	Audit email deliverability for a domain — checks SPF, DKIM, DMARC, MX records (POST variant)

`email_audit_deliverability`

Use this when you need to audit email deliverability configuration for a domain. Returns structured JSON with authentication record analysis and a deliverability score 0-100.

Parameters

Name	Type	Required	Description
`domain`	string	yes	Domain to audit (e.g. example.com, gmail.com)

Example response:

{"score":65,"spf":{"found":true,"valid":true,"record":"v=spf1 include:_spf.google.com ~all"},"dkim":{"google":true,"default":false},"dmarc":{"found":true,"policy":"none","record":"v=DMARC1; p=none"},"mx":[{"priority":10,"exchange":"alt1.gmail-smtp-in.l.google.com"}],"recommendations":["Upgrade DMARC policy from none to quarantine","Add DKIM for default selector"]}

When to use: launching email campaigns, onboarding new domains for outreach, or diagnosing inbox placement issues. Essential for email marketers, sales teams, and IT admins managing domain reputation.

Not for: single email validation (use email_verify_address), finding email addresses (use email_find_by_name), domain WHOIS/DNS (use domain_lookup_intelligence).

`email_audit_deliverability`

Use this when you need to audit email deliverability configuration for a domain. Returns structured JSON with authentication record analysis and a deliverability score 0-100. POST variant of email_audit_deliverability -- same params passed as JSON body instead of query string.

Parameters

Name	Type	Required	Description
`domain`	string	yes	Domain to audit (e.g. example.com, gmail.com)

Example response:

{"score":65,"spf":{"found":true,"valid":true,"record":"v=spf1 include:_spf.google.com ~all"},"dkim":{"google":true,"default":false},"dmarc":{"found":true,"policy":"none","record":"v=DMARC1; p=none"},"mx":[{"priority":10,"exchange":"alt1.gmail-smtp-in.l.google.com"}],"recommendations":["Upgrade DMARC policy from none to quarantine","Add DKIM for default selector"]}

Not for: single email validation (use email_verify_address), finding email addresses (use `email_f

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

18/100across 5 weighted dimensions

How we score →

0255075100

−82

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.Br0ski777/email-deliverability safe to use?: io.github.Br0ski777/email-deliverability has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.Br0ski777/email-deliverability?: io.github.Br0ski777/email-deliverability supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.Br0ski777/email-deliverability?: io.github.Br0ski777/email-deliverability is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.Br0ski777/email-deliverability actively maintained?: io.github.Br0ski777/email-deliverability is actively maintained — last commit was 2 days ago.