Skip to content

BounceLayer Email Verification MCP server

com.bouncelayer/mcpbouncelayer.comstreamable-httpv1.0.2Scanned

Check if an email address is real before you send, with a plain-English reason for every result.

9 tools: 1 can delete or cancel things, 4 change things and 4 only read.

Tools: 1 delete, 0 irreversible, 4 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BounceLayer Email Verification MCP server can do

The BounceLayer Email Verification MCP server is published by bouncelayer.com, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (1 tool: cancel_bulk_job) and create or change data (4 tools: verify_email, submit_bulk_verification, verify_email_demo and create_agent_account). 4 tools only read.

1 tool reads private data (get_api_discovery); 2 tools bring in text other people can write (verify_email and submit_bulk_verification); 1 tool can send data out of your system (submit_bulk_verification). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • cancel_bulk_jobCancel a pending or processing bulk job and release any reserved credits.No findings

    Why it is in this group

    • The name "cancel_bulk_job" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancel a pending or processing bulk job and release any reserved credits. Requires an API key.

    Annotations the server declares

    • title: Cancel a bulk job
    • readOnlyHint: false
    • destructiveHint: true
Changes things 4Claude Code: ask
  • create_agent_accountGet your own BounceLayer API key without a person signing up first.No findings

    Why it is in this group

    • The name "create_agent_account" says "create": a word for a change.
    Description, as the server wrote it
    Get your own BounceLayer API key without a person signing up first. No API key needed. Returns an API key with a few free credits and a claim_url. Use the key in the 'X-API-Key' header (reconnect this MCP server with it). Give claim_url to the person you work for: when they open it and set an email and password, the account becomes theirs and gets the full free monthly checks. The key and claim link are shown only once. Limited per network and site-wide.

    Annotations the server declares

    • title: Create an agent account and API key
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • submit_bulk_verificationQueue a list of emails for asynchronous verification.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "submit_bulk_verification" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Queue a list of emails for asynchronous verification. Reserves up to N credits (final charge settles on completion). Poll get_bulk_job for status and results. Optionally provide webhook_url for a completion callback. Requires an API key. Returns {job_id, status, total_emails, credits_reserved}.

    Annotations the server declares

    • title: Submit a bulk verification job
    • readOnlyHint: false
    • openWorldHint: true
  • verify_emailVerify a single email's deliverability (syntax, DNS/MX, SMTP mailbox, disposable / role / catch-all detection, confidence score).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Verify a single email's deliverability (syntax, DNS/MX, SMTP mailbox, disposable / role / catch-all detection, confidence score). Costs 1 credit for a billable result (valid/invalid/catch_all/disposable/do_not_mail), whether fresh or served from cache. `unknown` results are free. Requires an API key. Returns {success, credits_used, result}.

    Annotations the server declares

    • title: Verify an email address
    • readOnlyHint: false
    • openWorldHint: true
  • verify_email_demoCheck one email WITHOUT an API key: format, common typos, throwaway domains, role and free-provider addresses, and whether the domain has mail servers (MX).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check one email WITHOUT an API key: format, common typos, throwaway domains, role and free-provider addresses, and whether the domain has mail servers (MX). It never contacts the mailbox, so a good address comes back "unknown", not "valid"; use verify_email for a real answer. Limited per IP. Returns {success, credits_used: 0, result}.

    Annotations the server declares

    • title: Demo email validation (no API key)
    • readOnlyHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • get_api_discoveryReturn BounceLayer's machine-readable discovery URLs (OpenAPI, docs, auth.md, well-known metadata).Reads private dataNo findings

    Why it is in this group

    • The name "get_api_discovery" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "doc": it reads documents.
    Description, as the server wrote it
    Return BounceLayer's machine-readable discovery URLs (OpenAPI, docs, auth.md, well-known metadata). No API key required.

    Annotations the server declares

    • title: Get BounceLayer discovery URLs
    • readOnlyHint: true
    • openWorldHint: false
  • get_bulk_jobGet the status, progress, and (when complete) results of a bulk job by its job_id.No findings

    Why it is in this group

    • The name "get_bulk_job" says "get": a word for reading.
    Description, as the server wrote it
    Get the status, progress, and (when complete) results of a bulk job by its job_id. Requires an API key.

    Annotations the server declares

    • title: Get a bulk job's status and results
    • readOnlyHint: true
  • get_credit_balanceReturn your current credit balance and lifetime usage.No findings

    Why it is in this group

    • The name "get_credit_balance" says "get": a word for reading.
    Description, as the server wrote it
    Return your current credit balance and lifetime usage. Requires an API key.

    Annotations the server declares

    • title: Get your credit balance
    • readOnlyHint: true
  • list_bulk_jobsList your recent bulk verification jobs (paginated, newest first).No findings

    Why it is in this group

    • The name "list_bulk_jobs" says "list": a word for reading.
    Description, as the server wrote it
    List your recent bulk verification jobs (paginated, newest first). Optionally filter by status. Requires an API key.

    Annotations the server declares

    • title: List your bulk jobs
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__bouncelayer__submit_bulk_verification"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.bouncelayer.com/mcp/: tools/list returned 9 tools to an anonymous client, including cancel_bulk_job (destructive), verify_email (write), submit_bulk_verification (write), verify_email_demo (write), create_agent_account (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http bouncelayer https://api.bouncelayer.com/mcp/
claude mcp add --transport http bouncelayer https://api.bouncelayer.com/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bouncelayer__get_bulk_job",
      "mcp__bouncelayer__list_bulk_jobs",
      "mcp__bouncelayer__get_credit_balance",
      "mcp__bouncelayer__get_api_discovery"
    ],
    "ask": [
      "mcp__bouncelayer__verify_email",
      "mcp__bouncelayer__submit_bulk_verification",
      "mcp__bouncelayer__verify_email_demo",
      "mcp__bouncelayer__create_agent_account"
    ],
    "deny": [
      "mcp__bouncelayer__cancel_bulk_job"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bouncelayer. Review it before you use it.

Capability tags behind 3 rules
  • mcp__bouncelayer__verify_email untrusted-input
  • mcp__bouncelayer__submit_bulk_verification untrusted-input, outbound
  • mcp__bouncelayer__get_api_discovery private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.bouncelayer/mcp/verify?hash=5a53546cb6590fc21f1fdc0bd6600f85cbcde0796c7701ebd6d8b49bfc7d5692" | jq -e '.changed == false'

Pinned hash 5a53546cb659, from Nov 21, 2026, 00:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.bouncelayer/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.bouncelayer/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.bouncelayer/mcp.svg)](https://radar.anlyon.com/servers/com.bouncelayer/mcp)

Source: MCP Registry. Synced Nov 6, 2026, 22:17 UTC.

BounceLayer Email Verification MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BounceLayer Email Verification MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BounceLayer Email Verification MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_bulk_job.

Can the BounceLayer Email Verification MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BounceLayer Email Verification MCP server have?

9 tools: 1 destructive, 4 write, 4 read. cancel_bulk_job, verify_email, submit_bulk_verification, verify_email_demo, create_agent_account, get_bulk_job, list_bulk_jobs, get_credit_balance and 1 more.

Does the BounceLayer Email Verification MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BounceLayer Email Verification MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): submit_bulk_verification.

Has the BounceLayer Email Verification MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.