Alerts Bar MCP server

Which servers in the official MCP registry are Alerts Bar's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Alerts Bar

Whose server it is

Registry namebar.alerts/alertsbarverified in the MCP registry

The registry name sits under alerts.bar. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14

Stateanswerschecked 2026-10-14
Tools2
Server calls itselfalertsbar-mcp
Server version0.1.1
Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 656 ms.

Tools it offers2 tools · read 2026-10-14

exposure_counts_for_domain
Credential-exposure counters for a domain. Counts only - no credential values or per-account detail. Sources: known breaches, infostealer infections, unattributed heap of ULP (Url,Login,Password) bundles, stolen cookies. All figures are…
exposure_samples_for_domain
A small RANDOM sample of individual exposure records for a domain - metadata only, capped in number: up to 20 records per type (stealers_users, stealers_staff, heap_users, heap_staff, breaches). Cookies are not sampled - see cookies_* in…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "alertsbar": {
      "type": "http",
      "url": "https://mcp.alerts.bar/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.