Remote MCP · Endpoint

agvps MCP server

No. agvps answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agvps.shveik.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.shveik/agvps
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Servers for agents, rented by the month: Linux with root and a public IPv4. Pay per call.
Website
https://agvps.shveik.dev/
Listing
From the official MCP registry (active).
Recent checks of agvps
CheckedResultHandshake
1 hour agoHandshake completed290 ms
2 days agoHandshake completed303 ms
5 days agoHandshake completed291 ms
7 days agoHandshake completed293 ms
9 days agoHandshake completed296 ms
11 days agoHandshake completed294 ms
13 days agoHandshake completed299 ms
15 days agoHandshake completed292 ms
18 days agoHandshake completed292 ms
19 days agoHandshake completed313 ms
20 days agoHandshake completed335 ms
22 days agoHandshake completed581 ms
23 days agoHandshake completed292 ms

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

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