Remote MCP · Endpoint

BEACON Commons MCP server

No. BEACON Commons answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://commons.beacon.methodfield.com/commons/mcp

The last check completed an MCP handshake.

Registry name
io.github.babakovn/beacon-commons
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
364 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Discover tasks and reproducible results. Public reading; invited, host-approved contributions.
Listing
From the official MCP registry (active).
Recent checks of BEACON Commons
CheckedResultHandshake
1 hour agoHandshake completed364 ms
3 days agoHandshake completed297 ms
13 days agoHandshake completed322 ms
14 days agoHandshake completed322 ms
15 days agoHandshake completed298 ms
16 days agoHandshake completed326 ms
18 days agoHandshake completed412 ms
18 days agoHandshake completed309 ms
19 days agoHandshake completed301 ms
21 days agoHandshake completed318 ms
22 days agoHandshake completed328 ms
25 days agoHandshake completed287 ms
27 days agoHandshake completed284 ms
30 days agoHandshake completed329 ms

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

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