Remote MCP · Endpoint

kr.ai.vdb/vdb MCP server

No. kr.ai.vdb/vdb answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://vdb.ai.kr/mcp

The last check completed an MCP handshake.

Registry name
kr.ai.vdb/vdb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
236 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Check packages for CVEs, slopsquatting, and CISA KEV before your AI agent installs them.
Listing
From the official MCP registry (active).
Recent checks of kr.ai.vdb/vdb
CheckedResultHandshake
43 minutes agoHandshake completed236 ms
3 days agoHandshake completed217 ms
13 days agoHandshake completed210 ms
13 days agoHandshake completed212 ms
15 days agoHandshake completed210 ms
15 days agoHandshake completed221 ms
17 days agoHandshake completed202 ms
18 days agoHandshake completed208 ms
18 days agoHandshake completed217 ms
20 days agoHandshake completed210 ms
22 days agoHandshake completed206 ms
25 days agoHandshake completed234 ms
27 days agoHandshake completed231 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.

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 kr.ai.vdb/vdb and makes no claim about it beyond what these checks measured.