io.github.fahassan00/bounceprotect
NPM · @BOUNCEPROTECT/MCP · SCANNED AUG 3
Email validation and SMTP verification for Claude Desktop, Cursor, and Claude Code.
Available components
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 62 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 114 tokens (~38/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @bounceprotect/mcp
claude mcp add fahassan00-bounceprotect -- npx -y @bounceprotect/mcp
codex mcp add fahassan00-bounceprotect -- npx -y @bounceprotect/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fahassan00-bounceprotect": {
"type": "local",
"command": [
"npx",
"-y",
"@bounceprotect/mcp"
],
"enabled": true
}
}
} openclaw mcp add fahassan00-bounceprotect --command npx --arg -y --arg @bounceprotect/mcp
mcp_servers:
fahassan00-bounceprotect:
command: "npx"
args: ["-y", "@bounceprotect/mcp"] {
"mcpServers": {
"fahassan00-bounceprotect": {
"command": "npx",
"args": [
"-y",
"@bounceprotect/mcp"
]
}
}
} 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.
- 2 Aug 26 +15
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −39
- Install scripts: pass → unverified ▼ security
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- License: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
- 28 Jul 26 +53
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 27 Jul 26 25
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 3 Aug 2026 · Analysed npm/@bounceprotect/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
check_credits ~17
Check your remaining BounceProtect credit balance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate_email ~44
Validate a single email address. Returns deliverability status, spam risk score, SMTP verification result, and a send recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to validate |
No output schema declared.
No examples provided.
validate_emails_bulk ~53
Validate up to 100 email addresses at once. Returns validation results for each email including status, recommendation, and deliverability signals.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Array of email addresses to validate (maximum 100) |
No output schema declared.
No examples provided.