Remote MCP · Endpoint

Agent Beacon MCP server

No. Agent Beacon answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://beacon.sophomath.com/mcp

The last check completed an MCP handshake.

Registry name
com.sophomath/agent-beacon
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
434 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Report capabilities needed and not found. Requests aren't fulfilled.
Listing
From the official MCP registry (active).
Recent checks of Agent Beacon
CheckedResultHandshake
1 hour agoHandshake completed434 ms
2 days agoHandshake completed236 ms
4 days agoHandshake completed360 ms
5 days agoHandshake completed243 ms
7 days agoHandshake completed361 ms
8 days agoHandshake completed770 ms
9 days agoHandshake completed346 ms
12 days agoHandshake completed217 ms
13 days agoHandshake completed288 ms
15 days agoHandshake completed413 ms
16 days agoHandshake completed290 ms
17 days agoHandshake completed311 ms
19 days agoHandshake completed296 ms
20 days agoHandshake completed239 ms
20 days agoHandshake completed259 ms
21 days agoHandshake completed278 ms
22 days agoHandshake completed322 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 Agent Beacon and makes no claim about it beyond what these checks measured.