Remote MCP · Endpoint

ai.getvda/llm-orchestration-agent-2-df5979 MCP server

No. ai.getvda/llm-orchestration-agent-2-df5979 answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://llm-orchestration-agent-2-df5979.getvda.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.getvda/llm-orchestration-agent-2-df5979
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
70 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
LLM Orchestration Agent 2
Website
https://llm-orchestration-agent-2-df5979.getvda.ai/
Listing
From the official MCP registry (active).
Recent checks of ai.getvda/llm-orchestration-agent-2-df5979
CheckedResultHandshake
8 hours agoHandshake completed70 ms
2 days agoHandshake completed70 ms
4 days agoHandshake completed83 ms
5 days agoHandshake completed76 ms
7 days agoHandshake completed70 ms
8 days agoHandshake completed71 ms
9 days agoHandshake completed71 ms
12 days agoHandshake completed101 ms
13 days agoHandshake completed76 ms
15 days agoHandshake completed80 ms
16 days agoHandshake completed96 ms
17 days agoHandshake completed65 ms
18 days agoHandshake completed69 ms
19 days agoHandshake completed112 ms
20 days agoHandshake completed75 ms
21 days agoHandshake completed66 ms
23 days agoHandshake completed89 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.

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/llm-orchestration-agent-2-df5979 and makes no claim about it beyond what these checks measured.