Remote MCP · Endpoint
Golem Security MCP server
No. Golem Security answered an MCP handshake 2 days ago.
Up · key neededLast checked 2 days 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
- 1.42 s
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 2 checks from 2 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 |
|---|---|---|
| 2 days ago | Handshake completed | 1.42 s |
| 4 days ago | Handshake completed | 94 ms |
The last 2 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 2.
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.