B2B Email & Domain Scorer
REMOTE · EMAIL-SCORER.MOHAMED-BAHAA53000.WORKERS.DEV · 2 COMPONENTS
Lead email decisions: keep / fix typo / review / drop, plus a ready-to-send list. Paid: RapidAPI
Last scanned (13 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 22 Oct 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 269 tokens (~134/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 18 Oct 26 65
First indexed and scored.
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 22 Oct 2026 · Probed https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mohamed-bahaa53000.workers.dev | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 47240052cd2434ee13434869a0b4b51b |
| SANs: mohamed-bahaa53000.workers.dev, *.mohamed-bahaa53000.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of email-scorer.mohamed-bahaa53000.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp | Verified | 200 | |
| http (plaintext) | http://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp | Inconclusive | 405 |
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 →
score_domain Check a company domain ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Include SPF/DMARC |
| domain | string | yes | – |
No output schema declared.
No examples provided.
score_email Score an email address ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Also check SPF and DMARC records |
| dns | boolean | – | Set false for offline syntax/list checks only |
| string | yes | Email address |
No output schema declared.
No examples provided.
How do I install the B2B Email & Domain Scorer MCP server?
B2B Email & Domain Scorer is a hosted endpoint at https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · email-scorer.mohamed-bahaa53000.workers.dev
claude mcp add --transport http dev-workers-mohamed-bahaa53000-email-scorer-b2b- 'https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp'
What is the B2B Email & Domain Scorer MCP server?
B2B Email & Domain Scorer is an MCP server listed in the public MCP registry as dev.workers.mohamed-bahaa53000.email-scorer/b2b-email-domai…. Lead email decisions: keep / fix typo / review / drop, plus a ready-to-send list. Paid: RapidAPI. This page covers its hosted endpoint (https://email-scorer.mohamed-bahaa53000.workers.dev/demo/mcp).
Is the B2B Email & Domain Scorer MCP server safe to use?
B2B Email & Domain Scorer scores 67 out of 100 on VerifyMCP. 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 B2B Email & Domain Scorer MCP server expose?
B2B Email & Domain Scorer exposes 2 tools: score_email, score_domain. Their descriptions and schemas cost roughly 211 tokens of context every time the server is loaded.
Does the B2B Email & Domain Scorer MCP server require authentication?
No. We connected to B2B Email & Domain Scorer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the B2B Email & Domain Scorer MCP server still maintained?
B2B Email & Domain Scorer is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.