Remote MCP · Endpoint

ai.getvda/llm-orchestration-agent-d2feb0 MCP server

No. ai.getvda/llm-orchestration-agent-d2feb0 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://llm-orchestration-agent-d2feb0.getvda.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.getvda/llm-orchestration-agent-d2feb0
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
330 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
LangSmith-Traced LLM Orchestration Agent
Website
https://llm-orchestration-agent-d2feb0.getvda.ai/
Listing
From the official MCP registry (active).
Recent checks of ai.getvda/llm-orchestration-agent-d2feb0
CheckedResultHandshake
1 hour agoHandshake completed330 ms
2 days agoHandshake completed114 ms
4 days agoHandshake completed98 ms
5 days agoHandshake completed87 ms
7 days agoHandshake completed206 ms
8 days agoHandshake completed85 ms
9 days agoHandshake completed72 ms
11 days agoHandshake completed74 ms
13 days agoHandshake completed353 ms
15 days agoHandshake completed76 ms
17 days agoHandshake completed79 ms
18 days agoHandshake completed70 ms
19 days agoHandshake completed68 ms
20 days agoHandshake completed79 ms
21 days agoHandshake completed75 ms
21 days agoHandshake completed77 ms
23 days agoHandshake completed67 ms
24 days agoHandshake completed74 ms

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

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