Remote MCP · Endpoint

The Quartermaster MCP server

No. The Quartermaster answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://quartermaster.style/api/mcp/

The last check completed an MCP handshake.

Registry name
style.quartermaster/menswear-outfits
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
109 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Independent menswear concierge: what to wear to any occasion, and is this piece worth the price.
Listing
From the official MCP registry (active).
Recent checks of The Quartermaster
CheckedResultHandshake
2 hours agoHandshake completed109 ms
2 days agoHandshake completed87 ms
4 days agoHandshake completed99 ms
6 days agoHandshake completed141 ms
8 days agoHandshake completed174 ms
10 days agoHandshake completed239 ms
12 days agoHandshake completed83 ms
13 days agoHandshake completed87 ms
14 days agoHandshake completed81 ms
16 days agoHandshake completed69 ms
18 days agoHandshake completed90 ms
20 days agoHandshake completed68 ms
21 days agoHandshake completed65 ms
23 days agoHandshake completed109 ms
24 days agoHandshake completed200 ms

The last 15 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.

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