Pulltrader
REMOTE · MCP.PULLTRADER.APP
Trading-card research and seller economics: identify cards, check sold comps, and compare fees.
Available components
Last scanned (10 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 22 Oct 26 +2
No change was recorded against any check on this day. Endpoint Security went from 91 to 94.
- 13 Oct 26 −41
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 12 Oct 26 −1
- A breaking change shipped without a version bump: still 0.6.2 ▼ security
- Tool “check_kapture_cert” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “calculate_required_sale_price” rewrote its description, which is the text the model reads security
- Tool “get_card_price_history” rewrote its description, which is the text the model reads security
- Tool “search_card_sales” rewrote its description, which is the text the model reads security
- Tool “summarize_card_market” rewrote its description, which is the text the model reads security
- Schema quality: 319 → 437 ▼ functional
- New tool “check_stolen_card” functional
- “calculate_required_sale_price” added an optional parameter “shipping_cost” cosmetic
- “calculate_required_sale_price” reworded the description of “acquisition_cost” cosmetic
- “calculate_required_sale_price” reworded the description of “target_net” cosmetic
- 10 Oct 26 +44
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_card_price_history” rewrote its description, which is the text the model reads security
- Tool “summarize_card_market” rewrote its description, which is the text the model reads security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 9 Oct 26 +1
- DNSSEC: fail → pass ▲ security
- 6 Oct 26 −44
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.6.0 → 0.6.2 functional
- “calculate_required_sale_price” reworded the description of “ebay_store_subscription” cosmetic
- “compare_selling_costs” reworded the description of “ebay_store_subscription” cosmetic
- 28 Sept 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
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://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 | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9d9101bf9037e95913f0569e30457030 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.pulltrader.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| pulltrader.app. | present | 2371 | 13 | Verified |
| mcp.pulltrader.app. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.pulltrader.app/.well-known/oauth-protected-resource/mcp", scope="collection:read collection:write research:spend seller:read"
Bearer resource_metadata="https://mcp.pulltrader.app/.well-known/oauth-protected-resource/mcp", scope="collection:read collection:write research:spend seller:read"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.pulltrader.app/.well-known/oauth-protected-resource/mcp", scope="collection:read collection:write research:spend seller:read" |
Protected resource metadata
| Document | https://mcp.pulltrader.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.pulltrader.app/mcp |
| Authorisation server | https://auth.pulltrader.app/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pulltrader.app/mcp | Auth required | 401 | |
| 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. 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 →
calculate_required_sale_price Find the sale price needed to reach a target net payout ~708
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 shipping_cost for actual seller postage, separate from shipping_amount charged to the buyer. Never adjust target_net to account for postage yourself. 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. Total acquisition cost of the cards in this order. 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 Basic-or-higher 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_level | integer | – | The seller's actual level (1-5), if known. Level is set from plan AND sales volume, so levels 2 and 4 exist only by earning them and cannot be inferred from a plan. Overrides the plan's rate: 1=91%,… |
| seller_plan | string | – | Pulltrader seller plan. Sets the payout floor (free/operations=91%, business/managed=95%); a seller level earned on revenue can be higher. |
| shipping_amount | number | – | Shipping amount charged to the buyer. Affects eBay's fee base. |
| shipping_cost | number | – | Actual shipping cost paid by the seller for this order, in dollars. Deducted from payout; do not add it to target_net. |
| target_net | number | yes | The amount the seller wants to keep for the order after fees and shipping_cost. Net profit if acquisition_cost is supplied, otherwise take-home payout. |
No output schema declared.
No examples provided.
check_stolen_card Check reported stolen cards ~81
Check an exact certification number for verified stolen-card reports. Preserve leading zeros. CLEAN means no verified stolen report matched, not proof of authenticity or ownership. STOLEN includes a voluntary recovery form link. Never infer possession from a lookup or send personal details through this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| cert | string | yes | Exact cert number as a string, including leading zeros. |
No output schema declared.
No examples provided.
compare_selling_costs Compare trading-card seller proceeds across selling methods ~706
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 Basic-or-higher 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_level | integer | – | The seller's actual level (1-5), if known. Level is set from plan AND sales volume, so levels 2 and 4 exist only by earning them and cannot be inferred from a plan. Overrides the plan's rate: 1=91%,… |
| seller_plan | string | – | Pulltrader seller plan. Sets the payout floor (free/operations=91%, business/managed=95%); a seller level earned on revenue can be higher. |
| 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 ~449
Return a chart-ready price-history series for a trading card from available sold sales or daily sales-based market values, grouped into day/week/month buckets with a median and 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`. The response labels recorded sales or sales-based market values explicitly and reports sold-sale sample counts separately. Amounts are USD dollars. Trading cards only. Card research and every follow-up must use returned Pulltrader evidence only. Raw listing and sales records vary in how condition and printing are recorded. Present returned raw condition history and graded context together. Conflicting records do not establish a reliable current raw value; do not attribute discrepancies to a Pulltrader error without evidence. Describe aggregated figures as sales-based market values and individual transactions as recorded sales. Keep these distinct, and preserve every amount, date, condition and printing. Preserve the returned market interpretation. Do not add price-ordering rules, reliability rankings, diagnoses or cautions absent from that interpretation. Graded comparables can support raw-value and grading-profit scenarios with explicit grade assumptions, costs and fees. Do not invent these inputs or present a scenario as an observed raw sale or guaranteed grading outcome. Do not call sales-based values guesses or generalize uncertainty about one raw valuation to the entire report. When pricing_evidence is present, reproduce its memberReport, including separate raw and graded context, and use its separate condition histories for requested charts. Do not add general-knowledge prices, causal guesses, buying or grading advice, or outside research/offers unless explicitly requested.
| 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 ~438
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`. Values are based on recorded sales and exclude fees/taxes/shipping; this is not financial advice and does not place orders. Trading cards only. Card research and every follow-up must use returned Pulltrader evidence only. Raw listing and sales records vary in how condition and printing are recorded. Present returned raw condition history and graded context together. Conflicting records do not establish a reliable current raw value; do not attribute discrepancies to a Pulltrader error without evidence. Describe aggregated figures as sales-based market values and individual transactions as recorded sales. Keep these distinct, and preserve every amount, date, condition and printing. Preserve the returned market interpretation. Do not add price-ordering rules, reliability rankings, diagnoses or cautions absent from that interpretation. Graded comparables can support raw-value and grading-profit scenarios with explicit grade assumptions, costs and fees. Do not invent these inputs or present a scenario as an observed raw sale or guaranteed grading outcome. Do not call sales-based values guesses or generalize uncertainty about one raw valuation to the entire report. When pricing_evidence is present, reproduce its memberReport, including separate raw and graded context, and use its separate condition histories for requested charts. Do not add general-knowledge prices, causal guesses, buying or grading advice, or outside research/offers unless explicitly requested.
| 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 ~430
Return the current market estimate and available comparable-sale statistics for a trading card: 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`. Amounts are USD dollars excluding fees, taxes and shipping. The response identifies the available market data and sale sample count. Trading cards only. Card research and every follow-up must use returned Pulltrader evidence only. Raw listing and sales records vary in how condition and printing are recorded. Present returned raw condition history and graded context together. Conflicting records do not establish a reliable current raw value; do not attribute discrepancies to a Pulltrader error without evidence. Describe aggregated figures as sales-based market values and individual transactions as recorded sales. Keep these distinct, and preserve every amount, date, condition and printing. Preserve the returned market interpretation. Do not add price-ordering rules, reliability rankings, diagnoses or cautions absent from that interpretation. Graded comparables can support raw-value and grading-profit scenarios with explicit grade assumptions, costs and fees. Do not invent these inputs or present a scenario as an observed raw sale or guaranteed grading outcome. Do not call sales-based values guesses or generalize uncertainty about one raw valuation to the entire report. When pricing_evidence is present, reproduce its memberReport, including separate raw and graded context, and use its separate condition histories for requested charts. Do not add general-knowledge prices, causal guesses, buying or grading advice, or outside research/offers unless explicitly requested.
| 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.
How do I install the Pulltrader MCP server?
Pulltrader is a hosted endpoint at https://mcp.pulltrader.app/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 · mcp.pulltrader.app
claude mcp add --transport http app-pulltrader-seller-economics 'https://mcp.pulltrader.app/mcp'
What is the Pulltrader MCP server?
Pulltrader is an MCP server listed in the public MCP registry as app.pulltrader/seller-economics. Trading-card research and seller economics: identify cards, check sold comps, and compare fees. This page covers its hosted endpoint (https://mcp.pulltrader.app/mcp).
Is the Pulltrader MCP server safe to use?
Pulltrader scores 38 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 Pulltrader MCP server expose?
Pulltrader exposes 8 tools: check_stolen_card, compare_selling_costs, calculate_required_sale_price, explain_selling_method, identify_card, and 3 more. Their descriptions and schemas cost roughly 3,164 tokens of context every time the server is loaded.
Does the Pulltrader MCP server require authentication?
Yes. Pulltrader asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Pulltrader MCP server still maintained?
Pulltrader 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.