Remote MCP · Endpoint
Golem Security MCP server
No. Golem Security answered an MCP handshake 13 minutes ago.
Up · key neededLast checked 13 minutes ago
Server URL
https://context.golem.team/security
The handshake completes, but listing its tools needs credentials.
- Registry name
- team.golem/security
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 154 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- Threat-intelligence verdicts on a URL, domain or IP before a coding agent connects to it.
- Website
- https://golem.team/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 13 minutes ago | Handshake completed | 154 ms |
| 9 days ago | Handshake completed | 170 ms |
| 9 days ago | Handshake completed | 172 ms |
| 11 days ago | Handshake completed | 202 ms |
| 12 days ago | Handshake completed | 185 ms |
| 13 days ago | Handshake completed | 177 ms |
| 14 days ago | Handshake completed | 158 ms |
| 15 days ago | Handshake completed | 256 ms |
| 16 days ago | Handshake completed | 420 ms |
| 19 days ago | Handshake completed | 206 ms |
| 21 days ago | Handshake completed | 186 ms |
| 24 days ago | Handshake completed | 211 ms |
| 26 days ago | Handshake completed | 1.42 s |
| 28 days ago | Handshake completed | 94 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 Security and makes no claim about it beyond what these checks measured.