Remote MCP · Endpoint

Avahit MCP server

No. Avahit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://avahit.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.avahit/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
340 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Creator product picks with daily-verified store prices and Avahit's own price history.
Listing
From the official MCP registry (active).
Recent checks of Avahit
CheckedResultHandshake
1 hour agoHandshake completed340 ms
2 days agoHandshake completed236 ms
4 days agoHandshake completed341 ms
5 days agoHandshake completed390 ms
7 days agoHandshake completed354 ms
8 days agoHandshake completed385 ms
9 days agoHandshake completed807 ms
12 days agoHandshake completed409 ms
13 days agoHandshake completed357 ms
15 days agoHandshake completed523 ms
16 days agoHandshake completed309 ms
17 days agoHandshake completed310 ms
18 days agoHandshake completed146 ms
19 days agoHandshake completed127 ms
20 days agoHandshake completed322 ms
21 days agoHandshake completed339 ms
22 days agoHandshake completed306 ms

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

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