XposedOrNot Breach Intelligence
REMOTE · API.XPOSEDORNOT.COM · SCANNED OCT 5
Real-time data-breach lookup and analytics for emails and domains from XposedOrNot.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 381 tokens (~63/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the XposedOrNot Breach Intelligence MCP server?
XposedOrNot Breach Intelligence is a hosted endpoint at https://api.xposedornot.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 · api.xposedornot.com
claude mcp add --transport http com-xposedornot-xposedornot 'https://api.xposedornot.com/mcp'
{
"mcpServers": {
"com-xposedornot-xposedornot": {
"url": "https://api.xposedornot.com/mcp"
}
}
} {
"servers": {
"com-xposedornot-xposedornot": {
"type": "http",
"url": "https://api.xposedornot.com/mcp"
}
}
} [mcp_servers.com-xposedornot-xposedornot] url = "https://api.xposedornot.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-xposedornot-xposedornot": {
"type": "remote",
"url": "https://api.xposedornot.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-xposedornot-xposedornot --url 'https://api.xposedornot.com/mcp' --transport streamable-http
mcp_servers:
com-xposedornot-xposedornot:
url: "https://api.xposedornot.com/mcp" {
"McpServers": {
"com-xposedornot-xposedornot": {
"Transport": "http",
"Url": "https://api.xposedornot.com/mcp"
}
}
} assistant mcp add com-xposedornot-xposedornot -t streamable-http -u 'https://api.xposedornot.com/mcp'
{
"mcpServers": {
"com-xposedornot-xposedornot": {
"type": "http",
"url": "https://api.xposedornot.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 5 Oct 26 +38
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 3 Oct 26 36
First indexed and scored.
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 Oct 2026 · Probed https://api.xposedornot.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=xposedornot.com | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 755e5e8b49e23ac10e9f3c66f3b9b64b |
| SANs: xposedornot.com, *.xposedornot.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.xposedornot.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| xposedornot.com. | present | 2371 | 13 | Verified |
| api.xposedornot.com. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';script-src 'self' https://cdnjs.cloudflare.com https://maxcdn.bootstrapcdn.com https://*.cloudflareinsights.com https://*.googletagmanager.com https://*.hotjar.com;style-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com https://fonts.googleapis.com https://xposedornot.com https://maxcdn.bootstrapcdn.com https://*.hotjar.com;img-src 'self' https://xposedornot.com https://fastapi.tiangolo.com data: https://*.google-analytics.com https://*.googletagmanager.com https://*.hotjar.com;font-src 'self' https://fonts.gstatic.com https://cdnjs.cloudflare.com https://*.hotjar.com;object-src 'none';base-uri 'self';connect-src 'self' https://xposedornot.com https://api.xposedornot.com https://cdnjs.cloudflare.com https://maxcdn.bootstrapcdn.com https://*.cloudflareinsights.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.hotjar.com https://*.hotjar.io wss://*.hotjar.com;frame-src 'self' https://*.hotjar.com;worker-src 'self' blob:; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), microphone=(), midi=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.xposedornot.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.xposedornot.com/mcp | HTTPS enforced | 301 | https://api.xposedornot.com/mcp |
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 →
check_email_breaches Check Email for Breaches ~55
Check whether an email address appears in the XposedOrNot index of known public data breaches. Returns the list of breach names only. Never returns passwords.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to check for breaches |
No output schema declared.
No examples provided.
domain_breach_summary Summarize Domain Breach Exposure ~60
Get an aggregate breach summary for a domain, including the number of breaches, affected email accounts, pastes, and the most recent breach date. Returns only counts, not individual email addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to summarize breaches for |
No output schema declared.
No examples provided.
get_breach_analytics Get Email Breach Analytics ~65
Get a detailed breach history for one email address: the breaches it appeared in with dates and descriptions, exposure broken down by industry and by year, risk scoring, and any paste exposure. Never returns passwords.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to get analytics for |
No output schema declared.
No examples provided.
get_breach_metrics Get Breach Index Metrics ~43
Get system-wide breach statistics: total breaches and records indexed, breaches per year and industry, the largest and most recent breaches, and when the latest breach was added.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_recent_breaches Get Recent Breaches ~55
Get the breaches most recently added to XposedOrNot, newest first. Returns title, date, a short summary and a URL for each.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum breaches to return, default 10 |
No output schema declared.
No examples provided.
list_breaches List Indexed Breaches ~103
List breaches in the XposedOrNot catalog, optionally filtered by the breached company domain or by a specific breach ID. Returns breach name, date, industry, record count, categories of data exposed and a reference URL.
| Name | Type | Req | Description |
|---|---|---|---|
| breach_id | string | – | Optional specific breach identifier, for example Adobe |
| domain | string | – | Optional domain of the breached company, for example adobe.com |
| limit | integer | – | Maximum breaches to return, default 25 |
No output schema declared.
No examples provided.
What is the XposedOrNot Breach Intelligence MCP server?
XposedOrNot Breach Intelligence is an MCP server listed in the public MCP registry as com.xposedornot/xposedornot. Real-time data-breach lookup and analytics for emails and domains from XposedOrNot. This page covers its hosted endpoint (https://api.xposedornot.com/mcp).
Is the XposedOrNot Breach Intelligence MCP server safe to use?
XposedOrNot Breach Intelligence scores 74 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 XposedOrNot Breach Intelligence MCP server expose?
XposedOrNot Breach Intelligence exposes 6 tools: check_email_breaches, get_breach_analytics, list_breaches, domain_breach_summary, get_breach_metrics, get_recent_breaches. Their descriptions and schemas cost roughly 381 tokens of context every time the server is loaded.
Does the XposedOrNot Breach Intelligence MCP server require authentication?
No. We connected to XposedOrNot Breach Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the XposedOrNot Breach Intelligence MCP server still maintained?
XposedOrNot Breach Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.