Remote MCP · Endpoint

Circl Vulnerability Lookup MCP server

No. Circl Vulnerability Lookup answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/circl-vulnerability-lookup/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/circl-vulnerability-lookup
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
61 ms
Tools exposed
47 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
CIRCL Vulnerability-Lookup — aggregated vulnerability records
Listing
From the official MCP registry (active).
Recent checks of Circl Vulnerability Lookup
CheckedResultHandshake
1 hour agoHandshake completed61 ms
9 days agoHandshake completed106 ms
9 days agoHandshake completed113 ms
11 days agoHandshake completed1.21 s
12 days agoHandshake completed74 ms
13 days agoHandshake completed179 ms
14 days agoHandshake completed102 ms
15 days agoHandshake completed715 ms
16 days agoHandshake completed55 ms
19 days agoHandshake completed107 ms
22 days agoHandshake completed121 ms
24 days agoHandshake completed96 ms
26 days agoHandshake completed80 ms
28 days agoFailed - the request timed out—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 Circl Vulnerability Lookup and makes no claim about it beyond what these checks measured.