Remote MCP · Endpoint

com.vulnrable/vulnrable MCP server

No. com.vulnrable/vulnrable answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vulnrable.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.vulnrable/vulnrable
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
488 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Security grades for MCP servers and npm/PyPI packages, ranked by CISA KEV and EPSS.
Listing
From the official MCP registry (active).
Recent checks of com.vulnrable/vulnrable
CheckedResultHandshake
1 hour agoHandshake completed488 ms
7 hours agoHandshake completed533 ms
2 days agoHandshake completed557 ms
4 days agoHandshake completed469 ms
6 days agoHandshake completed496 ms
9 days agoHandshake completed565 ms
11 days agoHandshake completed352 ms
13 days agoHandshake completed413 ms
15 days agoHandshake completed422 ms
17 days agoHandshake completed430 ms
19 days agoHandshake completed461 ms
21 days agoHandshake completed356 ms
23 days agoHandshake completed510 ms
24 days agoHandshake completed383 ms

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

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