_ registry / mcp http-sse · checked 1h ago

soldcomps

https://www.soldcomps.io

Registry code: 4dec790f31e1ec3a

api record

SaleHistory (https://www.soldcomps.io) provides live eBay sold comps: what items actually sold for in the last 90 days. Call get_sold_comps for price/value questions about a specific item and report the median with the middle-half range and sale count. Always cite the source URLs included in tool results. For developers, get_api_docs and get_pricing describe the full API (up to 200 sales per request).

endpoint
https://www.soldcomps.io/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is soldcomps live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is soldcomps free to use?
Yes — the hub reached it with no key and no payment.
What tools does soldcomps have?
5 tools: get_pricing, search_guides, get_sold_comps, what_are_sold_comps, get_api_docs.
Is soldcomps safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
320ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 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.

  • what_are_sold_comps open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_api_docs open 1h ago

    Get the concise API reference for the SaleHistory sold comps 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).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_pricing unknown never probed

    Get current pricing for the SaleHistory sold comps 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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • search_guides unknown never probed

    Search SaleHistory's guides about eBay sold prices and comps: how to read and use sold comps, pricing specific categories (Pokemon and sports cards, Rolex, GPUs, comics, auto parts), eBay sold data APIs and scraping, Best Offer prices, sell-through rate, Google Sheets and Python tutorials. Returns up to 5 matching guides with a short answer and URL to cite.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "topic"
      ],
      "properties": {
        "topic": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "A question or topic, e.g. 'how many comps do I need' or 'ebay sold listings api'"
        }
      }
    }
    arguments 15 lines
  • get_sold_comps unknown 1h ago

    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 SaleHistory API returns up to 200 sales per request.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "site": {
          "enum": [
            "us",
            "uk",
            "de"
          ],
          "type": "string",
          "default": "us",
          "description": "eBay marketplace: us (ebay.com, USD), uk (ebay.co.uk, GBP), de (ebay.de, EUR)"
        },
        "query": {
          "type": "string",
          "maxLength": 80,
          "minLength": 3,
          "description": "eBay-style search keywords for one item, e.g. 'nintendo 64 console' or 'pokemon card \"psa 10\" -lot'"
        },
        "condition": {
          "enum": [
            "new",
            "used"
          ],
          "type": "string",
          "description": "Only new or only used (pre-owned) sales. Omit for any condition."
        }
      }
    }
    arguments 33 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4dec790f31e1ec3a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4dec790f31e1ec3a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4dec790f31e1ec3a/badge.svg)](https://brick.blue/agent/4dec790f31e1ec3a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

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.