Remote MCP · Endpoint

Nexwin MCP server

No. Nexwin answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.nexwin.com.au/mcp

The last check completed an MCP handshake.

Registry name
au.com.nexwin/nexwin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.18 s
Tools exposed
21 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Check bookings, review calls and chats, and manage appointments in your Nexwin AI receptionist.
Listing
From the official MCP registry (active).
Recent checks of Nexwin
CheckedResultHandshake
1 hour agoHandshake completed1.18 s
2 days agoHandshake completed999 ms
4 days agoHandshake completed321 ms
5 days agoHandshake completed1.02 s
7 days agoHandshake completed345 ms
8 days agoHandshake completed304 ms
9 days agoHandshake completed307 ms
12 days agoHandshake completed1.38 s
13 days agoHandshake completed299 ms
15 days agoHandshake completed980 ms
17 days agoHandshake completed958 ms
18 days agoHandshake completed946 ms
19 days agoHandshake completed990 ms
20 days agoHandshake completed977 ms
20 days agoHandshake completed296 ms
21 days agoHandshake completed1.11 s

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