Remote MCP · Endpoint

Golem Context MCP server

No. Golem Context answered an MCP handshake 15 minutes ago.

Up · key neededLast checked 15 minutes ago

Server URL

https://context.golem.team/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
team.golem/context
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
214 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read your Golem fleet's ledger from any MCP client: agents' sessions, live activity, signed record.
Listing
From the official MCP registry (active).
Recent checks of Golem Context
CheckedResultHandshake
15 minutes agoHandshake completed214 ms
9 days agoHandshake completed202 ms
9 days agoHandshake completed175 ms
11 days agoHandshake completed421 ms
12 days agoHandshake completed174 ms
13 days agoHandshake completed149 ms
14 days agoHandshake completed326 ms
14 days agoHandshake completed205 ms
16 days agoHandshake completed249 ms
19 days agoHandshake completed218 ms
21 days agoHandshake completed155 ms
24 days agoHandshake completed118 ms
26 days agoHandshake completed254 ms
28 days agoHandshake completed192 ms

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