Remote MCP · Endpoint

TrueProxies MCP server

No. TrueProxies answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.trueproxies.com/mcp

The last check completed an MCP handshake.

Registry name
com.trueproxies/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
549 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Plans, services, usage, invoices, endpoints and connection checks for your TrueProxies account
Listing
From the official MCP registry (active).
Recent checks of TrueProxies
CheckedResultHandshake
1 hour agoHandshake completed549 ms
2 days agoHandshake completed530 ms
4 days agoHandshake completed537 ms
6 days agoHandshake completed520 ms
8 days agoHandshake completed528 ms
10 days agoHandshake completed543 ms
12 days agoHandshake completed515 ms
14 days agoHandshake completed502 ms
15 days agoHandshake completed511 ms
16 days agoHandshake completed515 ms
17 days agoHandshake completed606 ms
20 days agoHandshake completed518 ms
22 days agoHandshake completed521 ms
23 days agoHandshake completed604 ms

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

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