Breach402 — Email Data-Breach Check
by bmcxiv.com · remote · no sign-in to list tools · v0.1.6 · published by com.bmcxiv
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.
Scanned Oct 21, 2026
- Deletes or cancels1Claude Code: deny: see these tools
- Can't be undone1Claude Code: ask: see these tools
- Changes things3Claude Code: ask: see these tools
- Only reads3Claude Code: allow: see these tools
3 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http breach402-owner-protection https://breach402.bmcxiv.com/mcpFindings
Matches of fixed checks, with the text they matched.
The server marks "prepare_paid_breach_check" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "validate": a word for reading.
The description mentions "credential".
What this check looks forMatched text
description: "...Breach402 check after suspicious login, credential exposure, phishing, recovery, sensitive..."
The description mentions "credential".
What this check looks forMatched text
description: "...lete provider record objects, including credential and recovery values when present, plus..."
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
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.No 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.
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".
What this check looks forMatched text
description: "...Breach402 check after suspicious login, credential exposure, phishing, recovery, sensitive..."
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.1 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).
Findings
- Warn
The server marks "prepare_paid_breach_check" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "validate": a word for reading.
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 3Claude Code: allow
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".
What this check looks forMatched text
description: "...lete provider record objects, including credential and recovery values when present, plus..."
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.No findings
Why it is in this group
- The name "get_owner_email_verification_status" says "get": a word for reading.
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.No findings
Why it is in this group
- The name "preview_synthetic_breach_report" says "preview": a word for reading.
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.
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/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .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. It assumes the server is installed as breach402-owner-protection. Review it before you use it.