Remote MCP · Endpoint

FlatHunt MCP server

No. FlatHunt answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.flat-hunt.com/mcp

The last check completed an MCP handshake.

Registry name
com.flat-hunt/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
130 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search furnished Berlin housing, compare listings, and manage favorites and saved-search alerts.
Listing
From the official MCP registry (active).
Recent checks of FlatHunt
CheckedResultHandshake
2 hours agoHandshake completed130 ms
2 days agoHandshake completed151 ms
4 days agoHandshake completed124 ms
7 days agoHandshake completed157 ms
9 days agoHandshake completed186 ms
11 days agoHandshake completed132 ms
13 days agoHandshake completed137 ms
15 days agoHandshake completed131 ms
16 days agoHandshake completed123 ms
18 days agoHandshake completed129 ms
19 days agoHandshake completed122 ms
20 days agoHandshake completed131 ms
23 days agoHandshake completed118 ms
24 days agoHandshake completed116 ms

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

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