Remote MCP · Endpoint

iFun MCP server

No. iFun answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://ifun.navatop.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.linhnnmt/ifun
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
183 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Bilingual (VN/EN) jokes, quotes, fun facts and short videos from ifun.navatop.com.
Listing
From the official MCP registry (active).
Recent checks of iFun
CheckedResultHandshake
5 hours agoHandshake completed183 ms
2 days agoHandshake completed229 ms
4 days agoHandshake completed127 ms
5 days agoHandshake completed104 ms
7 days agoHandshake completed219 ms
8 days agoHandshake completed235 ms
9 days agoHandshake completed143 ms
12 days agoHandshake completed258 ms
13 days agoHandshake completed116 ms
15 days agoHandshake completed180 ms
16 days agoHandshake completed103 ms
17 days agoHandshake completed51 ms
18 days agoHandshake completed114 ms
19 days agoHandshake completed47 ms
20 days agoHandshake completed145 ms
21 days agoHandshake completed125 ms
22 days agoHandshake completed133 ms

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

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