Remote MCP · Endpoint

NOSTOS MCP server

No. NOSTOS answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.nostos.market/mcp

The last check completed an MCP handshake.

Registry name
market.nostos/nostos
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
438 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Retro games and vintage apparel in Duluth, GA. Live catalog, prices, trade-in offers, policies.
Listing
From the official MCP registry (active).
Recent checks of NOSTOS
CheckedResultHandshake
1 hour agoHandshake completed438 ms
2 days agoHandshake completed642 ms
4 days agoHandshake completed489 ms
5 days agoHandshake completed528 ms
7 days agoHandshake completed583 ms
8 days agoHandshake completed703 ms
9 days agoHandshake completed676 ms
12 days agoHandshake completed514 ms
13 days agoHandshake completed470 ms
15 days agoHandshake completed502 ms
17 days agoHandshake completed468 ms
18 days agoHandshake completed422 ms
19 days agoHandshake completed544 ms
20 days agoHandshake completed517 ms
21 days agoHandshake completed560 ms
21 days agoHandshake completed709 ms
23 days agoHandshake completed541 ms

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

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