Breach402 — Email Data-Breach Check
com.bmcxiv/breach402-owner-protection · 0.1.6
Data-breach & credential-exposure check for one owner-approved email. $1 USDC on Solana (x402).
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 35 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://breach402.bmcxiv.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 8 tools.
- Protocol
- 2025-11-25
- Calls itself
- breach402 0.1.5
- Handshake time
- 246 ms
- HTTP status
- 200
The tools it lists (8, as of 6 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
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 connection, or monthly-review concerns. Never include an email address or other owner identifier.
preview_synthetic_breach_reportFree 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.
create_owner_email_verificationSend 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.
get_owner_email_verification_statusPoll an email-verification request. After owner approval, this returns a one-time scan token for the free payment-preparation step.
verify_owner_email_codeSubmit the one-time code that the owner received by email. The code is bound to the original agent enrollment.
prepare_paid_breach_checkValidate 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.
get_breach_reportRetrieve 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.bmcxiv/breach402-owner-protection, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 5 days ago. The registry entry