Remote MCP · Endpoint

io.github.cyanheads/nist-nvd-mcp-server MCP server

No. io.github.cyanheads/nist-nvd-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://nist-nvd.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/nist-nvd-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
117 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Search and audit NIST NVD CVEs by keyword, severity, CWE, CISA KEV status, and CPE.
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/nist-nvd-mcp-server
CheckedResultHandshake
1 hour agoHandshake completed117 ms
2 days agoHandshake completed91 ms
4 days agoHandshake completed171 ms
6 days agoHandshake completed96 ms
7 days agoHandshake completed110 ms
9 days agoHandshake completed73 ms
10 days agoHandshake completed130 ms
11 days agoHandshake completed93 ms
14 days agoHandshake completed134 ms
15 days agoHandshake completed92 ms
17 days agoHandshake completed109 ms
18 days agoHandshake completed98 ms
19 days agoHandshake completed101 ms
20 days agoHandshake completed107 ms
21 days agoHandshake completed73 ms
22 days agoHandshake completed85 ms
23 days agoHandshake completed106 ms
24 days agoHandshake completed77 ms

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

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 io.github.cyanheads/nist-nvd-mcp-server and makes no claim about it beyond what these checks measured.