eCommerce
pulltrader.app
Analyzes and compares selling costs and fees for trading cards across various online marketplaces to help sellers optimize their profits.
ENDPOINT 1
https://mcp.pulltrader.app/mcp
MCP server metadata
- Name
- pulltrader-mcp
- Version
- 0.4.0
Scout's trading-card intelligence tools. Card research: identify_card resolves a text description into structured fields; search_card_sales returns recent comparable sold sales; summarize_card_market gives median/percentile/volatility market value; get_card_price_history returns a price-over-time series. Seller economics: compare_selling_costs estimates what a seller keeps across eBay and Pulltrader methods; calculate_required_sale_price solves for the price to hit a target net; explain_selling_method describes how each method charges fees. All market figures are estimates from recent sales (excluding fees/taxes/shipping) and are not financial advice; never claim guaranteed value or one platform as universally cheapest. Trading cards only.
Known tools 7
compare_selling_costsCompare 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).
Inferred read-onlycalculate_required_sale_priceGiven 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).
Inferred read-onlyexplain_selling_methodReturn 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.
Inferred read-onlyidentify_cardResolve a natural-language trading-card description into structured fields (player/athlete, year, set, card number, parallel, grader, grade, sport/category).
Inferred read-onlysearch_card_salesReturn a capped sample of recent comparable SOLD listings for a trading card (price + sale date), plus a market snapshot (median, range, sample size).
Inferred read-onlysummarize_card_marketReturn 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.
Inferred read-onlyget_card_price_historyReturn 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.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pulltrader-mcp]
url = "https://mcp.pulltrader.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pulltrader-mcp": {
"type": "http",
"url": "https://mcp.pulltrader.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pulltrader-mcp
Remote MCP URL: https://mcp.pulltrader.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pulltrader-mcp": {
"url": "https://mcp.pulltrader.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pulltrader-mcp": {
"type": "http",
"url": "https://mcp.pulltrader.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pulltrader-mcp",
"transport": "streamable-http",
"url": "https://mcp.pulltrader.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.