Remote MCP · Endpoint

fline MCP server

No. fline answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://mcp.fline.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.fline/fline
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
294 ms
Tools exposed
40 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Hosting for apps you build with AI. Tested with Claude Code and Codex. Private beta: ask for access.
Listing
From the official MCP registry (active).
Recent checks of fline
CheckedResultHandshake
56 minutes agoHandshake completed294 ms
3 days agoHandshake completed300 ms
12 days agoHandshake completed395 ms
13 days agoHandshake completed311 ms
14 days agoHandshake completed638 ms
15 days agoHandshake completed308 ms
17 days agoHandshake completed311 ms
18 days agoHandshake completed292 ms
18 days agoHandshake completed373 ms
20 days agoHandshake completed324 ms
22 days agoHandshake completed295 ms
25 days agoHandshake completed284 ms
27 days agoHandshake completed303 ms
29 days agoHandshake completed277 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 fline and makes no claim about it beyond what these checks measured.