Remote MCP · Endpoint

ai.getvda/llm-orchestration-agent-langchain-core MCP server

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

UpLast checked 1 hour ago

Server URL

https://llm-orchestration-agent-langchain-core.getvda.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.getvda/llm-orchestration-agent-langchain-core
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
531 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
LLM Orchestration Agent (Langchain Core)
Listing
From the official MCP registry (active).
Recent checks of ai.getvda/llm-orchestration-agent-langchain-core
CheckedResultHandshake
1 hour agoHandshake completed531 ms
2 days agoHandshake completed103 ms
4 days agoHandshake completed83 ms
5 days agoHandshake completed66 ms
7 days agoHandshake completed78 ms
8 days agoHandshake completed106 ms
9 days agoHandshake completed69 ms
11 days agoHandshake completed66 ms
13 days agoHandshake completed489 ms
15 days agoHandshake completed71 ms
17 days agoHandshake completed82 ms
18 days agoHandshake completed98 ms
19 days agoHandshake completed70 ms
20 days agoHandshake completed68 ms
21 days agoHandshake completed83 ms
21 days agoHandshake completed72 ms
23 days agoHandshake completed65 ms
24 days agoHandshake completed75 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.

Listing data comes from the official MCP registry. Glide is not affiliated with ai.getvda/llm-orchestration-agent-langchain-core and makes no claim about it beyond what these checks measured.