B2B Email & Domain Scorer

dev.workers.mohamed-bahaa53000.email-scorerPublished by email-scorer.mohamed-bahaa53000.workers.devOfficial publisherv1.2.1Updated Oct 26, 2026

Lead email decisions: keep / fix typo / review / drop, plus a ready-to-send list. Paid: RapidAPI

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that scores lead emails and company domains, returning a keep, fix, review or drop decision before outreach.

What you can do
  • Score a single lead email and get an action (keep, fix, review, drop), a corrected send_to address, a plain-English reason, a verdict, a 0-100 score and typo suggestions
  • Inspect a company domain, URL or email for MX records, mail provider, free or disposable flags and SPF/DMARC
  • Optionally request deeper checks such as SPF/DMARC on a single email score
  • Clean a whole list in one call and get a deduplicated ready-to-send list with action counts (paid endpoint only)
When to use it
Useful for sales, SDR and lead-gen agents that need to filter disposable or free-mail signups, flag role inboxes like info@ or sales@, fix typo domains in form signups, or qualify a company domain before outreach.
Requirements
A remote Streamable HTTP endpoint; nothing to install locally. The demo endpoint needs no key but is limited to 10 tool calls per IP per UTC day and has no batch. The paid RapidAPI endpoint requires the X-RapidAPI-Key and X-RapidAPI-Host headers; a free Basic plan is available. Clients that only support stdio can bridge via npx mcp-remote.
Before you install
The paid endpoint is billed per request through RapidAPI and needs an X-RapidAPI-Key; the free Basic plan is limited to 100 requests per month. Email addresses and domains you submit are sent to a third-party hosted service and may appear in standard request logs. Scores are heuristics for lead quality, not a deliverability guarantee, and no mail is sent or SMTP probed.

Installation

In SourceWeft

  1. Open B2B Email & Domain Scorer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.mohamed-bahaa53000.email-scorer%2Fb2b-email-domain-scorer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "b2b-email-domain-scorer": {
      "type": "http",
      "url": "https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp"
    }
  }
}

README

B2B Email & Domain Scorer — remote MCP server

For sales and lead-gen teams: get a keep, fix, review or drop decision for every lead email before you send outreach.

1. Connect (free, no key; works in Claude Desktop, Cursor, Cline, VS Code and any client that supports remote Streamable HTTP):

json
{  "mcpServers": {    "email-scorer": {      "url": "https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp"    }  }}

2. Ask: "Is [email protected] OK to email?" Your agent calls:

json
{"name":"score_email","arguments":{"email":"[email protected]"}}

3. Get (real output from the free demo endpoint, trimmed):

json
{"action":"fix","send_to":"[email protected]", "action_reason":"Likely typo: send to [email protected] instead", "verdict":"risky","score":10,"reasons":["likely_typo","typo_domain_is_disposable_or_parked"]}

What makes it different

  • Decisions, not raw flags: most email validators return 15 booleans and leave your agent to guess. This returns what to do.
  • Typos fixed, not just flagged: [email protected] comes back as fix -> [email protected].
  • A ready-to-send list: score_batch returns send_list, the deduplicated list of kept plus corrected addresses, and keep/fix/review/drop counts.
  • B2B-aware: role inboxes (info@, sales@) and free mailboxes go to review with the reason, because they reach a company but rarely a decision-maker.
  • No mail is sent (no SMTP probing that can get your IP blocklisted), and it's MCP-native with a free, keyless demo endpoint.

No-code version

Not building an agent? The same scoring comes in ready-made tools:

Try it free

  • No key, right now: point any MCP client at https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp (10 tool calls per IP per day).
  • Free RapidAPI plan: 100 requests/month on the Basic plan, no card needed. Pro is $3.99 for 30,000.

This is a hosted (remote) MCP server using Streamable HTTP. There is nothing to install or run locally, and this repository holds documentation and the MCP Registry manifest only. The server code is not open source.

EndpointAuthLimits
https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcpnonefree, 10 tool calls per IP per UTC day, no batch
https://b2b-email-domain-scorer.p.rapidapi.com/mcpX-RapidAPI-Key + X-RapidAPI-Host headerspaid per request via RapidAPI (free Basic plan available)

Official MCP Registry name: dev.workers.mohamed-bahaa53000.email-scorer/b2b-email-domain-scorer

Tools

  • score_email: action (keep / fix / review / drop), send_to, action_reason, plus verdict (business / free / role / disposable / risky / invalid / unknown), a 0-100 score, reasons, risk, is_disposable / is_free / is_role / accepts_mail flags, MX and mail provider, and a typo suggestion (gmial.com -> gmail.com). deep=true adds SPF/DMARC. No mail is sent.
  • score_domain: MX records, mail provider (Google Workspace, Microsoft 365, ...), free/disposable flags, SPF/DMARC for a company domain, URL or email.
  • score_batch: clean a list in one call and get send_list plus action counts (paid endpoint only).

Use cases

  • Lead-gen and SDR agents: drop disposable and free-mail signups and flag role accounts (info@, sales@) before outreach.
  • Fix typo domains in form signups before sending.
  • Qualify a company domain: does it receive mail, and on which provider?

Connect

json
{  "mcpServers": {    "email-scorer": {      "url": "https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp"    }  }}

Paid / production (RapidAPI):

json
{  "mcpServers": {    "email-scorer": {      "url": "https://b2b-email-domain-scorer.p.rapidapi.com/mcp",      "headers": {        "X-RapidAPI-Key": "YOUR_RAPIDAPI_KEY",        "X-RapidAPI-Host": "b2b-email-domain-scorer.p.rapidapi.com"      }    }  }}

For clients that only support stdio: npx -y mcp-remote https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp

Notes

  • Stateless. Emails aren't stored beyond standard request logs, and the server never sends SMTP probes.
  • Scores are heuristics for lead quality, not a deliverability guarantee.

Source: README.md at commit b30c25f

Tools

2

score_email

Score an email address

Decide what to do with one lead email: action keep / fix (with the corrected address in send_to) / review / drop, plus a plain-English action_reason. Also returns verdict business / free / role / disposable / risky / invalid / unknown, a 0-100 score, reasons, MX + mail provider, typo suggestion (gmial.com -> gmail.com). Set deep=true to add SPF/DMARC checks. No mail is sent.

Parametersdnsdeepemailrequired

score_domain

Check a company domain

Check a company domain (or URL / email): MX records, mail provider (Google Workspace, Microsoft 365, ...), free/disposable flags, and SPF/DMARC. Useful before outreach or when qualifying a lead's company.

Parametersdeepdomainrequired

Version history

3
  1. v1.2.1LatestOct 18, 2026
  2. v1.2.0Oct 18, 2026
  3. v1.1.0Oct 18, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.