Remote MCP · Endpoint

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

No. ai.getvda/elasticsearch-mongodb-redis-stack-generator-elasticsearch-elasticsearch answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
ai.getvda/elasticsearch-mongodb-redis-stack-generator-elasticsearch-elasticsearch
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
77 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Elasticsearch + MongoDB + Redis Stack Generator (Elasticsearch/Elasticsearch)
Website
https://elasticsearch-mongodb-redis-stack-generator-el-d8f067.getvda.ai/
Listing
From the official MCP registry (active).
Recent checks of ai.getvda/elasticsearch-mongodb-redis-stack-generator-elasticsearch-elasticsearch
CheckedResultHandshake
2 hours agoHandshake completed77 ms
1 day agoHandshake completed71 ms
3 days agoHandshake completed75 ms
3 days agoHandshake completed73 ms
4 days agoHandshake completed74 ms
5 days agoHandshake completed83 ms
7 days agoHandshake completed87 ms
10 days agoHandshake completed76 ms
12 days agoHandshake completed96 ms
14 days agoHandshake completed84 ms
17 days agoHandshake completed80 ms
19 days agoHandshake completed134 ms
21 days agoHandshake completed205 ms
23 days agoHandshake completed123 ms
25 days agoHandshake completed72 ms
26 days agoHandshake completed82 ms
28 days agoHandshake completed80 ms
29 days agoHandshake completed79 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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.

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-mongodb-redis-stack-generator-elasticsearch-elasticsearch and makes no claim about it beyond what these checks measured.