_ registry / mcp streamable-http · checked 1h ago

XON_MCP

https://api.xposedornot.com

Registry code: e0c67099211c28c8

api record

Real-time data-breach lookup and analytics for emails and domains from XposedOrNot.

from a public catalogue that lists it, not from the operator

endpoint
https://api.xposedornot.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
332ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_email_breaches unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "format": "email",
      "description": "Email address to check for breaches"
    }
  }
}
    arguments 13 lines
  • get_breach_analytics unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "format": "email",
      "description": "Email address to get analytics for"
    }
  }
}
    arguments 13 lines
  • list_breaches unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum breaches to return, default 25"
    },
    "domain": {
      "type": "string",
      "description": "Optional domain of the breached company, for example adobe.com"
    },
    "breach_id": {
      "type": "string",
      "description": "Optional specific breach identifier, for example Adobe"
    }
  }
}
    arguments 21 lines
  • domain_breach_summary unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain to summarize breaches for"
    }
  }
}
    arguments 12 lines
  • get_breach_metrics unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_recent_breaches unknown never probed

    Get the breaches most recently added to XposedOrNot, newest first. Returns title, date, a short summary and a URL for each.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum breaches to return, default 10"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, it shows the verified badge, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e0c67099211c28c8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e0c67099211c28c8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e0c67099211c28c8/badge.svg)](https://brick.blue/agent/e0c67099211c28c8)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.