Remote MCP · Endpoint

Beamline UI MCP server

No. Beamline UI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.beamline.io/mcp

The last check completed an MCP handshake.

Registry name
io.beamline/beamline
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
401 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
React UI parts your agent copies into your repo as code you own: 200+ components, 50+ screens.
Listing
From the official MCP registry (active).
Recent checks of Beamline UI
CheckedResultHandshake
1 hour agoHandshake completed401 ms
22 hours agoHandshake completed273 ms
1 day agoHandshake completed364 ms
3 days agoHandshake completed299 ms
5 days agoHandshake completed274 ms
7 days agoHandshake completed228 ms
10 days agoCredentials required—
12 days agoCredentials required—
14 days agoCredentials required—
16 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
23 days agoCredentials required—

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

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