reusefulshop

Live second-hand price estimates with confidence for AI agents. Cached lookups free.

Should I use this

Quality & Safety

A
Description quality
95%
Schema completeness
100%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~389Tokens (tool definitions)
~368 BTypical response size
Minimal attention impact (0.30% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "reusefulshop": {
      "url": "https://reusefulshop.com/mcp"
    }
  }
}

Remote endpoints

https://reusefulshop.com/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_worth(q)

Use for a current second-hand value check: returns low/typical/high price estimate plus confidence for an item, from tracked eBay/Discogs marketplace data in GBP. Read-only and free for cached items. Example: q="used playstation 5 console".

Input Schema

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "The item, e.g. \"used playstation 5 console\""
    }
  },
  "required": [
    "q"
  ]
}
🟢check_deal(q, price)

Use when the user has a specific asking price to judge: compares it with the tracked market range and returns a verdict (great deal, good deal, fair price, above average, overpriced). Read-only and free. Example: q="iphone 13 128gb used", price=320.

Input Schema

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "The item"
    },
    "price": {
      "type": "number",
      "description": "Asking price in GBP"
    }
  },
  "required": [
    "q",
    "price"
  ]
}
🟢get_history(q)

Use for price trends over time: returns tracked daily price snapshots for an item (history starts when tracking began and may be short). Read-only and free. For a single current value prefer get_worth.

Input Schema

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "The item"
    }
  },
  "required": [
    "q"
  ]
}
🟢get_sold(q)

Use for real completed transactions: returns median/low/high sold prices from the operator's own eBay shop. Read-only and free. Prefer this for actual sold comparables; get_worth is for live asking-price estimates.

Input Schema

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "The item"
    }
  },
  "required": [
    "q"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools