Remote MCP · Endpoint

ai.getvda/encrypted-oauth-llm-agent MCP server

No. ai.getvda/encrypted-oauth-llm-agent answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://authenticated-llm-agent-cryptography.getvda.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.getvda/encrypted-oauth-llm-agent
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
86 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Encrypted OAuth LLM Agent
Listing
From the official MCP registry (active).
Recent checks of ai.getvda/encrypted-oauth-llm-agent
CheckedResultHandshake
43 minutes agoHandshake completed86 ms
10 days agoHandshake completed68 ms
10 days agoHandshake completed93 ms
11 days agoHandshake completed94 ms
12 days agoHandshake completed73 ms
14 days agoHandshake completed116 ms
14 days agoHandshake completed67 ms
15 days agoHandshake completed88 ms
17 days agoHandshake completed89 ms
19 days agoHandshake completed73 ms
21 days agoHandshake completed76 ms
24 days agoHandshake completed69 ms
26 days agoHandshake completed86 ms
28 days agoHandshake completed75 ms

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

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