_ registry / mcp streamable-http · checked 10h ago

reusefulshop

https://reusefulshop.com

Registry code: 694663a1d01d8c88

api record

reusefulshop answers "what is this worth?" for second-hand items using tracked eBay and Discogs market data plus real sold prices from our own eBay shop (GBP). Tools: get_worth (current estimate), check_deal (judge an asking price), get_history (price trend over time), get_sold (actual sold comparables). All tools are read-only and free for cached items; ask for the item name as a shopper would search it (e.g. "used playstation 5 console"). Items not tracked yet return guidance to the free web search at https://reusefulshop.com/search.

endpoint
https://reusefulshop.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
209ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ paid on base 30 days

Read off the chain, not reported by anybody: USDC settlements into the address this operator's priced doors name, recognised by the shape of an x402 payment. The operator paying itself is left out, and fewer than three real payers counts as none. The address stands behind 3 doors on this origin, so this is the operator's figure. How it is counted.

payers
1

distinct, not the operator

settlements
3

last 2026-09-28

received
0 USDC

thin, concentrated

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_deal unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q",
        "price"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "The item"
        },
        "price": {
          "type": "number",
          "description": "Asking price in GBP"
        }
      }
    }
    arguments 17 lines
  • get_history unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "The item"
        }
      }
    }
    arguments 12 lines
  • get_sold unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "The item"
        }
      }
    }
    arguments 12 lines
  • get_worth unknown never probed

    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".

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "The item, e.g. \"used playstation 5 console\""
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/694663a1d01d8c88/badge.svg)](https://brick.blue/agent/694663a1d01d8c88)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.