Remote MCP · Endpoint

FernTool Network Tools MCP server

No. FernTool Network Tools answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://www.ferntool.com/mcp

The last check completed an MCP handshake.

Registry name
com.ferntool/ip
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
178 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
24 free tools: IP/VPN lookup, WHOIS, DNS, SPF/DMARC, site up/down, redirects, time zones. No key.
Listing
From the official MCP registry (active).
Recent checks of FernTool Network Tools
CheckedResultHandshake
18 minutes agoHandshake completed178 ms
10 days agoHandshake completed117 ms
10 days agoHandshake completed128 ms
11 days agoHandshake completed87 ms
13 days agoHandshake completed79 ms
14 days agoHandshake completed96 ms
14 days agoHandshake completed125 ms
15 days agoHandshake completed143 ms
17 days agoHandshake completed99 ms
19 days agoHandshake completed208 ms
21 days agoHandshake completed60 ms
24 days agoHandshake completed91 ms
26 days agoHandshake completed93 ms
28 days agoHandshake completed81 ms

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

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