Remote MCP · Endpoint

io.github.Xavierfok/singapore-proxy-mcp MCP server

No. io.github.Xavierfok/singapore-proxy-mcp answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.singaporemobileproxy.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Xavierfok/singapore-proxy-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
784 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Browse the web and run Google search through real Singapore mobile carrier IPs.
Listing
From the official MCP registry (active).
Recent checks of io.github.Xavierfok/singapore-proxy-mcp
CheckedResultHandshake
2 hours agoHandshake completed784 ms
1 day agoHandshake completed775 ms
3 days agoHandshake completed751 ms
3 days agoHandshake completed733 ms
4 days agoHandshake completed762 ms
5 days agoHandshake completed750 ms
7 days agoHandshake completed781 ms
10 days agoHandshake completed795 ms
12 days agoHandshake completed763 ms
15 days agoHandshake completed803 ms
17 days agoHandshake completed760 ms
19 days agoHandshake completed779 ms
21 days agoHandshake completed728 ms
23 days agoHandshake completed1.00 s
25 days agoHandshake completed749 ms
26 days agoHandshake completed801 ms
28 days agoHandshake completed850 ms
29 days agoHandshake completed773 ms

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

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 io.github.Xavierfok/singapore-proxy-mcp and makes no claim about it beyond what these checks measured.