SoldStack MCP server
io.github.aar-ont/soldstackaar-ontstreamable-httpv1.3.0Scanned
Cleaned sold prices for used clothing, shoes and bags: Poshmark US and Canada.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SoldStack MCP server can do
The SoldStack MCP server is published by the GitHub account aar-ont. It has 3 tools. It can create or change data (2 tools: sold_comps and buy_or_pass), but cannot delete data. 1 tool only reads.
3 tools bring in text other people can write (sold_comps, buy_or_pass and value_donation_list).
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
buy_or_passWhether an item is worth buying at a given cost to resell on Poshmark: buy, maybe or pass with the reason, judged from its clean sold comps after Poshmark's fee.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Whether an item is worth buying at a given cost to resell on Poshmark: buy, maybe or pass with the reason, judged from its clean sold comps after Poshmark's fee. Call it for one item at a time; if it reports busy, wait the given number of seconds and call again. query: brand + item, e.g. "patagonia better sweater". cost: what you'd pay, e.g. the thrift-store tag price, in the same currency as source (USD for poshmark, CAD for poshmark_ca). min_profit: smallest profit after fees worth the effort (default 10). size / condition: same filters as sold_comps. source: "poshmark" (US, default) or "poshmark_ca" (Poshmark Canada; prices and fees in CAD).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
sold_compsWhat an item actually sold for on Poshmark: median sold price, typical range (p10-p90), days to sell, what the seller keeps after fees, price by condition, a confidence rating, and…Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,468 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...US, default) or "poshmark_ca" (Poshmark Canada; prices and fees in CAD)."
Description, as the server wrote it What an item actually sold for on Poshmark: median sold price, typical range (p10-p90), days to sell, what the seller keeps after fees, price by condition, a confidence rating, and the matching sales. Call it for one item at a time; if it reports busy, wait the given number of seconds and call again. query: brand + item, e.g. "coach tabby 26" or "lululemon align leggings", or a plain item type like "womens jeans". For kids' clothing put girls, boys, kids, toddler or youth in the query ("girls jeans"); otherwise kids' sizes are removed. size: only this size, e.g. "8", "M" or "10.5". Leave it out unless the user named a size: it can leave very few sales. condition: "new", "used", a plain word (nwt, like new, excellent, very good, good, fair, poor), or an exact grade: new_with_tags, not_new_with_tags, used_like_new, used_excellent, used_good, used_fair (comma-separated for several). days: only sales from the last N days (1-365). Poshmark lists sold results by relevance, not date, so without it the sales can be years old; days=365 (or 90) keeps prices recent. limit: how many individual sales to include in `sales` (default 10, 0-50). Each sale has the same fields as a /v1/sold item. exclude_seller: comma-separated seller usernames to leave out (case-insensitive). sort: order of the included sales: "recent" (newest first), "price_asc" or "price_desc". Stats are unaffected. department: comma-separated: Women, Men, Kids, Home, Pets, Electronics. "Kids" also keeps kids' sizes, and adds "kids" to a query with no kids' word ("snow pants" searches "kids snow pants"; query_note says so). category: comma-separated Poshmark categories, e.g. "Jeans". kids_age: only kids' sales in "baby" (0-24 months), "toddler" (2T-5T) or "big_kids" (4/5 and up) sizes. Kids' searches otherwise keep 12-24 month and toddler sizes, as Poshmark's Kids department does. include_removed: true also returns removed_items, the sales cleaning dropped, each with a removed_reason. deep: true reads up to ~190 sales (4 pages of up to 48, in Poshmark's relevance order) instead of one page (slower when not cached, about 10s; one lookup). source: "poshmark" (US, default) or "poshmark_ca" (Poshmark Canada; prices and fees in CAD).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
Only reads 1Show 1 read-only tool
value_donation_listFair-market values for a whole donation list (clothing, shoes, bags and household goods: kitchen, home, electronics, media, toys, baby gear, pets, beauty), each item with the Poshm…Reads text others write1 finding
Why it is in this group
- The name "value_donation_list" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 3,498 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ingle item, or a group of similar items (same category), is over $5,000."
Description, as the server wrote it Fair-market values for a whole donation list (clothing, shoes, bags and household goods: kitchen, home, electronics, media, toys, baby gear, pets, beauty), each item with the Poshmark sales behind it, a list total and a dated method paragraph the donor can keep with their records. One call values up to 100 items and costs one lookup per item. Call it once with the whole list, not once per item. items: a list of objects, one per item. Only description is required. description: what it is, as the donor would say it: "womens handbag", "mens suit", "kids snow pants", "Levi's 501 jeans", "KitchenAid stand mixer". Put brand and model in brand or description. Goods are valued only from sales of the same product, so name it as it would be listed; a count in the text ("throw pillows (4)") is read as the quantity. brand: optional, e.g. "Coach". With a brand the item is priced from that brand's own sales when enough are saved, else from its category. condition: optional. new_with_tags, used_like_new, used_excellent, used_good, used_fair, a plain word (like new, good, fair), or new or used. Default used, which is right for most donations. category, department, size: optional; read from the description when left out. A kids' size such as "4T" marks the item as kids'. kids_age: optional, for kids' items: "baby" (0-24 months), "toddler" (2T-5T) or "big_kids" (4/5 and up). quantity: optional, default 1. total is value times quantity. source: "poshmark" (US, USD, default) or "poshmark_ca" (Poshmark Canada, CAD). examples_per_item: how many of the sales behind each value to include (0-5, default 2). Each has a title, price, sold date and link. days: only sales from the last N days (1-3650); 365 is the last 12 months. Default: every sale. sold_after, sold_before: only sales sold on or after / on or before these dates (YYYY-MM-DD). On the Free, pass and Starter plans every value uses only sales from the last 90 days (any window is cut to it, history_days is 90 and history_note says so), except keys issued before Oct 25 2026, which keep the full archive (history_days is null); Growth and Scale use the full archive, back to 2012. Each item gets value (the median sold price), low and high (the 25th and 75th percentiles), p10 and p90 (the 10th and 90th), sales_used, oldest_sold and newest_sold (within the window), matched_on ("brand + item", "item description", "category + department" or "category, all departments"), broadened (true when the value comes from wider sales than the item as described: no brand match, a description reduced to its category, all departments, or the condition group instead of the exact grade), condition_matched (the grade or group the sales are in), by_condition (median and range per grade), a confidence rating and a reason that says why. basis is the older name of matched_on. An item with nothing to go on has value null and a reason; never guess a value for it. The list has total, items_valued, method and disclaimer. This is resale market data, not tax or legal advice; appraisal_may_be_needed is true when a single item, or a group of similar items (same category), is over $5,000.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:01 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://soldstack.dev/mcp: tools/list returned 3 tools to an anonymous client, including sold_comps (write), buy_or_pass (write)
Findings
Matches of fixed checks, with the text they matched.
- Infosold_comps
The description is 2,468 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...US, default) or "poshmark_ca" (Poshmark Canada; prices and fees in CAD)."
The description is 3,498 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ingle item, or a group of similar items (same category), is over $5,000."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:value_donation_listOnly readsdescription
Tools3 changed.~3 changedView diff
- Changed:buy_or_passChanges thingsdescription
- Changed:sold_compsChanges thingsdescription
- Changed:value_donation_listOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:buy_or_passChanges thingsdescription
- Changed:sold_compsChanges thingsdescription
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http soldstack https://soldstack.dev/mcp --header 'X-API-Key: <your-x-api-key>'claude mcp add --transport http soldstack https://soldstack.dev/mcp --header 'X-API-Key: <your-x-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__soldstack__value_donation_list"
],
"ask": [
"mcp__soldstack__sold_comps",
"mcp__soldstack__buy_or_pass"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as soldstack. Review it before you use it.
Capability tags behind 3 rules
- mcp__soldstack__sold_comps untrusted-input
- mcp__soldstack__buy_or_pass untrusted-input
- mcp__soldstack__value_donation_list untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.aar-ont/soldstack/verify?hash=edae54d44bd45f29de17b9b4e1d785f69540d9aef22c64c4d2c9ddf48b88a4cc" | jq -e '.changed == false'Pinned hash edae54d44bd4, from Nov 9, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.aar-ont/soldstack/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.aar-ont/soldstack)Source: MCP Registry. Synced Oct 25, 2026, 05:17 UTC.
SoldStack MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SoldStack MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SoldStack MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SoldStack MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SoldStack MCP server have?
- 3 tools: 2 write, 1 read. sold_comps, buy_or_pass and value_donation_list.
Does the SoldStack MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SoldStack MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SoldStack MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.