com.bounceprotect.www/mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor exact implementation activity, MCP interface, permission and setup changes.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Email validation and SMTP checks

What we know

Email validation and SMTP verification for Claude Desktop, Cursor, and Claude Code. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Maintenance / activity evidence

npm exact package downloads 241 in 2026-09-09..2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Email addresses submitted to validation service; account/privacy and per-lookup fees depend on provider. Complete write authority is not verified.
Refer to first-party setup documentation; do not infer authorization from package existence.
Sensitive access: email lists and verification requests

Email addresses submitted to validation service; account/privacy and per-lookup fees depend on provider.
Public tracking suitability is not an installation safety audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 241 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @bounceprotect/mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T03:38:00Z.

All limitations / Review context

Has com.bounceprotect.www/mcp changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?

Limited editorial listing; known permission implications disclosed, no independently established publication blocker.

Email addresses submitted to validation service; account/privacy and per-lookup fees depend on provider.
Public tracking suitability is not an installation safety audit.
Refer to first-party setup documentation; do not infer authorization from package existence.
email lists and verification requests
Sensitive access: email lists and verification requests
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Upstream credential and permission scopes must be validated before runtime use.
Precise setup/auth/permissions not verified
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Dated package download count is usage signal, not necessarily a current maintenance release.

Original activity observations

npm exact package downloads 241 in 2026-09-09..2026-10-08

Technical identity

npm/@bounceprotect/mcp

Exact implementation source: https://www.npmjs.com/package/@bounceprotect/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@bounceprotect/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@bounceprotect/mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Retained node-template limitation; does not restrict the V3 npm launch: Exact server entrypoint in README is only /path/to/mcp-server/index.js placeholder; publisher npm README lacks verified package-to-path install steps.
BOUNCEPROTECT_API_KEY required; credits consumed by validation calls.
Publisher README config reproduced as MCP100 structured data; requires real credentials and may require separately installed or built server. Not runtime tested.
Prior reviewed safety note: List tools and use check_credits read-only; avoid validating actual email addresses in connectivity smoke check.
Prior reviewed safety note: Do not invent a one-line reversal command.
Direct npm README reviewed 2026-10-14; client registration still required.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.

Install / connect
Publisher instructions
Retained local-node template context; its restriction applies to that template, not the V3 package launch: Official README gives a Claude Desktop node-based local entrypoint, but does NOT document how to download/build /path/to/mcp-server/index.js from this npm package. Keep this as a conditional, non-copyable template, not an npx command.
publisher documented mcp stdio launch · Publisher instructions
npx -y @bounceprotect/mcp
Configure / authenticate
MCP100 setup guide
Add `npx -y @bounceprotect/mcp` to the MCP client with `BOUNCEPROTECT_API_KEY` in its environment.
claude desktop or cursor mcpServers json · Publisher instructions · Review before use
```
{
  "mcpServers": {
    "bounceprotect": {
      "args": [
        "/path/to/mcp-server/index.js"
      ],
      "command": "node",
      "env": {
        "BOUNCEPROTECT_API_KEY": "YOUR_KEY"
      }
    }
  }
}
```
Check connection
Suggested check
Use `check_credits` to check authenticated account status without consuming an email-verification credit.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `bounceprotect-mcp`, run `claude mcp remove bounceprotect-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove bounceprotect-mcp

Official Documentation & Sources

What it does

Email validation and SMTP verification for Claude Desktop, Cursor, and Claude Code. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Email validation and SMTP checks

Representative uses

Email validation and SMTP checks

Limitations

Email addresses submitted to validation service; account/privacy and per-lookup fees depend on provider.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Dated package download count is usage signal, not necessarily a current maintenance release.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.
Permissions: Email addresses submitted to validation service; account/privacy and per-lookup fees depend on provider.
Data handling: email lists and verification requests
Cost: Provider or usage fees possible; verify current pricing
Risk and cautions: Email addresses submitted to validation service; account/privacy and per-lookup fees depend on provider.

Access scope and cautions

Write actions: Not verified
Sensitive access: email lists and verification requests
Risk level: medium
Security notes: Email addresses submitted to validation service; account/privacy and per-lookup fees depend on provider. Public tracking suitability is not an installation safety audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Email validation and SMTP checks.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Installation command omitted unless verified or clearly package-specific; do not infer npx/uvx entrypoints. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Email addresses submitted to validation service; account/privacy and per-lookup fees depend on provider.

What data-handling boundary should I consider?

email lists and verification requests Recorded sensitive-access context: email lists and verification requests.

What limitations and risks should I check before use?

Email addresses submitted to validation service; account/privacy and per-lookup fees depend on provider. Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted. Dated package download count is usage signal, not necessarily a current maintenance release. Public tracking suitability is not an installation safety audit. Upstream credential and permission scopes must be validated before runtime use.