Remote MCP · Endpoint

Damsgaard FM MCP server

No. Damsgaard FM answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://dgfm.dk/mcp

The last check completed an MCP handshake.

Registry name
dk.dgfm/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
125 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Damsgaard FM er udbudsrådgivere for ejendomsejere og står bag platformen Properly.fm.
Website
https://dgfm.dk/
Listing
From the official MCP registry (active).
Recent checks of Damsgaard FM
CheckedResultHandshake
12 minutes agoHandshake completed125 ms
9 days agoHandshake completed98 ms
9 days agoHandshake completed58 ms
11 days agoHandshake completed205 ms
12 days agoHandshake completed169 ms
13 days agoHandshake completed99 ms
14 days agoHandshake completed58 ms
14 days agoHandshake completed113 ms
16 days agoHandshake completed73 ms
19 days agoHandshake completed83 ms
21 days agoHandshake completed75 ms
24 days agoHandshake completed88 ms
26 days agoHandshake completed90 ms
28 days agoHandshake completed984 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Damsgaard FM and makes no claim about it beyond what these checks measured.