Remote MCP · Endpoint

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

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

UpLast checked 8 hours ago

Server URL

https://langchain-langchain-core-langsmit-d042fc.getvda.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.getvda/llm-observability-orchestration-agent-langchain
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
120 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
LLM Observability & Orchestration Agent (Langchain)
Listing
From the official MCP registry (active).
Recent checks of ai.getvda/llm-observability-orchestration-agent-langchain
CheckedResultHandshake
8 hours agoHandshake completed120 ms
2 days agoHandshake completed111 ms
4 days agoHandshake completed79 ms
5 days agoHandshake completed74 ms
7 days agoHandshake completed71 ms
8 days agoHandshake completed65 ms
9 days agoHandshake completed72 ms
12 days agoHandshake completed93 ms
13 days agoHandshake completed76 ms
15 days agoHandshake completed80 ms
16 days agoHandshake completed65 ms
17 days agoHandshake completed63 ms
18 days agoHandshake completed85 ms
19 days agoHandshake completed69 ms
20 days agoHandshake completed64 ms
21 days agoHandshake completed83 ms
23 days agoHandshake completed66 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.

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