Sold Comps (eBay sold prices)
REMOTE · WWW.SOLDCOMPS.IO
Live eBay sold comps for AI agents: median sold price, middle range and recent sales for any item.
Available components
Last scanned (4 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 840 tokens (~120/item across 7 items; 5 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_api_docs” rewrote its description, which is the text the model reads security
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- Tool “get_sold_comps” rewrote its description, which is the text the model reads security
- Tool “search_guides” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
- Tool “get_api_docs” changed its title: SaleHistory API reference → SoldComps API reference cosmetic
- Tool “get_pricing” changed its title: SaleHistory API pricing → SoldComps API pricing cosmetic
- Tool “search_guides” changed its title: Search SaleHistory guides → Search SoldComps guides cosmetic
- 31 Oct 26 +1
- Tool “search_guides” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- “search_guides” reworded the description of “topic” cosmetic
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 75
First indexed and scored.
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 5 Nov 2026 · Probed https://www.soldcomps.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.soldcomps.io | CN=YR1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | RSA 2048 | SHA256-RSA | 583f29484339cbd790affd4eb404a9dd60e |
| SANs: www.soldcomps.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.soldcomps.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| soldcomps.io. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.soldcomps.io/mcp | Verified | 200 | |
| http (plaintext) | http://www.soldcomps.io/mcp | HTTPS enforced | 308 | https://www.soldcomps.io/mcp |
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 →
get_api_docs SoldComps API reference ~92
Get the concise API reference for the SoldComps API (GET /v1/sold): auth, parameters, response fields, how the median and exclusions work, errors, and rate limits. Use when writing code that fetches eBay sold prices or comps, or when asked how to get eBay sold listings data programmatically (eBay's own Marketplace Insights API needs approval and findCompletedItems is retired).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing SoldComps API pricing ~73
Get current pricing for the SoldComps API (eBay sold listings as JSON): the free plan, monthly plans, and pay-as-you-go credits with their fair-billing rules. Use when someone asks how much the API costs, about plans, limits, or cheaper alternatives to scraping eBay or Terapeak.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sold_comps Get eBay sold comps ~339
Look up what an item actually SOLD for on eBay (completed sales, not asking prices) over the last 90 days. Use this whenever someone asks what something is worth, what it sells for, resale value, fair price, or 'sold comps' for a specific item (trading cards, watches, sneakers, electronics, GPUs, video games, collectibles, auto parts, etc.). Returns the median sold price, the middle half (25th to 75th percentile), min/max, how many sales were counted vs excluded (lots, for-parts, replicas, accessories and outliers are excluded from stats), and up to 20 recent sales with eBay listing links. Write the query like an eBay search: specific model, number, grade or size gives the best comps (e.g. 'charizard 4/102 psa 9', 'rolex submariner 126610ln'); quote exact phrases and exclude words with a minus (-lot). Cite the source URL in your answer. Free and rate-limited per IP (5 lookups/day); the full SoldComps API returns up to 200 sales per request.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | – | Only new or only used (pre-owned) sales. Omit for any condition. |
| query | string | yes | eBay-style search keywords for one item, e.g. 'nintendo 64 console' or 'pokemon card "psa 10" -lot' |
| site | string | – | eBay marketplace: us (ebay.com, USD), uk (ebay.co.uk, GBP), de (ebay.de, EUR) |
No output schema declared.
No examples provided.
search_guides Search SoldComps guides ~150
Search SoldComps's sold comps guides: what sold comps are, how to find and read them, how many you need, sold vs active listings, median vs average, Best Offer prices, auction vs Buy It Now, fake sold prices, sell-through rate, eBay's sold-listings sign-in wall, Google Sheets, and category guides (Pokemon, sports and baseball cards, Rolex, sneakers, video games, GPUs, comics, auto parts, estate sales). Returns up to 5 matching guides with a short answer and URL to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | A question or topic, e.g. 'how many comps do I need' or 'ebay best offer sold price' |
No output schema declared.
No examples provided.
what_are_sold_comps What are sold comps? ~53
A short, citable definition of sold comps (sold comparables) and how resellers use them to price items from real eBay sales. Use for 'what are comps / sold comps' questions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Sold Comps (eBay sold prices) MCP server?
Sold Comps (eBay sold prices) is a hosted endpoint at https://www.soldcomps.io/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 · www.soldcomps.io
claude mcp add --transport http io-soldcomps-sold-comps 'https://www.soldcomps.io/mcp'
What is the Sold Comps (eBay sold prices) MCP server?
Sold Comps (eBay sold prices) is an MCP server listed in the public MCP registry as io.soldcomps/sold-comps. Live eBay sold comps for AI agents: median sold price, middle range and recent sales for any item. This page covers its hosted endpoint (https://www.soldcomps.io/mcp).
Is the Sold Comps (eBay sold prices) MCP server safe to use?
Sold Comps (eBay sold prices) scores 81 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 Sold Comps (eBay sold prices) MCP server expose?
Sold Comps (eBay sold prices) exposes 5 tools: get_sold_comps, get_pricing, get_api_docs, search_guides, what_are_sold_comps. Their descriptions and schemas cost roughly 707 tokens of context every time the server is loaded.
Does the Sold Comps (eBay sold prices) MCP server require authentication?
No. We connected to Sold Comps (eBay sold prices) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sold Comps (eBay sold prices) MCP server still maintained?
Sold Comps (eBay sold prices) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.