Remote MCP · Endpoint

Nomid MDM MCP server

No. Nomid MDM answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://mcp.nomid.tech/emm/api/mcp

The last check completed an MCP handshake.

Registry name
com.nomidmdm/nomid-mdm
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
57 ms
Tools exposed
35 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Manage Android and VR device fleets: policies, kiosk mode, device commands and enrollment QR codes.
Listing
From the official MCP registry (active).
Recent checks of Nomid MDM
CheckedResultHandshake
10 hours agoHandshake completed57 ms
4 days agoHandshake completed47 ms
7 days agoHandshake completed51 ms

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

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