Pulltrader Seller Economics
REMOTE · MCP.PULLTRADER.APP · SCANNED AUG 3
Compare what a trading-card seller keeps across eBay, Pulltrader, and other card marketplaces.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2263 tokens (~323/item across 7 items; 7 tools + 0 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.pulltrader.app
claude mcp add --transport http app-pulltrader-seller-economics https://mcp.pulltrader.app/mcp
[mcp_servers.app-pulltrader-seller-economics] url = "https://mcp.pulltrader.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-pulltrader-seller-economics": {
"type": "remote",
"url": "https://mcp.pulltrader.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-pulltrader-seller-economics --url https://mcp.pulltrader.app/mcp --transport streamable-http
mcp_servers:
app-pulltrader-seller-economics:
url: "https://mcp.pulltrader.app/mcp" {
"mcpServers": {
"app-pulltrader-seller-economics": {
"type": "http",
"url": "https://mcp.pulltrader.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
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 3 Aug 2026 · Probed https://mcp.pulltrader.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pulltrader.app | CN=WE1,O=Google Trust Services,C=US | 27 Jun 2026 | 25 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | d5089440e5a2fe3113b3d086371597b0 |
| SANs: pulltrader.app, mcp.pulltrader.app, *.mcp.pulltrader.app | ||||||
| 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 |
DNSSEC insecure
Validation of mcp.pulltrader.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| pulltrader.app. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pulltrader.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.pulltrader.app/mcp | HTTPS enforced | 301 | https://mcp.pulltrader.app/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.
calculate_required_sale_price Find the sale price needed to reach a target net payout ~551
Given a target take-home amount, compute the per-item sale price a trading-card seller must list at to net that amount on ONE selling method, after fees — eBay (estimated), a Pulltrader selling method (marketplace, Fulfilled by Pulltrader, branded storefront, in-person POS), or an estimated competitor marketplace (TCGplayer, Mana Pool, Misprint, Fanatics Collect, Goldin). If acquisition_cost is supplied, the target is treated as net profit (payout minus what you paid); otherwise it is the take-home payout. Use this when a seller asks 'what do I need to list this at to walk away with $X', 'to net/profit $X after fees', or 'to break even'. Calculations are deterministic and use dated fee schedules. Do NOT use this to look up a card's market value or recent sales (this tool does not price cards), and do NOT use it for non-trading-card categories. Present eBay and competitor figures as estimates, never as guaranteed proceeds.
| Name | Type | Req | Description |
|---|---|---|---|
| acquisition_cost | number | — | Optional. What the seller paid for the card. When supplied, target_net is interpreted as net profit (payout minus this cost). |
| currency | string | — | ISO currency code. Only USD is supported. |
| ebay_fee_percent_override | number | — | Optional. Override the estimated eBay final value fee percentage. |
| ebay_store_subscription | boolean | — | If true, estimate eBay fees using the eBay Store subscriber rate instead of the individual rate. |
| item_category | string | — | Item category. Only trading_cards is supported. |
| method | string | — | The single selling method to solve for. One of: ebay, pulltrader_marketplace, pulltrader_fbp, pulltrader_storefront, pulltrader_pos, tcgplayer, manapool, misprint, fanatics_collect, goldin. |
| quantity | integer | — | Number of identical items in one order. Per-order fixed fees are applied once. |
| seller_covers_fees | boolean | — | If true, the seller absorbs the Pulltrader platform fee (3.25% + $0.40). If false (default), the buyer pays it at checkout. |
| seller_plan | string | — | Pulltrader seller plan. Determines the marketplace payout tier (free=91%, starter=93%, pro=94%, shop=95%). |
| shipping_amount | number | — | Shipping amount charged to the buyer. Affects eBay's fee base. |
| target_net | number | yes | The amount the seller wants to keep per item after fees. Net profit if acquisition_cost is supplied, otherwise take-home payout. |
No output schema declared.
No examples provided.
compare_selling_costs Compare trading-card seller proceeds across selling methods ~617
Compare estimated fees and the net amount a trading-card seller keeps when selling the SAME card across eBay (estimated), Pulltrader selling methods (marketplace, Fulfilled by Pulltrader, branded storefront, and in-person POS), and other marketplaces (TCGplayer, Mana Pool, Misprint, Fanatics Collect, Goldin — estimated fixed-price/Buy Now seller fees). Use this when a seller asks what they would keep/net/take-home on a sale, how fees compare between platforms, or which method leaves them with more money. Calculations are deterministic and use dated fee schedules. Competitor marketplaces are off by default; include them via the `methods` field. Only fixed-price seller fees are modeled — auction formats (hammer price, buyer's premium, negotiated consignment) are not. Do NOT use this to look up a card's market value or recent sales (this tool does not price cards), and do NOT use it for non-trading-card categories. Present competitor and eBay figures as estimates, never as guaranteed proceeds, and never claim one platform is universally cheapest.
| Name | Type | Req | Description |
|---|---|---|---|
| acquisition_cost | number | — | Optional. What the seller paid for the card; used to estimate net profit per method. |
| currency | string | — | ISO currency code. Only USD is supported. |
| ebay_fee_percent_override | number | — | Optional. Override the estimated eBay final value fee percentage (e.g. for a seller with an eBay Store subscription). |
| ebay_store_subscription | boolean | — | If true, estimate eBay fees using the eBay Store subscriber rate (12.35% up to $2,500/item) instead of the individual rate (13.25% up to $7,500/item). |
| item_category | string | — | Item category. Only trading_cards is supported. |
| methods | array | — | Which selling methods to compare. Defaults to eBay, Pulltrader marketplace, and Pulltrader storefront. Other supported methods (off by default): pulltrader_fbp, pulltrader_pos, and estimated competit… |
| quantity | integer | — | Number of identical items in one order. Per-order fixed fees are applied once. |
| sale_price | number | yes | The per-item sale price (the card's listed/sold price), in the given currency. |
| seller_covers_fees | boolean | — | If true, the seller absorbs the Pulltrader platform fee (3.25% + $0.40). If false (default), the buyer pays it at checkout. The platform fee is always charged on Pulltrader card sales regardless. |
| seller_plan | string | — | Pulltrader seller plan. Determines the marketplace payout tier (free=91%, starter=93%, pro=94%, shop=95%). |
| shipping_amount | number | — | Shipping amount charged to the buyer. Affects eBay's fee base. See assumptions for how each method treats shipping. |
No output schema declared.
No examples provided.
explain_selling_method Explain how a supported selling method works and what fees apply ~224
Return a plain, structured explanation of one or more supported trading-card selling methods: who owns the listing, who fulfills, where it sells, the fee components that apply, and important caveats. Covers eBay (estimated), Pulltrader marketplace, Fulfilled by Pulltrader, branded storefront, in-person POS, and estimated competitor marketplaces (TCGplayer, Mana Pool, Misprint, Fanatics Collect, Goldin). Use this when a seller asks how a method works, what fees a platform charges, or how Pulltrader selling options differ. Do NOT use this to compute a specific payout (use compare_selling_costs) or the price needed for a target net (use calculate_required_sale_price), and do NOT use it to price cards.
| Name | Type | Req | Description |
|---|---|---|---|
| methods | array | — | Which selling methods to explain. Defaults to all supported methods: ebay, pulltrader_marketplace, pulltrader_fbp, pulltrader_storefront, pulltrader_pos, tcgplayer, manapool, misprint, fanatics_colle… |
No output schema declared.
No examples provided.
get_card_price_history Get the price history time series for a trading card ~211
Return a chart-ready price-history series for a trading card, aggregated from recent comparable sold sales into day/week/month buckets with a median per bucket and an overall trend. Use this when a user asks 'how has the price changed', 'price over time', 'is it trending up or down', or wants a chart. Accepts a natural-language `query` or a structured `item`. Series is built from sold-sale samples (and vendor TCG history when available); estimates only, not financial advice. Trading cards only.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | — | Bucket size for the series. Defaults to week. |
| item | object | — | Structured card fields (alternative to query): player_athlete, year_manufactured, set_name, card_number, parallel_variety, grader, grade, sport. |
| query | string | — | Natural-language card description, e.g. '2023 Panini Prizm Victor Wembanyama #136 Silver PSA 10'. Either query or item is required. |
No output schema declared.
No examples provided.
identify_card Identify a trading card from a text description ~128
Resolve a natural-language trading-card description into structured fields (player/athlete, year, set, card number, parallel, grader, grade, sport/category). Use this first when a user names a card in prose and you need its canonical fields before looking up sales or market value. Returns a confidence level and which fields were resolved. This does NOT price the card or return sales — use search_card_sales or summarize_card_market for that. Trading cards only.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The card description to identify, e.g. '2018 Prizm Luka Doncic Silver PSA 10'. |
No output schema declared.
No examples provided.
search_card_sales Find recent comparable sold sales for a trading card ~204
Return a capped sample of recent comparable SOLD listings for a trading card (price + sale date), plus a market snapshot (median, range, sample size). Use this when a user asks 'what is this card selling for', 'recent sales', or 'comps'. Accepts a natural-language `query` or a structured `item`. Figures are estimates from recent sales and exclude fees/taxes/shipping; this is not financial advice and does not place orders. Trading cards only.
| Name | Type | Req | Description |
|---|---|---|---|
| item | object | — | Structured card fields (alternative to query): player_athlete, year_manufactured, set_name, card_number, parallel_variety, grader, grade, sport. |
| limit | integer | — | Maximum number of example sales to return (1–10). |
| query | string | — | Natural-language card description, e.g. '2023 Panini Prizm Victor Wembanyama #136 Silver PSA 10'. Either query or item is required. |
No output schema declared.
No examples provided.
summarize_card_market Summarize the current market for a trading card ~187
Return a canonical market summary for a trading card from recent comparable sales: median, mean, 10th–90th percentile range, volatility, and a confidence level based on sample size and dispersion. Use this when a user asks 'what's it worth', 'market value', or 'how volatile is this card'. Accepts a natural-language `query` or a structured `item`. Estimates from recent sales, excluding fees/taxes/shipping; not financial advice. Trading cards only.
| Name | Type | Req | Description |
|---|---|---|---|
| item | object | — | Structured card fields (alternative to query): player_athlete, year_manufactured, set_name, card_number, parallel_variety, grader, grade, sport. |
| query | string | — | Natural-language card description, e.g. '2023 Panini Prizm Victor Wembanyama #136 Silver PSA 10'. Either query or item is required. |
No output schema declared.
No examples provided.