Remote MCP · Endpoint

Broadcastwell MCP server

No. Broadcastwell answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://app.broadcastwell.com/mcp/demo/kalvenor

The last check completed an MCP handshake.

Registry name
io.github.Broadcastwell/connector
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
915 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read how five AI engines answer your buyers' questions, who they name instead, and every receipt.
Listing
From the official MCP registry (active).
Recent checks of Broadcastwell
CheckedResultHandshake
43 minutes agoHandshake completed915 ms
8 days agoHandshake completed632 ms
9 days agoHandshake completed566 ms
11 days agoHandshake completed563 ms
12 days agoHandshake completed455 ms
13 days agoHandshake completed522 ms
14 days agoHandshake completed793 ms
14 days agoHandshake completed1.09 s
16 days agoHandshake completed588 ms
19 days agoHandshake completed551 ms
21 days agoHandshake completed614 ms
24 days agoHandshake completed561 ms
26 days agoHandshake completed501 ms
28 days agoHandshake completed165 ms

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

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 Broadcastwell and makes no claim about it beyond what these checks measured.