Remote MCP · Endpoint

AlertsBar MCP server

No. AlertsBar answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.alerts.bar/mcp

The last check completed an MCP handshake.

Registry name
bar.alerts/alertsbar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
400 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Domain exposures: breaches, infostealers, ULP heap, cookies. Counts and samples, free.
Listing
From the official MCP registry (active).
Recent checks of AlertsBar
CheckedResultHandshake
1 hour agoHandshake completed400 ms
2 days agoHandshake completed388 ms
4 days agoHandshake completed421 ms
6 days agoHandshake completed390 ms
7 days agoHandshake completed411 ms
9 days agoHandshake completed420 ms
10 days agoHandshake completed387 ms
11 days agoHandshake completed404 ms
14 days agoHandshake completed399 ms
15 days agoHandshake completed405 ms
17 days agoHandshake completed450 ms
18 days agoHandshake completed416 ms
19 days agoHandshake completed389 ms
21 days agoHandshake completed386 ms
21 days agoHandshake completed425 ms
22 days agoHandshake completed397 ms
23 days agoHandshake completed426 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with AlertsBar and makes no claim about it beyond what these checks measured.