Remote MCP · Endpoint

SoleScout MCP server

No. SoleScout answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://solescout.ai/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyberLdy/solescout
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
128 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live sneaker & streetwear prices and in-stock sizes across 600+ US stores, by style code.
Listing
From the official MCP registry (active).
Recent checks of SoleScout
CheckedResultHandshake
2 hours agoHandshake completed128 ms
10 days agoHandshake completed187 ms
11 days agoHandshake completed161 ms
11 days agoHandshake completed354 ms
13 days agoHandshake completed149 ms
14 days agoHandshake completed143 ms
15 days agoHandshake completed117 ms
16 days agoHandshake completed232 ms
17 days agoHandshake completed139 ms
19 days agoHandshake completed143 ms
22 days agoHandshake completed172 ms
24 days agoHandshake completed274 ms
26 days agoHandshake completed152 ms

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

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