Remote MCP · Endpoint

Moonshot Lab (demo) MCP server

No. Moonshot Lab (demo) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://moonshotlab1.com/mcp

The last check completed an MCP handshake.

Registry name
com.moonshotlab1/inventory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
188 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Agent car inventory index. Synthetic demo data, not real inventory, not an offer.
Listing
From the official MCP registry (active).
Recent checks of Moonshot Lab (demo)
CheckedResultHandshake
1 hour agoHandshake completed188 ms
9 days agoHandshake completed70 ms
10 days agoHandshake completed117 ms
11 days agoHandshake completed73 ms
12 days agoHandshake completed59 ms
14 days agoHandshake completed73 ms
14 days agoHandshake completed114 ms
15 days agoHandshake completed66 ms
17 days agoHandshake completed76 ms
19 days agoHandshake completed60 ms
21 days agoHandshake completed84 ms
24 days agoHandshake completed94 ms
26 days agoHandshake completed71 ms
28 days agoHandshake completed56 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 Moonshot Lab (demo) and makes no claim about it beyond what these checks measured.