Remote MCP · Endpoint

isIPsafe MCP server

No. isIPsafe answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://isipsafe.com/mcp

The last check completed an MCP handshake.

Registry name
com.isipsafe/isipsafe
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
316 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 5 checks
Described by its publisher as
Check whether an IP address or network is malicious and report abusive IPs to isIPsafe.
Listing
From the official MCP registry (active).
Recent checks of isIPsafe
CheckedResultHandshake
52 minutes agoHandshake completed316 ms
3 days agoHandshake completed421 ms
12 days agoHandshake completed149 ms
13 days agoHandshake completed136 ms
14 days agoHandshake completed1.56 s

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

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

isIPsafe MCP server - status, uptime and latency - Glide