Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Breach402 Owner Protection

REMOTE · BREACH402.BMCXIV.COM · SCANNED AUG 3

Protect owners with private checks across 13.3B+ breach records and prioritized defenses.

+6 this week 64 Trust /100

Recent critical change

Authorization (29 Jul 2026). See the changelog before you install this server.

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 623 tokens (~69/item across 9 items; 6 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · breach402.bmcxiv.com

# add to Claude Code
claude mcp add --transport http com-bmcxiv-breach402-owner-protection https://breach402.bmcxiv.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-bmcxiv-breach402-owner-protection]
url = "https://breach402.bmcxiv.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-bmcxiv-breach402-owner-protection": {
      "type": "remote",
      "url": "https://breach402.bmcxiv.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-bmcxiv-breach402-owner-protection --url https://breach402.bmcxiv.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-bmcxiv-breach402-owner-protection:
    url: "https://breach402.bmcxiv.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-bmcxiv-breach402-owner-protection": {
      "type": "http",
      "url": "https://breach402.bmcxiv.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1
    • Server version: 0.1.3 → 0.1.4 functional
  • 1 Aug 26 +1
    • Server version: 0.1.2 → 0.1.3 functional
  • 31 Jul 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Jul 26 +5
    • Authorization: unverified → fail critical
    • Tool “revoke_owner_email_authorization” is now declared destructive security
    • Schema quality: 61 → 69 functional
    • Tool coverage: 31% → 100% functional
    • Tool “get_breach_report” now declares an output schema functional
    • Tool “get_owner_email_verification_status” now declares an output schema functional
    • Tool “prepare_paid_breach_check” now declares an output schema functional
    • Tool “revoke_owner_email_authorization” now declares an output schema functional
    • Tool “verify_owner_email_code” now declares an output schema functional
    • Tool “create_owner_email_verification” now declares an output schema functional
    • First check of Tool coverage: 100 functional
    • “get_breach_report” reworded the description of “check_id” cosmetic
    • “get_breach_report” reworded the description of “report_token” cosmetic
    • “get_owner_email_verification_status” reworded the description of “enrollment_id” cosmetic
    • “get_owner_email_verification_status” reworded the description of “poll_token” cosmetic
    • “revoke_owner_email_authorization” reworded the description of “enrollment_id” cosmetic
    • “revoke_owner_email_authorization” reworded the description of “poll_token” cosmetic
    • “verify_owner_email_code” reworded the description of “enrollment_id” cosmetic
    • “verify_owner_email_code” reworded the description of “poll_token” cosmetic
    • “verify_owner_email_code” reworded the description of “verification_code” cosmetic
    • Tool “create_owner_email_verification” changed its title: Start Owner Email Verification cosmetic
    • Tool “get_breach_report” changed its title: Get Private Breach Report cosmetic
    • Tool “get_owner_email_verification_status” changed its title: Check Owner Verification Status cosmetic
    • Tool “revoke_owner_email_authorization” changed its title: Revoke Owner Authorization cosmetic
    • Tool “verify_owner_email_code” changed its title: Verify Owner Email Code cosmetic
    • Tool “prepare_paid_breach_check” changed its title: Prepare Paid Breach Check cosmetic
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 58

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://breach402.bmcxiv.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bmcxiv.com CN=YE1,O=Let's Encrypt,C=US 28 Jul 2026 26 Oct 2026 ECDSA 256 ECDSA-SHA384 66b8cbcd82d4dc9b387fc9c06c7b6090159
SANs: *.bmcxiv.com, bmcxiv.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of breach402.bmcxiv.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
bmcxiv.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=(), payment=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://breach402.bmcxiv.com/mcp Verified 200
http (plaintext) http://breach402.bmcxiv.com/mcp Inconclusive 405
MCP tools — 6 exposed · ~469 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
create_owner_email_verification ~85

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.

NameTypeReqDescription
agent_walletstringOptional agent-supplied Solana address displayed as an unverified claim. It is not proof of wallet control.
emailstringyesThe owner-controlled email address to verify.
NameTypeReqDescription
emailstringyesMasked owner email address.
enrollment_idstringyesUnique identifier for this verification enrollment.
next_stepstringyesSafe next action for the requesting agent.
poll_tokenstringyesPrivate bearer capability for polling or revoking this enrollment.
statusstringyesCurrent enrollment state.
status_urlstringyesHTTP endpoint for enrollment status.
verification_expires_atstringyesTime when owner approval expires.
verification_methodsarrayyesOwner approval methods offered.

No examples provided.

get_breach_report ~95

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.

NameTypeReqDescription
check_idstringyesPaid-check identifier returned after successful x402 settlement.
report_tokenstringyesPrivate bearer capability returned with the paid-check receipt.
NameTypeReqDescription
check_idstringyesPaid-check identifier.
completed_atstring|nullTime when provider processing completed.
created_atstring|nullTime when the check was created.
errorobjectSafe failure details, present only when the scan failed.
reportobjectComplete private report, present only when the scan is complete.
report_expires_atstringyesTime when the encrypted report is purged.
started_atstring|nullTime when provider processing began.
statusstringyesCurrent scan state.

No examples provided.

get_owner_email_verification_status ~68

Poll an email-verification request. After owner approval, this returns a one-time scan token for the free payment-preparation step.

NameTypeReqDescription
enrollment_idstringyesEnrollment identifier returned when verification was started.
poll_tokenstringyesPrivate polling capability returned with the enrollment.
NameTypeReqDescription
emailstringyesMasked owner email address.
enrollment_idstringyesVerification enrollment identifier.
next_stepstringSafe next action for the requesting agent.
scan_tokenstringPrivate one-time scan authorization, present only after owner approval.
statusstringyesCurrent enrollment state.
verification_expires_atstringTime when owner approval expires.

No examples provided.

prepare_paid_breach_check ~81

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.

NameTypeReqDescription
idempotency_keystringyes8-128 character unique key generated by the agent.
scan_tokenstringyesOne-time token returned after owner verification.
NameTypeReqDescription
already_paidbooleanWhether this idempotent request already produced a paid check.
assetstringSettlement asset.
bodyobjectExact JSON body for the protected request.
checkobjectExisting paid-check receipt when already paid.
expires_atstringTime when the prepared payment request expires.
headersobjectRequired HTTP headers, including the idempotency key.
instructionstringPayment and retry instructions for the customer agent.
methodstringHTTP method for the protected request.
networkstringSolana network used for settlement.
payment_ticketstringPrivate signed capability for submitting the protected x402 request.
payment_ticket_idstringIdentifier for the reserved payment attempt.
pricestringUSDC price for the owner-approved scan.
urlstringProtected endpoint that returns the x402 payment requirement.

No examples provided.

revoke_owner_email_authorization ~61

Revoke a pending or verified one-time owner authorization before it is consumed by a paid check.

NameTypeReqDescription
enrollment_idstringyesEnrollment identifier whose authorization should be revoked.
poll_tokenstringyesPrivate polling capability proving control of the enrollment.
NameTypeReqDescription
enrollment_idstringyesRevoked verification enrollment identifier.
statusstringyesFinal enrollment state.

No examples provided.

verify_owner_email_code ~79

Submit the one-time code that the owner received by email. The code is bound to the original agent enrollment.

NameTypeReqDescription
enrollment_idstringyesEnrollment identifier returned when verification was started.
poll_tokenstringyesPrivate polling capability returned with the enrollment.
verification_codestringyesOne-time code supplied directly by the verified owner.
NameTypeReqDescription
emailstringyesMasked owner email address.
enrollment_idstringyesVerification enrollment identifier.
next_stepstringSafe next action for the requesting agent.
scan_tokenstringyesPrivate one-time authorization for preparing the paid scan.
statusstringyesConfirmed owner-verification state.

No examples provided.