Breach402 — Email Data-Breach Check
REMOTE · BREACH402.BMCXIV.COM
Data-breach & credential-exposure check for one owner-approved email. $1 USDC on Solana (x402).
Available components
Last scanned (3 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
Recent critical change
Authorization (19 Oct 2026). See the changelog before you install this server.
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 → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (revoke_owner_email_authorization). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 837 tokens (~64/item across 13 items; 8 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 19 Oct 26 +58
- Authorization: unverified → fail ▼ critical
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 8 Oct 26 −58
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 5 Oct 26 0
- Server version: 0.1.5 → 0.1.6 functional
- 28 Sept 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
- 25 Sept 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 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
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 5 Nov 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=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6e7b631f07c0822914665ca2113571cf1a1 |
| SANs: *.bmcxiv.com, bmcxiv.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
Background: What to check on a remote MCP endpoint →
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=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_owner_security_need Assess Owner Security Need ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | string | yes | Non-identifying description of the owner's security situation. Email addresses are rejected. |
Structured output declared, but exposes no named fields.
No examples provided.
create_owner_email_verification Start 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_wallet | string | – | Optional agent-supplied Solana address displayed as an unverified claim. It is not proof of wallet control. |
| string | yes | The owner-controlled email address to verify. |
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Masked owner email address. | |
| enrollment_id | string | yes | Unique identifier for this verification enrollment. |
| next_step | string | yes | Safe next action for the requesting agent. |
| poll_token | string | yes | Private bearer capability for polling or revoking this enrollment. |
| status | string | yes | Current enrollment state. |
| status_url | string | yes | HTTP endpoint for enrollment status. |
| verification_expires_at | string | yes | Time when owner approval expires. |
| verification_methods | array | yes | Owner approval methods offered. |
No examples provided.
get_breach_report Get Private 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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | Paid-check identifier returned after successful x402 settlement. |
| report_token | string | yes | Private bearer capability returned with the paid-check receipt. |
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | Paid-check identifier. |
| completed_at | string|null | – | Time when provider processing completed. |
| created_at | string|null | – | Time when the check was created. |
| error | object | – | Safe failure details, present only when the scan failed. |
| report | object | – | Complete private report, present only when the scan is complete. |
| report_expires_at | string | yes | Time when the encrypted report is purged. |
| started_at | string|null | – | Time when provider processing began. |
| status | string | yes | Current scan state. |
No examples provided.
get_owner_email_verification_status Check Owner Verification Status ~68
Poll an email-verification request. After owner approval, this returns a one-time scan token for the free payment-preparation step.
| Name | Type | Req | Description |
|---|---|---|---|
| enrollment_id | string | yes | Enrollment identifier returned when verification was started. |
| poll_token | string | yes | Private polling capability returned with the enrollment. |
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Masked owner email address. | |
| enrollment_id | string | yes | Verification enrollment identifier. |
| next_step | string | – | Safe next action for the requesting agent. |
| scan_token | string | – | Private one-time scan authorization, present only after owner approval. |
| status | string | yes | Current enrollment state. |
| verification_expires_at | string | – | Time when owner approval expires. |
No examples provided.
prepare_paid_breach_check 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.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | 8-128 character unique key generated by the agent. |
| scan_token | string | yes | One-time token returned after owner verification. |
| Name | Type | Req | Description |
|---|---|---|---|
| already_paid | boolean | – | Whether this idempotent request already produced a paid check. |
| asset | string | – | Settlement asset. |
| body | object | – | Exact JSON body for the protected request. |
| check | object | – | Existing paid-check receipt when already paid. |
| expires_at | string | – | Time when the prepared payment request expires. |
| headers | object | – | Required HTTP headers, including the idempotency key. |
| instruction | string | – | Payment and retry instructions for the customer agent. |
| method | string | – | HTTP method for the protected request. |
| network | string | – | Solana network used for settlement. |
| payment_ticket | string | – | Private signed capability for submitting the protected x402 request. |
| payment_ticket_id | string | – | Identifier for the reserved payment attempt. |
| price | string | – | USDC price for the owner-approved scan. |
| url | string | – | Protected endpoint that returns the x402 payment requirement. |
No examples provided.
preview_synthetic_breach_report Preview Synthetic Breach Report ~46
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
revoke_owner_email_authorization Revoke Owner Authorization ~61
Revoke a pending or verified one-time owner authorization before it is consumed by a paid check.
| Name | Type | Req | Description |
|---|---|---|---|
| enrollment_id | string | yes | Enrollment identifier whose authorization should be revoked. |
| poll_token | string | yes | Private polling capability proving control of the enrollment. |
| Name | Type | Req | Description |
|---|---|---|---|
| enrollment_id | string | yes | Revoked verification enrollment identifier. |
| status | string | yes | Final enrollment state. |
No examples provided.
verify_owner_email_code 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.
| Name | Type | Req | Description |
|---|---|---|---|
| enrollment_id | string | yes | Enrollment identifier returned when verification was started. |
| poll_token | string | yes | Private polling capability returned with the enrollment. |
| verification_code | string | yes | One-time code supplied directly by the verified owner. |
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Masked owner email address. | |
| enrollment_id | string | yes | Verification enrollment identifier. |
| next_step | string | – | Safe next action for the requesting agent. |
| scan_token | string | yes | Private one-time authorization for preparing the paid scan. |
| status | string | yes | Confirmed owner-verification state. |
No examples provided.
How do I install the Breach402 — Email Data-Breach Check MCP server?
Breach402 — Email Data-Breach Check is a hosted endpoint at https://breach402.bmcxiv.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · breach402.bmcxiv.com
claude mcp add --transport http com-bmcxiv-breach402-owner-protection 'https://breach402.bmcxiv.com/mcp'
What is the Breach402 — Email Data-Breach Check MCP server?
Breach402 — Email Data-Breach Check is an MCP server listed in the public MCP registry as com.bmcxiv/breach402-owner-protection. Data-breach & credential-exposure check for one owner-approved email. $1 USDC on Solana (x402). This page covers its hosted endpoint (https://breach402.bmcxiv.com/mcp).
Is the Breach402 — Email Data-Breach Check MCP server safe to use?
Breach402 — Email Data-Breach Check scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Breach402 — Email Data-Breach Check MCP server expose?
Breach402 — Email Data-Breach Check exposes 8 tools: assess_owner_security_need, preview_synthetic_breach_report, create_owner_email_verification, get_owner_email_verification_status, verify_owner_email_code, and 3 more. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.
Does the Breach402 — Email Data-Breach Check MCP server require authentication?
No. We connected to Breach402 — Email Data-Breach Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Breach402 — Email Data-Breach Check MCP server still maintained?
Breach402 — Email Data-Breach Check is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.