Remote MCP · Endpoint

ai.getvda/elasticsearch-redis-stack-generator MCP server

No. ai.getvda/elasticsearch-redis-stack-generator answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://elasticsearch-redis-stack-generator.getvda.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.getvda/elasticsearch-redis-stack-generator
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
77 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Elasticsearch + Redis Stack Generator
Website
https://elasticsearch-redis-stack-generator.getvda.ai/
Listing
From the official MCP registry (active).
Recent checks of ai.getvda/elasticsearch-redis-stack-generator
CheckedResultHandshake
1 hour agoHandshake completed77 ms
22 hours agoHandshake completed98 ms
2 days agoHandshake completed70 ms
3 days agoHandshake completed148 ms
4 days agoHandshake completed65 ms
5 days agoHandshake completed70 ms
6 days agoHandshake completed73 ms
8 days agoHandshake completed75 ms
11 days agoHandshake completed81 ms
13 days agoHandshake completed78 ms
15 days agoHandshake completed68 ms
18 days agoHandshake completed88 ms
20 days agoHandshake completed183 ms
22 days agoHandshake completed300 ms
24 days agoHandshake completed110 ms
25 days agoHandshake completed85 ms
27 days agoHandshake completed74 ms
29 days agoHandshake completed83 ms
29 days agoHandshake completed74 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with ai.getvda/elasticsearch-redis-stack-generator and makes no claim about it beyond what these checks measured.