Index / messaging

Breach402 — Email Data-Breach Check

com-bmcxiv-breach402-owner-protection declares 8 capabilities across 8 tools, with 3 critical issues.

49/100 exposureElevated

Manifest recorded 2026-10-21 from tools/list on https://breach402.bmcxiv.com/mcp, published in the official MCP registry as com.bmcxiv/breach402-owner-protection 0.1.6. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 8 tools

8 of 8 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 3 of 8 tools

3 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 1 of 8 tools

1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 8 tools

8 of 8 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 8 tools

8 of 8 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

low · uncapped-read · 5 of 8 tools

5 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

Tool	Read as	Basis
`assess_owner_security_need`	`read`	declared
`preview_synthetic_breach_report`	`read`	declared
`create_owner_email_verification`	`send`	inferred
`get_owner_email_verification_status`	`read`	declared
`verify_owner_email_code`	`read`	inferred
`prepare_paid_breach_check`	`pay`	inferred
`get_breach_report`	`read`	declared
`revoke_owner_email_authorization`	`destructive`	declared

Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.

Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.