XposedOrNot Breach Intelligence logo

XposedOrNot Breach Intelligence

Read-only MCP tools for checking email breaches, exploring breach data, and viewing domain and system-level exposure metrics.

Install XposedOrNot Breach Intelligence

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://api.xposedornot.com/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 10/29/2026, 1:17:06 AM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://api.xposedornot.com/mcp

Overview

XposedOrNot Breach Intelligence connects AI assistants to XposedOrNot’s breach database through a remote Streamable HTTP MCP endpoint. It exposes read-only tools for email breach checks, analytics, breach catalog searches, domain summaries, metrics, and recent breach activity without requiring MCP authentication. Reach for it when an agent needs to investigate known breach exposure without returning passwords.

Use cases

  • Check an email address against known breaches
  • Review detailed breach and paste exposure
  • Summarize known breaches for a domain
  • Inspect recent breach activity
  • Add breach metrics to a security investigation

Key features

  • Email breach lookups
  • Detailed breach analytics and risk scores
  • Breach catalog filtering
  • Domain breach summaries
  • System-wide and recent-breach metrics
  • Read-only Streamable HTTP MCP access

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 15d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars101Stargazers on the source repository.
Last commit1d agoMost recent push to the default branch.

How XposedOrNot Breach Intelligence works

What XposedOrNot Breach Intelligence does

XposedOrNot Breach Intelligence gives MCP-compatible AI clients access to breach intelligence from XposedOrNot. Its tools can check whether an email appears in known breaches, retrieve detailed exposure history, browse the breach catalog, summarize domain exposure, inspect overall breach metrics, and identify recently added breaches.

The service is designed for read-only investigation. The exposed tools do not return passwords, and the MCP connection does not require an API key or other authentication.

How it works

Connect an MCP client to https://api.xposedornot.com/mcp. The endpoint uses Streamable HTTP and accepts JSON-RPC 2.0 requests over HTTP POST. Clients can discover the available functions with the MCP tools/list method, then invoke individual tools as needed.

The MCP layer provides access to selected XposedOrNot API data, including email lookups, breach analytics, breach listings, domain summaries, aggregate metrics, and recent breach activity. It is intended for interactive agent workflows rather than making changes to breach records or account settings.

Setup and configuration

A compatible client can register the remote endpoint directly. For Claude Code, the connection command is:

Terminal
claude mcp add --transport http xposedornot https://api.xposedornot.com/mcp

The MCP service itself needs no API key. The underlying XposedOrNot API uses API keys for certain domain-monitoring operations, but the built-in MCP connection is described as unauthenticated. A machine-readable server card is available at https://api.xposedornot.com/.well-known/mcp/server-card.json.

To inspect the advertised tools manually, send a JSON-RPC request with Content-Type: application/json to the MCP endpoint and call tools/list.

Tools and capabilities

  • check_email_breaches checks whether an email address appears in known breaches.
  • get_breach_analytics returns detailed breach history, a risk score, and paste-exposure information for an email.
  • list_breaches browses the breach catalog and supports filtering by domain or breach ID.
  • domain_breach_summary provides aggregated breach counts for a domain.
  • get_breach_metrics returns system-wide breach statistics.
  • get_recent_breaches lists recently added breaches with the newest entries first.

These capabilities fit workflows such as triaging an email address, reviewing an organization’s known exposure, answering questions about breach activity, or adding breach context to a security investigation.

Limitations and notes

The service is read-only through MCP and does not provide password data. The underlying free API applies per-IP, per-endpoint rate limits. The documented limits include 25 requests per hour and 100 per day for email checks and analytics, and 50 per hour and 100 per day for the breach catalog. Requests that exceed a limit receive HTTP 429 responses with retry information.

Domain breach monitoring in the underlying API requires verified domain ownership and an API key obtained through the XposedOrNot web console. Commercial or higher-volume API access is offered separately through xonAPI+; those terms do not change the unauthenticated MCP connection described above.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about XposedOrNot Breach Intelligence

XposedOrNot Breach Intelligence is an MCP server that connects AI clients to XposedOrNot’s breach database. Its read-only tools check email exposure, return breach analytics, browse breach records, summarize domain exposure, report system metrics, and list recent breaches without requiring MCP authentication or returning passwords.

Add the remote Streamable HTTP endpoint `https://api.xposedornot.com/mcp` to an MCP-compatible client. Claude Code can use `claude mcp add --transport http xposedornot https://api.xposedornot.com/mcp`; other clients need their equivalent remote-server configuration.

Yes, Cursor is named as a supported client for the MCP service. Configure Cursor to connect to `https://api.xposedornot.com/mcp` using its remote MCP setup; the endpoint uses Streamable HTTP and does not require an API key.

No, the MCP connection requires no API key or authentication. The underlying API does require an API key for domain breach monitoring after domain ownership verification, but that requirement is separate from the built-in MCP endpoint.

The underlying API applies per-IP, per-endpoint limits. Email checks and analytics allow up to 2 requests per second, 25 per hour, and 100 per day; exceeding a limit produces HTTP 429 with retry timing.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewXposedOrNot Breach Intelligence AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/xposedornot-breach-intelligence?style=directory)](https://allmcps.com/mcp/xposedornot-breach-intelligence)
HTML Embed
<a href="https://allmcps.com/mcp/xposedornot-breach-intelligence"><img src="https://allmcps.com/api/badge/xposedornot-breach-intelligence?style=directory" alt="XposedOrNot Breach Intelligence on AllMCPs" /></a>