Remote MCP · Endpoint

SoldStack MCP server

No. SoldStack answered an MCP handshake 19 hours ago.

UpLast checked 19 hours ago

Server URL

https://soldstack.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.aar-ont/soldstack
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
38 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
What secondhand clothes, shoes and bags actually sold for on Poshmark, plus buy or pass verdicts.
Listing
From the official MCP registry (active).
Recent checks of SoldStack
CheckedResultHandshake
19 hours agoHandshake completed38 ms
4 days agoHandshake completed29 ms
8 days agoHandshake completed60 ms
17 days agoHandshake completed41 ms
17 days agoHandshake completed39 ms
19 days agoHandshake completed28 ms
20 days agoHandshake completed34 ms
21 days agoHandshake completed29 ms
22 days agoHandshake completed36 ms
23 days agoHandshake completed31 ms
24 days agoHandshake completed25 ms
27 days agoHandshake completed29 ms
29 days agoHandshake completed29 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 23.

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