Skip to main content
Glama
xposedornot

xposedornot

by pipeworx-io

XposedOrNot

Free breach-exposure lookup by email address — which data breaches an email appears in, what data was exposed, and an overall risk score. No key required.

Part of Pipeworx — an MCP gateway connecting AI agents to 1867+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Complements the hibp pack: HIBP's per-email lookup requires a paid BYO subscription key; XposedOrNot's is free. For password checks use hibp (k-anonymity, the password never leaves the worker).

Tools

Tool

What it does

email_breaches

Fast check: list of breach names an email appears in, or breached: false.

email_breach_analytics

Full report: per-breach dates, records affected, exposed data classes, password risk, overall risk score, paste exposures.

Related MCP server: domain-security-mcp-server

Auth

None. XposedOrNot rate-limits per IP; a 429 surfaces with a retry hint.

Data sources

A breached: false result means absence from XposedOrNot's corpus, not proof the email was never compromised.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "xposedornot": {
      "url": "https://gateway.pipeworx.io/xposedornot/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/xposedornot/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1867+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/email_breaches \
  -H 'Content-Type: application/json' \
  -d '{"email":"test@example.com"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/email_breaches. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-xposedornot is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/xposedornot/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "xposedornot": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-xposedornot"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Xposedornot data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      Not graded
      maintenance
      Provides real-time threat intelligence including IP risk scores, CVE lookups, and malware hash analysis without requiring an API key. It enables users to monitor active threats, predict CISA KEV additions, and detect pre-attack infrastructure staging through natural language.
      8
      22 PyPI
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run domain-intelligence investigations through six free tools: sanctions screening, IP geolocation with VPN/Tor detection, email validation with breach status, company profiling, WHOIS and email-security scoring, and a single-call domain dossier.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to look up data breaches and leaked passwords, search NVD CVEs and the CISA KEV catalogue, and generate passive attack-surface reports for a domain covering security headers, TLS, email/DNS security, and CT-log subdomains. All checks are read-only and passive, using only public third-party data sources.
      10
      MIT