Search / bar.alerts/alertsbar
protogridR0· no sign-inDomain exposures: breaches, infostealers, ULP heap, cookies. Counts and samples, free.
v0.1.1 · active · website · descriptor JSON · versions
{
"mcpServers": {
"alertsbar": {
"type": "http",
"url": "https://mcp.alerts.bar/mcp"
}
}
}claude mcp add --transport http alertsbar https://mcp.alerts.bar/mcp[mcp_servers.alertsbar]
url = "https://mcp.alerts.bar/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"alertsbar": {
"type": "remote",
"url": "https://mcp.alerts.bar/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"alertsbar": {
"type": "http",
"url": "https://mcp.alerts.bar/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=alertsbar&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmFsZXJ0cy5iYXIvbWNwIn0%3D"
}{
"servers": {
"alertsbar": {
"type": "http",
"url": "https://mcp.alerts.bar/mcp"
}
}
}{
"mcpServers": {
"alertsbar": {
"httpUrl": "https://mcp.alerts.bar/mcp"
}
}
}extensions:
"alertsbar":
enabled: true
name: "alertsbar"
type: streamable_http
uri: "https://mcp.alerts.bar/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations2 of 2 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: exposure_samples_for_domain (destructiveHint, idempotentHint, openWorldHint); exposure_counts_for_domain (destructiveHint, idempotentHint, openWorldHint)tools.token_costabout 711 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes4 tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageexposure_samples_for_domainchangeddescription, output schemaA small sample of individual exposure records for a domain - metadata only, capped in number. 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 and identifies NO individual: no password, no username, and the login's local part is redacted. Use exposure_counts_for_domain first for the scale of the problem; use this only when the user asks to see concrete examples. The sample is capped and does not grow on repeat calls - never call it again to collect more records.
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.
exposure_counts_for_domainchangeddescription, output schemaCredential-exposure counters for a domain. Counts only - no credential values or per-account detail. Sources: known breaches, infostealer infections, unattributed ULP bundles (heap), 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. An IDN must already be in punycode (xn--) form. Free, no auth.
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.
exposure_samples_for_domainaddedA small sample of individual exposure records for a domain - metadata only, capped in number. 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 and identifies NO individual: no password, no username, and the login's local part is redacted. Use exposure_counts_for_domain first for the scale of the problem; use this only when the user asks to see concrete examples. The sample is capped and does not grow on repeat calls - never call it again to collect more records.
exposure_counts_for_domainchangeddescription, input schema, annotationsCredential-exposure counters for a domain. Counts only - no credential values or per-account detail. Sources: known breaches, infostealer infections, unattributed ULP bundles (heap), stolen cookies. All figures are INDEXATION dates, not incident dates: _month/_week mean 'newly indexed', never 'newly leaked' - the underlying leak may be months 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, URL or IDN in punycode (xn--) form normalized to the registrable domain. Free, no auth.
Credential-exposure counters for a domain. Counts only - no credential values or per-account detail. Sources: known breaches, infostealer infections, unattributed ULP bundles (heap), 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. An IDN must already be in punycode (xn--) form. Free, no auth.
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website +reachable +uptime-100% +updated-18d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://mcp.alerts.bar/mcp streamable-http | none | yes | 100% | 600 ms | 2025-11-25 | 2026-10-20 |
exposure_counts_for_domainread-only | 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. |
exposure_samples_for_domainread-only | 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. |
Schemas: list_tools.
{
"name": "bar.alerts/alertsbar",
"title": "AlertsBar",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://mcp.alerts.bar/mcp",
"type": "streamable-http"
}
],
"version": "0.1.1",
"websiteUrl": "https://www.alerts.bar",
"description": "Domain exposures: breaches, infostealers, ULP heap, cookies. Counts and samples, free."
}