BounceLens Email Check
MCPB · BOUNCELENS-EMAIL-CHECK-1.0.0.MCPB
Check emails for typos, disposable domains and dead domains. Runs locally, no API key.
Available components
Last scanned (9 hours ago)
Scores higher than 92% of MCPB servers
Category CRM and Sales
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 Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 279 tokens (~139/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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +6
- Stability: unverified → 0.37 ▲ functional
- 3 Oct 26 48
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 18 Oct 2026 · Analysed mcpb/https://github.com/bouncelens/mcp-email-check/releases/download/v1.0.0/bouncelens-email-check-1.0.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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_email Check one email address ~139
Check one email address for bad syntax, typos in the domain (gmial.com → gmail.com), disposable/throwaway domains, role addresses (info@, sales@) and domains that do not exist or have no mail server. status is "invalid" (will bounce: bad syntax, domain does not exist, no mail server), "risky" (disposable domain, likely typo such as gmial.com, no MX record) or "unconfirmed" (format and domain OK; the mailbox itself is not checked). did_you_mean holds the corrected address for typos.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to check |
No output schema declared.
No examples provided.
check_emails Check a list of email addresses ~140
Check up to 500 email addresses at once (same checks as check_email, plus duplicates, counting Gmail dot and +tag variants as the same inbox). Returns a summary with counts and one result per address, in input order. status is "invalid" (will bounce: bad syntax, domain does not exist, no mail server), "risky" (disposable domain, likely typo such as gmial.com, no MX record) or "unconfirmed" (format and domain OK; the mailbox itself is not checked). did_you_mean holds the corrected address for typos.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Email addresses, at most 500 |
No output schema declared.
No examples provided.
How do I install the BounceLens Email Check MCP server?
BounceLens Email Check ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, f3541d57c8ddab9c03237eac6d087dfb187944fe8c4d2356fcd132fda7d1e350; the commands to do that are on this page. If it does not match, do not open it.
mcpb · bouncelens-email-check-1.0.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
f3541d57c8ddab9c03237eac6d087dfb187944fe8c4d2356fcd132fda7d1e350
macOS / Linux
echo "f3541d57c8ddab9c03237eac6d087dfb187944fe8c4d2356fcd132fda7d1e350 bouncelens-email-check-1.0.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\bouncelens-email-check-1.0.0.mcpb).Hash -eq "f3541d57c8ddab9c03237eac6d087dfb187944fe8c4d2356fcd132fda7d1e350"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the BounceLens Email Check MCP server?
BounceLens Email Check is an MCP server listed in the public MCP registry as io.github.akshaycu777-ui/bouncelens-email-check. Check emails for typos, disposable domains and dead domains. Runs locally, no API key. This page covers its MCPB bundle (https://github.com/bouncelens/mcp-email-check/releases/download/v1.0.0/bouncelens-email-check-1.0.0.mcpb).
Is the BounceLens Email Check MCP server safe to use?
BounceLens Email Check scores 55 out of 100 on VerifyMCP. 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 BounceLens Email Check MCP server expose?
BounceLens Email Check exposes 2 tools: check_email, check_emails. Their descriptions and schemas cost roughly 279 tokens of context every time the server is loaded.
What licence is the BounceLens Email Check MCP server under?
BounceLens Email Check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.