Remote MCP · Endpoint

Vadivam Icons MCP server

No. Vadivam Icons answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://vadivam.praveenjuge.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.praveenjuge/vadivam
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
533 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search 24px outline icons by name, tag, or category and get SVG or framework code.
Listing
From the official MCP registry (active).
Recent checks of Vadivam Icons
CheckedResultHandshake
33 minutes agoHandshake completed533 ms
3 days agoHandshake completed396 ms
13 days agoHandshake completed313 ms
13 days agoHandshake completed427 ms
15 days agoHandshake completed55 ms
16 days agoHandshake completed342 ms
17 days agoHandshake completed442 ms
18 days agoHandshake completed289 ms
18 days agoHandshake completed295 ms
20 days agoHandshake completed87 ms
22 days agoHandshake completed312 ms
25 days agoHandshake completed179 ms
27 days agoHandshake completed445 ms

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

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