Remote MCP · Endpoint

IP Judge MCP server

No. IP Judge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ipjudge.org/mcp

The last check completed an MCP handshake.

Registry name
org.ipjudge/ipjudge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
286 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check an IP or your own network exit before using ChatGPT, Claude, Gemini or Meta Muse.
Listing
From the official MCP registry (active).
Recent checks of IP Judge
CheckedResultHandshake
1 hour agoHandshake completed286 ms
2 days agoHandshake completed5.99 s
4 days agoHandshake completed244 ms
6 days agoHandshake completed805 ms
8 days agoHandshake completed976 ms
10 days agoHandshake completed289 ms
13 days agoHandshake completed257 ms
14 days agoHandshake completed221 ms
16 days agoHandshake completed391 ms
17 days agoHandshake completed747 ms
18 days agoHandshake completed221 ms
21 days agoHandshake completed225 ms
22 days agoHandshake completed237 ms
24 days agoHandshake completed277 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 IP Judge and makes no claim about it beyond what these checks measured.