Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AlertsBar

REMOTE · MCP.ALERTS.BAR · SCANNED OCT 6

Domain exposures: breaches, infostealers, ULP heap, cookies. Counts and samples, free.

Available components

remote · mcp.alerts.bar 69
+36 this week 69 Trust /100
Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 937 tokens (~468/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

Install

How do I install the AlertsBar MCP server?

AlertsBar is a hosted endpoint at https://mcp.alerts.bar/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 · mcp.alerts.bar

# add to Claude Code
claude mcp add --transport http bar-alerts-alertsbar 'https://mcp.alerts.bar/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "bar-alerts-alertsbar": {
      "url": "https://mcp.alerts.bar/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "bar-alerts-alertsbar": {
      "type": "http",
      "url": "https://mcp.alerts.bar/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.bar-alerts-alertsbar]
url = "https://mcp.alerts.bar/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bar-alerts-alertsbar": {
      "type": "remote",
      "url": "https://mcp.alerts.bar/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bar-alerts-alertsbar --url 'https://mcp.alerts.bar/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  bar-alerts-alertsbar:
    url: "https://mcp.alerts.bar/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "bar-alerts-alertsbar": {
      "Transport": "http",
      "Url": "https://mcp.alerts.bar/mcp"
    }
  }
}
# add to Vellum
assistant mcp add bar-alerts-alertsbar -t streamable-http -u 'https://mcp.alerts.bar/mcp'
// mcp.json
{
  "mcpServers": {
    "bar-alerts-alertsbar": {
      "type": "http",
      "url": "https://mcp.alerts.bar/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 6 Oct 26 +36
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Schema quality: 234 → 468 ▼ functional
    • Schema quality: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Destructive annotations: pass functional
    • First check of Tool coverage: 100 functional
    • First check of Tool coverage: 100 functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
  • 25 Sept 26 −16
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 23 Sept 26 48

    First indexed and scored.

Diagnostics

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 6 Oct 2026 · Probed https://mcp.alerts.bar/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=alerts.bar CN=WE1,O=Google Trust Services,C=US 22 Sept 2026 21 Dec 2026 ECDSA 256 ECDSA-SHA256 d9bc47ca2b71897d0e1179495861bce8
SANs: alerts.bar, *.alerts.bar
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 insecure

Validation of mcp.alerts.bar. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
bar. present 4459 13 Verified
alerts.bar. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.alerts.bar/mcp Verified 200
http (plaintext) http://mcp.alerts.bar/mcp HTTPS enforced 301 https://mcp.alerts.bar/mcp
MCP tools · 2 exposed · ~579 tokens

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 →

Tool Tokens
exposure_counts_for_domain ~334

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 INDEXATION dates, not incident dates: _month/_week mean 'newly indexed', never 'newly leaked' - the underlying leak may be years old. Windows nest (_total includes _month includes _week) - never sum them. Counters are rebuilt once daily, so figures are up to 24h old and never real-time. Repeated calls for the same input within a day return identical values - do not re-query to check for changes. Accepts a bare domain or a full URL; scheme, path, port, case and a leading www. are stripped and subdomains collapse to the registrable domain (multi-tenant hosting suffixes such as github.io are not collapsed). An IDN must already be in punycode (xn--) form. Invalid input (not a domain, an IP address) returns an error. If the domain is not in the index at all, every counter and both dates are null: that means NO DATA, not that the domain is clean - never report it as 'no exposure'. first_indexed_at and last_indexed_at give the date range of the domain's records; use last_indexed_at as the 'last updated' date for the domain. Free, no auth.

NameTypeReqDescription
domainstringyesDomain to check, e.g. example.com. A full URL is accepted and normalized.
NameTypeReqDescription
breaches_monthinteger|nullyesIndexed in last 30d. Subset of breaches_total.
breaches_totalinteger|nullyesRecords from known breach incidents, indexed all time.
breaches_weekinteger|nullyesIndexed in last 7d. Subset of breaches_month.
cookies_monthinteger|nullyesIndexed in last 30d. Subset of cookies_total.
cookies_totalinteger|nullyesStolen browser session cookies, indexed all time. Non-zero means session-hijacking risk that a password reset alone does not fix. Cookies are counted here only; they are not included in exposure_samp…
cookies_weekinteger|nullyesIndexed in last 7d. Subset of cookies_month.
domainstringyesNormalized domain actually queried. May differ from the input - report this one to the user.
first_indexed_atstring|nullyesDate-time (format YYYY-MM-DD HH:MM:SS, UTC) when AlertsBar first indexed a record for this domain. Indexation date, not incident date - never say the domain was first leaked then. Null if the domain…
heap_staff_monthinteger|nullyesIndexed in last 30d. Subset of heap_staff_total.
heap_staff_totalinteger|nullyesStaff logins in unattributed heap of ULP (Url,Login,Password) bundles - no linkable breach, device or leak date. Credentials circulating in the wild.
heap_staff_weekinteger|nullyesIndexed in last 7d. Subset of heap_staff_month.
heap_users_monthinteger|nullyesIndexed in last 30d. Subset of heap_users_total.
heap_users_totalinteger|nullyesCustomer logins in unattributed heap of ULP (Url,Login,Password) bundles - no linkable breach, device or leak date.
heap_users_weekinteger|nullyesIndexed in last 7d. Subset of heap_users_month.
last_indexed_atstring|nullyesDate-time (format YYYY-MM-DD HH:MM:SS, UTC) when AlertsBar last indexed a record for this domain. This is the domain's 'last updated' date and the only reliable freshness signal - samples are random…
stealers_staff_monthinteger|nullyesIndexed in last 30d. Subset of stealers_staff_total.
stealers_staff_totalinteger|nullyesStaff logins from infostealer-infected devices, indexed all time. Implies a compromised machine, not just a leaked password. The credentials may be for any site, not only this domain's own systems.
stealers_staff_weekinteger|nullyesIndexed in last 7d. Subset of stealers_staff_month.
stealers_users_monthinteger|nullyesIndexed in last 30d. Subset of stealers_users_total.
stealers_users_totalinteger|nullyesCustomer logins for this domain's site from infostealer-infected devices, indexed all time.
stealers_users_weekinteger|nullyesIndexed in last 7d. Subset of stealers_users_month.

No examples provided.

exposure_samples_for_domain ~245

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 exposure_counts_for_domain. The sample is neither the newest nor the largest nor the most severe records, and it can differ between calls; identical-looking records can repeat and because of different logins/passwords. Each record says WHICH url was affected, WHICH domain the captured login belonged to, from WHICH source type, roughly when the incident was, and when the record was indexed. It carries NO credentials: no password, no username, and the login's local part is redacted. Use exposure_counts_for_domain first for the scale of the problem and for freshness (last_indexed_at); use this only when the user asks to see concrete examples. Calling again returns another random subset, never the full set - do not call it repeatedly to collect more records.

NameTypeReqDescription
domainstringyesDomain to check, e.g. example.com. A full URL is accepted and normalized, same rules as exposure_counts_for_domain.
NameTypeReqDescription
domainstringyesNormalized domain actually queried. May differ from the input - report this one to the user.
recordsarrayyesA random subset of up to 20 records per type, listed by indexed_at descending inside this response. NOT the newest records: a recent or old indexed_at here says nothing about the domain's overall rec…

No examples provided.

Common questions

What is the AlertsBar MCP server?

AlertsBar is an MCP server listed in the public MCP registry as bar.alerts/alertsbar. Domain exposures: breaches, infostealers, ULP heap, cookies. Counts and samples, free. This page covers its hosted endpoint (https://mcp.alerts.bar/mcp).

Is the AlertsBar MCP server safe to use?

AlertsBar scores 69 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 AlertsBar MCP server expose?

AlertsBar exposes 2 tools: exposure_counts_for_domain, exposure_samples_for_domain. Their descriptions and schemas cost roughly 579 tokens of context every time the server is loaded.

Does the AlertsBar MCP server require authentication?

No. We connected to AlertsBar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AlertsBar MCP server still maintained?

AlertsBar is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.