Remote MCP · Endpoint
ZEN SecDB MCP server
No. ZEN SecDB answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://secdb.nttzen.cloud/mcp
The last check completed an MCP handshake.
- Registry name
- cloud.nttzen.secdb/zen-secdb
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 305 ms
- Tools exposed
- 19 tools
- Uptime, last 30 days
- 88.9% from 18 checks
- Described by its publisher as
- ZEN SecDB MCP server for CVE intelligence, CVSS/EPSS scoring, advisories, SSVC, and package audits.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 305 ms |
| 1 day ago | Handshake completed | 329 ms |
| 3 days ago | Handshake completed | 449 ms |
| 3 days ago | Handshake completed | 396 ms |
| 4 days ago | Handshake completed | 302 ms |
| 5 days ago | Handshake completed | 464 ms |
| 7 days ago | Failed - the request timed out | — |
| 10 days ago | Handshake completed | 462 ms |
| 12 days ago | Handshake completed | 371 ms |
| 14 days ago | Handshake completed | 295 ms |
| 17 days ago | Handshake completed | 292 ms |
| 19 days ago | Handshake completed | 318 ms |
| 21 days ago | Handshake completed | 284 ms |
| 23 days ago | Handshake completed | 290 ms |
| 25 days ago | Handshake completed | 1.08 s |
| 26 days ago | Handshake completed | 299 ms |
| 28 days ago | Handshake completed | 286 ms |
| 29 days ago | Failed - the request timed out | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 29.
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 ZEN SecDB and makes no claim about it beyond what these checks measured.