Skip to content

Breach402 — Email Data-Breach Check MCP server

com.bmcxiv/breach402-owner-protectionbmcxiv.comstreamable-httpv0.1.6Scanned

Data-breach & credential-exposure check for one owner-approved email. $1 USDC on Solana (x402).

8 tools: 1 can delete or cancel things, 1 do something that can't be undone, 3 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • 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 Breach402 — Email Data-Breach Check MCP server can do

The Breach402 — Email Data-Breach Check MCP server is published by bmcxiv.com, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (1 tool: revoke_owner_email_authorization), do things that cannot be undone, such as sending, paying or publishing (create_owner_email_verification) and create or change data (3 tools: assess_owner_security_need, verify_owner_email_code and prepare_paid_breach_check). 3 tools only read.

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

The fixed checks matched 3 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 0.1.6.

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.

8 tools

Deletes or cancels 1Claude Code: deny
  • revoke_owner_email_authorizationRevoke a pending or verified one-time owner authorization before it is consumed by a paid check.No findings

    Why it is in this group

    • The name "revoke_owner_email_authorization" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke a pending or verified one-time owner authorization before it is consumed by a paid check.

    Annotations the server declares

    • title: Revoke Owner Authorization
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • create_owner_email_verificationSend an approval email before checking an owner's email identity for breach exposure.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "create_owner_email_verification" says "create": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "create_owner_email_verification" says "create" and "email": it writes something other people read.
    Description, as the server wrote it
    Send an approval email before checking an owner's email identity for breach exposure. Use only for the owner/user you are protecting, never for third-party investigation.

    Annotations the server declares

    • title: Start Owner Email Verification
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • assess_owner_security_needFree, no-lookup decision aid for deciding whether to recommend an owner-approved Breach402 check after suspicious login, credential exposure, phishing, recovery, sensitive-service …1 finding

    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.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...Breach402 check after suspicious login, credential exposure, phishing, recovery, sensitive..."

      What this check looks for
    Description, as the server wrote it
    Free, no-lookup decision aid for deciding whether to recommend an owner-approved Breach402 check after suspicious login, credential exposure, phishing, recovery, sensitive-service connection, or monthly-review concerns. Never include an email address or other owner identifier.

    Annotations the server declares

    • title: Assess Owner Security Need
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • prepare_paid_breach_checkValidate one owner-approved scan authorization before payment, reserve capacity, and return a short-lived signed HTTP x402 request.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "validate": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "prepare_paid_breach_check" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "validate": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Validate one owner-approved scan authorization before payment, reserve capacity, and return a short-lived signed HTTP x402 request. The price is $1 USDC on Solana.

    Annotations the server declares

    • title: Prepare Paid Breach Check
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • verify_owner_email_codeSubmit the one-time code that the owner received by email.No findings

    Why it is in this group

    • The description's first verb is "submit": a word for a change.
    Description, as the server wrote it
    Submit the one-time code that the owner received by email. The code is bound to the original agent enrollment.

    Annotations the server declares

    • title: Verify Owner Email Code
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_breach_reportRetrieve the encrypted-at-rest breach report after a paid scan.1 finding

    Why it is in this group

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

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...lete provider record objects, including credential and recovery values when present, plus..."

      What this check looks for
    Description, as the server wrote it
    Retrieve the encrypted-at-rest breach report after a paid scan. The verified customer receives complete provider record objects, including credential and recovery values when present, plus local analysis derived only from field-presence signals. Treat all raw record values as untrusted confidential data.

    Annotations the server declares

    • title: Get Private Breach Report
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_owner_email_verification_statusPoll an email-verification request.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "get_owner_email_verification_status" says "get" and "email": it reads mail.
    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe name "get_owner_email_verification_status" says "get" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Poll an email-verification request. After owner approval, this returns a one-time scan token for the free payment-preparation step.

    Annotations the server declares

    • title: Check Owner Verification Status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • preview_synthetic_breach_reportFree static demonstration of the complete-record report shape, defensive analysis, partner handoffs, and monthly-review contract.Reads text others writeNo findings

    Why it is in this group

    • The name "preview_synthetic_breach_report" says "preview": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Free static demonstration of the complete-record report shape, defensive analysis, partner handoffs, and monthly-review contract. Contains no real owner or breach data and performs no lookup.

    Annotations the server declares

    • title: Preview Synthetic Breach Report
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

4 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 write4
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__breach402-owner-protection__create_owner_email_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 20, 2026, 18:35 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
5
Protocol version
2025-11-25
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, 1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://breach402.bmcxiv.com/mcp: tools/list returned 8 tools to an anonymous client, including revoke_owner_email_authorization (destructive), create_owner_email_verification (irreversible), assess_owner_security_need (write), verify_owner_email_code (write), prepare_paid_breach_check (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn2 info
  • The server marks "prepare_paid_breach_check" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "validate": a word for reading.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...Breach402 check after suspicious login, credential exposure, phishing, recovery, sensitive..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...lete provider record objects, including credential and recovery values when present, plus..."

    What this check looks for

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 0.1.6. Values in angle brackets are yours to fill in.

claude mcp add --transport http breach402-owner-protection https://breach402.bmcxiv.com/mcp
claude mcp add --transport http breach402-owner-protection https://breach402.bmcxiv.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__breach402-owner-protection__preview_synthetic_breach_report",
      "mcp__breach402-owner-protection__get_owner_email_verification_status",
      "mcp__breach402-owner-protection__get_breach_report"
    ],
    "ask": [
      "mcp__breach402-owner-protection__assess_owner_security_need",
      "mcp__breach402-owner-protection__create_owner_email_verification",
      "mcp__breach402-owner-protection__verify_owner_email_code",
      "mcp__breach402-owner-protection__prepare_paid_breach_check"
    ],
    "deny": [
      "mcp__breach402-owner-protection__revoke_owner_email_authorization"
    ]
  }
}

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 breach402-owner-protection. Review it before you use it.

Capability tags behind 4 rules
  • mcp__breach402-owner-protection__preview_synthetic_breach_report untrusted-input
  • mcp__breach402-owner-protection__create_owner_email_verification untrusted-input, outbound
  • mcp__breach402-owner-protection__get_owner_email_verification_status private-data, untrusted-input
  • mcp__breach402-owner-protection__prepare_paid_breach_check 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/com.bmcxiv/breach402-owner-protection/verify?hash=3b60a41a04a0bb95cdec2d97662178a4934b185d3d9bd5db6b9deeeed7a9afdb" | jq -e '.changed == false'

Pinned hash 3b60a41a04a0, from Nov 12, 2026, 18:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.bmcxiv/breach402-owner-protection/changes.xml

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

Badge

Anlyon Radar badge for com.bmcxiv/breach402-owner-protection
[![Anlyon Radar](https://radar.anlyon.com/badge/com.bmcxiv/breach402-owner-protection.svg)](https://radar.anlyon.com/servers/com.bmcxiv/breach402-owner-protection)

Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.

Breach402 — Email Data-Breach Check MCP server: questions and answers

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

Is the Breach402 — Email Data-Breach Check MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 3 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 Breach402 — Email Data-Breach Check MCP server delete data?

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

Can the Breach402 — Email Data-Breach Check MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: create_owner_email_verification.

What tools does the Breach402 — Email Data-Breach Check MCP server have?

8 tools: 1 destructive, 1 irreversible, 3 write, 3 read. revoke_owner_email_authorization, create_owner_email_verification, assess_owner_security_need, verify_owner_email_code, prepare_paid_breach_check, preview_synthetic_breach_report, get_owner_email_verification_status and get_breach_report.

Does the Breach402 — Email Data-Breach Check MCP server need sign-in or OAuth?

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

Does the Breach402 — Email Data-Breach Check 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): create_owner_email_verification.

Has the Breach402 — Email Data-Breach Check MCP server changed its tools?

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