Remote MCP · Endpoint

Properly.fm MCP server

No. Properly.fm answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://properly.fm/mcp

The last check completed an MCP handshake.

Registry name
fm.properly/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
179 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Properly.fm er en dansk platform til udbud af serviceaftaler på ejendomme, fra Damsgaard FM.
Listing
From the official MCP registry (active).
Recent checks of Properly.fm
CheckedResultHandshake
12 minutes agoHandshake completed179 ms
9 days agoHandshake completed203 ms
9 days agoHandshake completed188 ms
11 days agoHandshake completed219 ms
12 days agoHandshake completed1.22 s
13 days agoHandshake completed208 ms
14 days agoHandshake completed202 ms
14 days agoHandshake completed181 ms
16 days agoHandshake completed214 ms
19 days agoHandshake completed198 ms
21 days agoHandshake completed177 ms
24 days agoHandshake completed162 ms
26 days agoHandshake completed172 ms
28 days agoHandshake completed209 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 Properly.fm and makes no claim about it beyond what these checks measured.