Breach402 Owner Protection
Server Details
Protect owners with private checks across 13.3B+ breach records and prioritized defenses.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.5/5 across 5 of 6 tools scored. Lowest: 2.9/5.
Each tool has a clearly distinct purpose covering different stages of the owner verification and breach check workflow. No two tools overlap in function, making misselection unlikely.
All tool names follow a consistent verb_noun snake_case pattern, with clear and descriptive terms like create, get, prepare, revoke, and verify.
With 6 tools, the server is well-scoped for its purpose, covering the essential operations without unnecessary bloat or gaps.
The tool set covers the full email verification lifecycle and the paid breach check process, though there is a minor gap: after preparing the paid check, there is no explicit tool to confirm the scan completion beyond retrieving the report.
Available Tools
6 toolscreate_owner_email_verificationInspect
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 | Required | Description | Default |
|---|---|---|---|
| Yes | The owner-controlled email address to verify. | ||
| agent_wallet | No | Optional agent-supplied Solana address displayed as an unverified claim. It is not proof of wallet control. |
get_breach_reportInspect
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 | Required | Description | Default |
|---|---|---|---|
| check_id | Yes | ||
| report_token | Yes |
get_owner_email_verification_statusInspect
Poll an email-verification request. After owner approval, this returns a one-time scan token for the free payment-preparation step.
| Name | Required | Description | Default |
|---|---|---|---|
| poll_token | Yes | ||
| enrollment_id | Yes |
prepare_paid_breach_checkInspect
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 | Required | Description | Default |
|---|---|---|---|
| scan_token | Yes | One-time token returned after owner verification. | |
| idempotency_key | Yes | 8-128 character unique key generated by the agent. |
revoke_owner_email_authorizationInspect
Revoke a pending or verified one-time owner authorization before it is consumed by a paid check.
| Name | Required | Description | Default |
|---|---|---|---|
| poll_token | Yes | ||
| enrollment_id | Yes |
verify_owner_email_codeInspect
Submit the one-time code that the owner received by email. The code is bound to the original agent enrollment.
| Name | Required | Description | Default |
|---|---|---|---|
| poll_token | Yes | ||
| enrollment_id | Yes | ||
| verification_code | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!