Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Auricah1/reusefulshop

REMOTE · REUSEFULSHOP.COM

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

Available components

0 this week 80 Trust /100

Last scanned (22 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability85
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 420 tokens (~105/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_deal” rewrote its description, which is the text the model reads security
    • Tool “get_history” rewrote its description, which is the text the model reads security
    • Tool “get_sold” rewrote its description, which is the text the model reads security
    • Tool “get_worth” rewrote its description, which is the text the model reads security
    • Schema quality: 51 → 105 ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://reusefulshop.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=reusefulshop.com CN=WE1,O=Google Trust Services,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA256 7af2c61e67ac718c1381d3b85bf7819f
SANs: reusefulshop.com, www.reusefulshop.com, *.www.reusefulshop.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of reusefulshop.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
reusefulshop.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://reusefulshop.com/mcp Verified 200
http (plaintext) http://reusefulshop.com/mcp HTTPS enforced 301 https://reusefulshop.com/mcp
MCP tools · 4 exposed · ~292 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_deal ~88

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.

NameTypeReqDescription
pricenumberyesAsking price in GBP
qstringyesThe item

No output schema declared.

No examples provided.

get_history ~58

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.

NameTypeReqDescription
qstringyesThe item

No output schema declared.

No examples provided.

get_sold ~63

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.

NameTypeReqDescription
qstringyesThe item

No output schema declared.

No examples provided.

get_worth ~83

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

NameTypeReqDescription
qstringyesThe item, e.g. "used playstation 5 console"

No output schema declared.

No examples provided.

Install

How do I install the io.github.Auricah1/reusefulshop MCP server?

io.github.Auricah1/reusefulshop is a hosted endpoint at https://reusefulshop.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · reusefulshop.com

# add to Claude Code
claude mcp add --transport http auricah1-reusefulshop 'https://reusefulshop.com/mcp'
Common questions

What is the io.github.Auricah1/reusefulshop MCP server?

io.github.Auricah1/reusefulshop is an MCP server listed in the public MCP registry as io.github.Auricah1/reusefulshop. Live second-hand price estimates with confidence for AI agents. Cached lookups free. This page covers its hosted endpoint (https://reusefulshop.com/mcp).

Is the io.github.Auricah1/reusefulshop MCP server safe to use?

io.github.Auricah1/reusefulshop scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Auricah1/reusefulshop MCP server expose?

io.github.Auricah1/reusefulshop exposes 4 tools: get_worth, check_deal, get_history, get_sold. Their descriptions and schemas cost roughly 292 tokens of context every time the server is loaded.

Does the io.github.Auricah1/reusefulshop MCP server require authentication?

No. We connected to io.github.Auricah1/reusefulshop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.Auricah1/reusefulshop MCP server still maintained?

io.github.Auricah1/reusefulshop is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.Auricah1/reusefulshop MCP server?

VerifyMCP ran 12 checks on io.github.Auricah1/reusefulshop, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.Auricah1/reusefulshop: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.