Remote MCP · Endpoint

agproxy MCP server

No. agproxy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agproxy.shveik.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.shveik/agproxy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
298 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Residential proxy traffic and raw fetch for agents, 190+ countries, sticky sessions. Pay per call.
Website
https://agproxy.shveik.dev/
Listing
From the official MCP registry (active).
Recent checks of agproxy
CheckedResultHandshake
1 hour agoHandshake completed298 ms
2 days agoHandshake completed295 ms
5 days agoHandshake completed290 ms
7 days agoHandshake completed298 ms
9 days agoHandshake completed390 ms
11 days agoHandshake completed291 ms
13 days agoHandshake completed290 ms
15 days agoHandshake completed291 ms
17 days agoHandshake completed308 ms
19 days agoHandshake completed302 ms
20 days agoHandshake completed310 ms
21 days agoHandshake completed307 ms
22 days agoHandshake completed291 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 agproxy and makes no claim about it beyond what these checks measured.