Skip to content

NoBounce Email Validation MCP server

io.github.notprathap/nobounce-mcpnotprathapstreamable-httpv1.0.1Scanned

Real-time single and bulk email validation (syntax, MX, 5,000+ disposable domains, SMTP).

2 tools: 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • 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 NoBounce Email Validation MCP server can do

The NoBounce Email Validation MCP server is published by the GitHub account notprathap. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools bring in text other people can write (validate_email and validate_emails_bulk).

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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.1.

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.

2 tools

Only reads 2Show 2 read-only tools
  • validate_emailValidate a single email address in real time using NoBounce API.Reads text others writeNo findings

    Why it is in this group

    • The name "validate_email" says "validate": a word for reading.

    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
    Validate a single email address in real time using NoBounce API. Checks RFC 5322 syntax, DNS MX records, 5,000+ disposable providers, role accounts, free webmail providers, typo suggestions, and optional SMTP handshake.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Validate Single Email Address
  • validate_emails_bulkValidate a batch of up to 1,000 email addresses in a single call using NoBounce API.Reads text others writeNo findings

    Why it is in this group

    • The name "validate_emails_bulk" says "validate": a word for reading.

    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
    Validate a batch of up to 1,000 email addresses in a single call using NoBounce API. Returns per-email validation results plus summary counts (valid, invalid, disposable, catch_all, unknown).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Validate Bulk Email Addresses

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
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 out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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 20, 2026, 19:08 UTC, unchanged since Oct 22, 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
0
Protocol version
2024-11-05
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

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.

  1. Tools2 changed.~2 changedView diff

Install

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

claude mcp add --transport http nobounce https://nobounceapi.com/mcp --header 'X-API-Key: <your-x-api-key>'
claude mcp add --transport http nobounce https://nobounceapi.com/mcp --header 'X-API-Key: <your-x-api-key>'

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__nobounce__validate_email",
      "mcp__nobounce__validate_emails_bulk"
    ],
    "ask": [],
    "deny": []
  }
}

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 nobounce. Review it before you use it.

Capability tags behind 2 rules
  • mcp__nobounce__validate_email untrusted-input
  • mcp__nobounce__validate_emails_bulk untrusted-input

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/io.github.notprathap/nobounce-mcp/verify?hash=f401b29d488f59a8b09306e76b326c765de4ece40dc3562711bd5c1f8875f7c5" | jq -e '.changed == false'

Pinned hash f401b29d488f, from Nov 12, 2026, 08:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.notprathap/nobounce-mcp/changes.xml

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

Badge

Anlyon Radar badge for io.github.notprathap/nobounce-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.notprathap/nobounce-mcp.svg)](https://radar.anlyon.com/servers/io.github.notprathap/nobounce-mcp)

Source: MCP Registry · repository. Synced Nov 12, 2026, 08:18 UTC.

NoBounce Email Validation MCP server: questions and answers

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

Is the NoBounce Email Validation MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the NoBounce Email Validation MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the NoBounce Email Validation 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 NoBounce Email Validation MCP server have?

2 tools: 2 read. validate_email and validate_emails_bulk.

Does the NoBounce Email Validation MCP server need sign-in or OAuth?

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

Does the NoBounce Email Validation MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the NoBounce Email Validation MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.