Remote MCP · Endpoint

Fleek MCP server

No. Fleek answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://deals-mcp.getfleek.app/registry/mcp

The last check completed an MCP handshake.

Registry name
app.getfleek/deals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
263 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fleek's current prices for digital subscriptions vs list price, plan comparisons and app links.
Listing
From the official MCP registry (active).
Recent checks of Fleek
CheckedResultHandshake
43 minutes agoHandshake completed263 ms
8 days agoHandshake completed185 ms
9 days agoHandshake completed170 ms
11 days agoHandshake completed74 ms
12 days agoHandshake completed310 ms
13 days agoHandshake completed61 ms
14 days agoHandshake completed193 ms
14 days agoHandshake completed223 ms
16 days agoHandshake completed65 ms
19 days agoHandshake completed191 ms
21 days agoHandshake completed64 ms
24 days agoHandshake completed185 ms
26 days agoHandshake completed49 ms
28 days agoHandshake completed167 ms

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

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