Remote MCP · Endpoint
app.surewhynot.quartermaster/quartermaster MCP server
No. app.surewhynot.quartermaster/quartermaster answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://quartermaster.surewhynot.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.surewhynot.quartermaster/quartermaster
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 604 ms
- Tools exposed
- 49 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- x402 toolkit for AI agents: paid web, AI, and Base chain tools per call in USDC. Free tools too.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 604 ms |
| 1 day ago | Handshake completed | 430 ms |
| 2 days ago | Handshake completed | 268 ms |
| 3 days ago | Handshake completed | 270 ms |
| 4 days ago | Handshake completed | 297 ms |
| 5 days ago | Handshake completed | 319 ms |
| 7 days ago | Handshake completed | 464 ms |
| 10 days ago | Handshake completed | 623 ms |
| 12 days ago | Handshake completed | 343 ms |
| 15 days ago | Handshake completed | 435 ms |
| 17 days ago | Handshake completed | 287 ms |
| 19 days ago | Handshake completed | 289 ms |
| 21 days ago | Handshake completed | 354 ms |
| 23 days ago | Handshake completed | 319 ms |
| 25 days ago | Handshake completed | 552 ms |
| 26 days ago | Handshake completed | 421 ms |
| 28 days ago | Handshake completed | 44 ms |
| 29 days ago | Handshake completed | 294 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 app.surewhynot.quartermaster/quartermaster and makes no claim about it beyond what these checks measured.