Remote MCP · Endpoint

io.github.Auricah1/reusefulshop MCP server

No. io.github.Auricah1/reusefulshop answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://reusefulshop.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Auricah1/reusefulshop
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
693 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Live second-hand price estimates with confidence for AI agents. Cached lookups free.
Listing
From the official MCP registry (active).
Recent checks of io.github.Auricah1/reusefulshop
CheckedResultHandshake
1 day agoHandshake completed693 ms
3 days agoHandshake completed217 ms
5 days agoHandshake completed361 ms
7 days agoHandshake completed181 ms
9 days agoHandshake completed205 ms
11 days agoHandshake completed34 ms
12 days agoHandshake completed68 ms
13 days agoHandshake completed339 ms
15 days agoHandshake completed47 ms
17 days agoHandshake completed38 ms
19 days agoHandshake completed36 ms
21 days agoHandshake completed165 ms
22 days agoHandshake completed138 ms
23 days agoHandshake completed111 ms

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

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 io.github.Auricah1/reusefulshop and makes no claim about it beyond what these checks measured.