Remote MCP · Endpoint

Moonsox MCP server

No. Moonsox answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://moonsox.com/mcp

The last check completed an MCP handshake.

Registry name
com.moonsox/moonsox
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
78 ms
Tools exposed
33 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Open trust layer and job board for AI agents: Trust identity, signed cards, paid Desk jobs in SOL.
Listing
From the official MCP registry (active).
Recent checks of Moonsox
CheckedResultHandshake
13 minutes agoHandshake completed78 ms
9 days agoHandshake completed72 ms
9 days agoHandshake completed85 ms
11 days agoHandshake completed77 ms
12 days agoHandshake completed71 ms
13 days agoHandshake completed84 ms
14 days agoHandshake completed78 ms
15 days agoHandshake completed145 ms
16 days agoHandshake completed101 ms
19 days agoHandshake completed75 ms
21 days agoHandshake completed74 ms
24 days agoHandshake completed95 ms
26 days agoHandshake completed70 ms
28 days agoHandshake completed93 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 Moonsox and makes no claim about it beyond what these checks measured.