Sorsa
REMOTE · SORSA.APP
Amazon FBA arbitrage toolkit: product analysis, deal feeds, price alerts and sourcing management.
Available components
Last scanned (19 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 4 Nov 2026.
Category E-commerce
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 Security46
- 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 73 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 enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 7611 tokens (~104/item across 73 items; 73 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_fba_refunds" implies "refund" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 74 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 −1
- Schema quality: pass → fail ▼ functional
- Stability: pass → 0.97 functional
- New tool “configure_prep_sheet” functional
- New tool “get_prep_sheet_config” functional
- New tool “queue_checkout” functional
- 9 Oct 26 0
- Tool “start_a2a_finder_scan” rewrote its description, which is the text the model reads security
- Tool “start_reverse_source_scan” rewrote its description, which is the text the model reads security
- Schema quality: 5789 → 6925 ▼ functional
- New tool “get_ungate_brands” functional
- 3 Oct 26 +10
- Judged manipulation: unverified → pass ▲ security
- Schema quality: unverified → good ▲ functional
- “find_products” added an optional parameter “min_sellers” cosmetic
- 2 Oct 26 60
- Judged manipulation: pass → unverified ▼ security
- Schema quality: 5014 → 5782 ▼ functional
- Schema quality: good → unverified ▼ functional
- New tool “add_purchase” functional
- New tool “create_listing” functional
- New tool “generate_sku” functional
- New tool “get_sheet_status” functional
- New tool “run_sheet_action” functional
- New tool “set_cog” functional
- 1 Oct 26 0
- New tool “find_products” functional
- New tool “get_keepa_key_status” functional
- 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
- 25 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
- 26 Aug 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 4 Nov 2026 · Probed https://sorsa.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sorsa.app | CN=YE1,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60766d13857bbb3e63954a75d51b54758a4 |
| SANs: *.sorsa.app, sorsa.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sorsa.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| sorsa.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sorsa.app/mcp | Verified | 200 | |
| http (plaintext) | http://sorsa.app/mcp | Inconclusive | 404 |
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 →
add_purchase ~175
Add an item the user has BOUGHT to their Items Purchased list (the next step after sourcing). Returns the created item incl. its `id` — use that id with generate_sku and create_listing. cost is per unit; sourced_from is the retailer/site they bought from. projected_sale_price: default this to the product's 90-day average price (from analyse_product) and tell the user what you've set — don't guess a price. It's what create_listing will list at unless changed.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | – | – | – |
| company | – | – | – |
| cost | – | – | – |
| notes | – | – | – |
| projected_profit | – | – | – |
| projected_sale_price | – | – | – |
| quantity | integer | – | – |
| roi | – | – | – |
| sourced_from | – | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
add_storefront_monitor ~87
Start monitoring another Amazon seller's storefront — new products they list will appear in the user's store results. storefront_id is the Amazon seller ID (e.g. A1B2C3D4E5F6G7, found in the seller page URL). Call when the user says 'track this seller'.
| Name | Type | Req | Description |
|---|---|---|---|
| storefront_id | string | yes | – |
No output schema declared.
No examples provided.
add_to_sourcing_list ~133
Add a product to the user's sourcing list (their buy list). Call when the user says 'add this to my buy list' — typically after analysing a product, passing through the numbers from the analysis. sourced_from is where they'd buy it (retailer/site).
| Name | Type | Req | Description |
|---|---|---|---|
| asin | – | – | – |
| company | – | – | – |
| cost | – | – | – |
| monthly_sales | – | – | – |
| notes | – | – | – |
| projected_profit | – | – | – |
| projected_sale_price | – | – | – |
| roi | – | – | – |
| sales_rank | – | – | – |
| sourced_from | – | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
analyse_product ~103
Quick analysis of an Amazon product by ASIN: title, brand, current/90-day pricing, sales rank and estimated monthly sales, FBA fees and profit basics. Call this first whenever the user asks about a specific ASIN. Costs the user 1 analyse credit unless cached. Domain is the Amazon marketplace: GB, US, DE, FR, ES or IT.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | – |
| domain | string | – | – |
No output schema declared.
No examples provided.
analyse_product_full ~97
Full analysis of an Amazon product by ASIN — everything in analyse_product plus seller/stock breakdown, buy-box history and variations. Slower and heavier than analyse_product; use when the user wants seller-level or historical detail in one shot. Costs 1 analyse credit unless the ASIN was analysed in the last 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | – |
| domain | string | – | – |
No output schema declared.
No examples provided.
calculate_profit ~126
Calculate Amazon FBA profit and ROI for given sell/cost prices using the full fee engine (tiered referral fees, digital services tax, VAT on fees). Call for what-if questions like 'what would I make selling at £24.99 if I buy at £12?'. Prices are in the marketplace currency.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| cost_price | number | yes | – |
| domain | string | – | – |
| pick_and_pack_fee | number | – | – |
| referral_fee_pct | number | – | – |
| sell_price | number | yes | – |
No output schema declared.
No examples provided.
check_eligibility ~117
Check whether the user is allowed to sell (ungated for) one or more ASINs on their Amazon account. Call for 'am I ungated for this?' or 'can I sell these ASINs?'. Returns per-ASIN {state, gated, apply_link}. Uncached ASINs are queued for a fresh check, so re-call shortly for any still pending. Requires a connected Amazon account.
| Name | Type | Req | Description |
|---|---|---|---|
| asins | array | yes | – |
| condition | string | – | – |
No output schema declared.
No examples provided.
configure_prep_sheet ~285
Configure the prep sheet. `enabled` turns auto-push to the user's own Google Sheet on/off: every new purchase (web app, MCP add_purchase, or the Discord 🛒 button) is appended as a row to `tab_name` (default 'Prep Sheet'). `columns` is the user's prep centre's column headers IN ORDER — free text, exactly as they appear on the sheet. Known headers are synonym-matched to purchase fields (Date, Item/Title, ASIN, SKU, Qty, Cost, Total Cost, Sale Price, Profit, ROI, Store/Company, Sourced From, Sales Rank, Monthly Sales, Notes, Image URL); unknown headers (e.g. 'Order Number') become empty columns the prep centre fills in. This is the SAME column config as the Items Purchased page's Prep Sheet Settings and the daily DM CSV, so changing it here changes all three. Omitted arguments keep their current values. The push also needs their Google Sheet connected (get_sheet_status) with an 'append_row' action in their Apps Script — if the response shows sheet_connected false, tell them to connect it in Sorsa Settings first.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | – | – | – |
| enabled | – | – | – |
| tab_name | – | – | – |
No output schema declared.
No examples provided.
confirm_ungate_supplier ~67
Record that a supplier's invoice got the user approved (ungated) for a brand. This increments that supplier's confirmation count for the brand so other users see which suppliers actually work.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | – |
| supplier_id | integer | yes | – |
No output schema declared.
No examples provided.
create_deal_task ~116
Create an A2A deal-monitor task: the user gets notified whenever the deal feed finds products matching these filters. Call when the user says e.g. 'notify me about deals over £5 profit and 40% ROI in Toys'.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| keepa_drops | – | – | – |
| max_asin_rank | – | – | – |
| min_monthly_sales | – | – | – |
| min_profit | – | – | – |
| min_roi | – | – | – |
| source | – | – | – |
| task_name | string | yes | – |
No output schema declared.
No examples provided.
create_finder_monitor ~359
Create a LIVE Keepa Product Finder monitor from the same filters as find_products. It runs on the user's OWN Keepa key and sends a Discord alert to `webhook_url` whenever a NEW product starts matching the filters — the saved/recurring version of find_products. REQUIRED: a `name` for the monitor and a Discord `webhook_url` (https://…) — ALWAYS ask the user for their webhook URL; never invent one. The user must also have their Keepa key connected (call get_keepa_key_status first). Provide at least one filter (same semantics/units as find_products). This creates a real, active monitor that will start pinging the webhook — confirm with the user before creating it. Set active=False to create it paused.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | – |
| amazon_not_on_listing | – | – | – |
| brand | – | – | – |
| category | – | – | – |
| drop_1d | – | – | – |
| drop_30d | – | – | – |
| drop_7d | – | – | – |
| drop_90d | – | – | – |
| drop_type | string | – | – |
| exclude_word | – | – | – |
| marketplace | string | – | – |
| max_amazon_price | – | – | – |
| max_bsr | – | – | – |
| max_buy_box_price | – | – | – |
| max_prime_price | – | – | – |
| max_sellers | – | – | – |
| min_amazon_price | – | – | – |
| min_buy_box_price | – | – | – |
| min_monthly_sold | – | – | – |
| min_prime_price | – | – | – |
| min_rating | – | – | – |
| min_reviews | – | – | – |
| min_sellers | – | – | – |
| name | string | yes | – |
| webhook_url | string | yes | – |
No output schema declared.
No examples provided.
create_listing ~195
Create the Amazon listing for a purchased item — the final step. Requires the item to have an ASIN, a listing_sku (run generate_sku first) and a sale price. SALE PRICE RULE: set `sale_price` to the product's 90-day average price (from analyse_product) as a sensible default — but ALWAYS tell the user the price you're about to list at and get their OK first. Never invent a price. If sale_price is omitted, the item's existing projected_sale_price is used (and the call fails if it has none). fulfillment: AMAZON_EU (FBA) or DEFAULT (FBM). This creates a REAL live Amazon listing on the user's account.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | – | – |
| fulfillment | string | – | – |
| item_id | integer | yes | – |
| quantity | – | – | – |
| sale_price | – | – | – |
No output schema declared.
No examples provided.
create_price_monitor ~100
Watch an ASIN and alert the user when its price drops to the target. Call when the user says things like 'watch this' or 'alert me if it goes below £20'. source is the marketplace: Amazon UK, Amazon DE, Amazon IT, Amazon ES, Amazon FR, Amazon US or Amazon Business UK.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | – |
| source | string | – | – |
| target_price | number | yes | – |
No output schema declared.
No examples provided.
find_products ~377
Search Amazon via Keepa's Product Finder and return the matching ASINs (up to 100). Runs on the USER'S OWN Keepa key — call get_keepa_key_status first; if not connected, tell them to add their key in Sorsa Settings. Provide at least one filter. Prices are in the marketplace's currency (e.g. £ for UK). marketplace: UK, US, DE, FR, IT, ES. Drop filters find items whose price fell by a % over a period — set any of drop_1d/7d/30d/90d (e.g. drop_30d=20 = 'dropped 20%+ in 30 days'), applied to drop_type: BUY_BOX_SHIPPING, AMAZON, or PRIME_EXCL. category is a Keepa root-category id (omit for all categories). Returns {count, asins[]} — analyse specific ones with analyse_product.
| Name | Type | Req | Description |
|---|---|---|---|
| amazon_not_on_listing | – | – | – |
| brand | – | – | – |
| category | – | – | – |
| drop_1d | – | – | – |
| drop_30d | – | – | – |
| drop_7d | – | – | – |
| drop_90d | – | – | – |
| drop_type | string | – | – |
| exclude_word | – | – | – |
| marketplace | string | – | – |
| max_amazon_price | – | – | – |
| max_bsr | – | – | – |
| max_buy_box_price | – | – | – |
| max_prime_price | – | – | – |
| max_sellers | – | – | – |
| min_amazon_price | – | – | – |
| min_buy_box_price | – | – | – |
| min_monthly_sold | – | – | – |
| min_prime_price | – | – | – |
| min_rating | – | – | – |
| min_reviews | – | – | – |
| min_sellers | – | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
generate_sku ~83
Generate a SKU for a purchased item (from its title/cost/qty using the user's SKU convention) and save it to the row. Pass the `id` returned by add_purchase or shown in get_items_purchased. Do this before create_listing. Returns the item with its new listing_sku.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | integer | yes | – |
No output schema declared.
No examples provided.
get_a2a_finder_jobs ~40
List the user's recent A2A Finder scan jobs and their status. Call to find a job_id whose results to fetch.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_a2a_finder_status ~68
Status and results of an A2A Finder scan started with start_a2a_finder_scan. Returns progress % and, once complete, the profitable cross-marketplace flips found (per ASIN, per country).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
get_aged_stock ~109
Age profile of the user's on-hand FBA stock, bucketed by days on shelf (0-30, 31-90, 91-180, 181-365, 365+), with capital tied up and how much is aged 90+ days (long-term storage-fee risk). Call for 'what stock is old or at risk?' or 'how much capital is stuck in aged inventory?'. Requires a connected Amazon account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_amazon_inventory ~82
The user's live FBA inventory: SKUs, quantities, conditions. Call when the user asks what stock they have or about a specific SKU/product they sell. Requires their Amazon account to be connected (closed beta).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min_quantity | – | – | – |
| page | integer | – | – |
| search | – | – | – |
No output schema declared.
No examples provided.
get_amazon_orders ~117
The user's Amazon orders with fees and COGS-based profit. Call for questions like 'how are sales today?' or 'show orders for this SKU'. timeframe: today, yesterday, week, month; or use date_from/date_to (YYYY-MM-DD). Requires a connected Amazon account (closed beta).
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | – | – | – |
| date_to | – | – | – |
| limit | integer | – | – |
| page | integer | – | – |
| search | – | – | – |
| status | – | – | – |
| timeframe | – | – | – |
No output schema declared.
No examples provided.
get_analyse_history ~61
The user's recent product analyses (ASIN, title, when). Call when the user asks what they looked at recently, or to re-find a product they mention having analysed. limit max 50.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_best_sellers ~90
The user's own top-selling ASINs by net profit for each of the last N months, derived from their sales. Call for 'what are my best sellers?' or 'top products this year'. months up to 24, top_n up to 50. Requires a connected Amazon account.
| Name | Type | Req | Description |
|---|---|---|---|
| months | integer | – | – |
| top_n | integer | – | – |
No output schema declared.
No examples provided.
get_credits ~46
The user's remaining monthly analyse and AI credits and the reset date. Call when the user asks about their usage limits, or after a credit-limit error from an analysis tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_dashboard_summary ~45
The user's Sorsa dashboard summary — headline stats across their monitors and results. Call for a general 'how's it looking' overview before drilling into specific feeds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_deal_results ~169
Search Sorsa's Amazon-to-Amazon (A2A) deal database — products found by the deal monitors with profit, ROI, sales rank and pricing. Call when the user asks for current deals, e.g. 'show me deals over £5 profit and 50% ROI'. Free to call. sort_field: timestamp, profit, roi_percentage, asin_rank or current_price.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | – | – | – |
| category | – | – | – |
| limit | integer | – | – |
| max_rank | – | – | – |
| min_profit | – | – | – |
| min_roi | – | – | – |
| min_sales | – | – | – |
| offset | integer | – | – |
| search_title | – | – | – |
| sort_direction | string | – | – |
| sort_field | string | – | – |
| source | – | – | – |
No output schema declared.
No examples provided.
get_deal_tasks ~47
List the user's A2A deal-monitor tasks (saved filters that generate notifications). Call before creating one, or when the user asks what monitors they have set up.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fba_refunds ~64
Refunds issued to the user's customers. Call when the user asks about refunds or money returned to buyers. Requires a connected Amazon account (closed beta).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
| search | – | – | – |
No output schema declared.
No examples provided.
get_fba_reimbursements ~75
Reimbursements Amazon has paid the user (lost/damaged stock etc). Call when the user asks what Amazon has paid them back. Requires a connected Amazon account (closed beta).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
| reason | – | – | – |
| search | – | – | – |
No output schema declared.
No examples provided.
get_fba_returns ~70
The user's FBA customer returns with dispositions (sellable, damaged, etc). Call when the user asks about returns. Requires a connected Amazon account (closed beta).
| Name | Type | Req | Description |
|---|---|---|---|
| disposition | – | – | – |
| limit | integer | – | – |
| page | integer | – | – |
| search | – | – | – |
No output schema declared.
No examples provided.
get_fba_shipment_items ~61
The line items inside one FBA shipment (expected vs received quantities). Call after get_fba_shipments when the user asks what was in a specific shipment or whether everything was received.
| Name | Type | Req | Description |
|---|---|---|---|
| shipment_id | string | yes | – |
No output schema declared.
No examples provided.
get_fba_shipments ~70
The user's inbound FBA shipments with summary stats. Call when the user asks about shipments they've sent to Amazon. Requires a connected Amazon account (closed beta).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
| search | – | – | – |
| status | – | – | – |
No output schema declared.
No examples provided.
get_international_prices ~78
Prices for the same ASIN across international Amazon marketplaces. Call when the user asks about cross-market price differences or EU arbitrage opportunities for a product. Costs 1 analyse credit unless the ASIN was analysed in the last 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | – |
| domain | string | – | – |
No output schema declared.
No examples provided.
get_items_purchased ~46
Items the user has actually purchased from their sourcing list, including listing status (SKU, listing errors). Call when the user asks what they've bought or about listing progress.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_items_sourced ~48
The user's sourcing list — products they've found and are considering buying, with cost/profit projections and status. Call when the user asks about their buy list or sourcing pipeline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_keepa_key_status ~51
Whether the user has connected their own Keepa API key (needed for find_products). If not connected, tell them to add it in Sorsa Settings. Never returns the key itself.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_monthly_pnl ~93
Per-SKU profit & loss for one calendar month: revenue, Amazon fees, COGS, refunds and net profit, plus account totals. Call for 'what was my profit in <month>?' or 'break down last month's P&L'. month is 'YYYY-MM'. Requires a connected Amazon account.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | – |
| vat_registered | boolean | – | – |
No output schema declared.
No examples provided.
get_notifications ~64
The user's price-alert notifications from their A2A monitor tasks, grouped by task. Call when the user asks what alerts or notifications they have. show_checked: 'unchecked' (default), 'checked' or 'all'.
| Name | Type | Req | Description |
|---|---|---|---|
| show_checked | string | – | – |
No output schema declared.
No examples provided.
get_oa_deals ~129
Profitable online-arbitrage (OA) deals: retail products matched to Amazon listings with profit and ROI. Call when the user asks about OA or retail sourcing opportunities. sort: roi, profit, price, newest, sell, rank, monthly_sold or sellers.
| Name | Type | Req | Description |
|---|---|---|---|
| max_rank | – | – | – |
| min_monthly_sold | – | – | – |
| min_profit | – | – | – |
| min_roi | – | – | – |
| page | integer | – | – |
| per_page | integer | – | – |
| retailer | – | – | – |
| search | – | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
get_oa_retailers ~40
List the retailers available in the OA deals feed. Call to know which retailer names are valid filters for get_oa_deals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_prep_sheet_config ~102
The user's prep-sheet settings: whether new Items Purchased rows are auto-pushed to their connected Google Sheet, which tab they go to, and the column order. The columns are SHARED with the Prep Sheet Settings modal on the Items Purchased page and the daily prep-sheet Discord DM — one config, three outputs. Call before configure_prep_sheet, or when the user asks how their prep sheet is set up.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_price_monitors ~46
List the user's ASIN price monitors (watched products with target prices). Call before creating one to avoid duplicates, or when the user asks what they're watching.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_product_performance ~89
Per-SKU profitability over the last N days: units, revenue, profit, ROI, return rate, current price vs break-even and a selling-at-a-loss flag. Call for 'which products make or lose me money?' or 'what's selling below break-even?'. days 7-365. Requires a connected Amazon account.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
get_product_sellers ~84
Current sellers and their stock levels for an Amazon ASIN. Call when the user asks who is selling a product, how many sellers there are, or how much stock competitors hold. Costs 1 analyse credit unless the ASIN was analysed in the last 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | – |
| domain | string | – | – |
No output schema declared.
No examples provided.
get_purchase_stats ~54
Purchase statistics: total spent, projected profit, items bought and ROI, broken down daily/monthly/yearly and by category and source. Call for questions like 'how much have I spent this month?'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_purchases ~46
The user's logged purchase history. timeframe: all, day, week, month or year. Call when the user asks what they've bought recently.
| Name | Type | Req | Description |
|---|---|---|---|
| timeframe | string | – | – |
No output schema declared.
No examples provided.
get_reconciliation_claims ~91
Individual reclaim opportunities with evidence — what to claim from Amazon and why. Call after get_reconciliation_summary to list the actual claims. status: open, dismissed, filed or all. Requires a connected Amazon account (closed beta).
| Name | Type | Req | Description |
|---|---|---|---|
| claim_type | string | – | – |
| limit | integer | – | – |
| page | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
get_reconciliation_summary ~67
Totals of reclaimable money Sorsa has detected the user is owed by Amazon, broken down by claim type (shipment shortages, lost inventory, unreturned refunds...). Call for 'how much does Amazon owe me?'. Requires a connected Amazon account (closed beta).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_repricer_items ~173
The user's repricer SKUs with live pricing state: current price, Buy Box price, lowest FBA price, cost/min/max, strategy, computed profit/ROI at the current price, floor price and stock. Call when the user asks what the repricer is doing, whether they hold the Buy Box on something, or why an item isn't repricing. search matches SKU or ASIN. status filters to one of: active, off, out_of_stock, needs_cog, needs_min, awaiting_fees, error, or 'attention' (needs_cog + needs_min + error). limit max 500. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
| search | – | – | – |
| status | – | – | – |
No output schema declared.
No examples provided.
get_repricer_log ~96
Recent repricer price changes, newest first: SKU, old → new price, the reason, the reference price it repriced against (Buy Box / lowest FBA) and whether the floor or ceiling capped the move. Call when the user asks what the repricer changed recently or why a price moved. limit max 500.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
get_repricer_settings ~56
The user's global repricer settings: whether repricing is globally enabled, seller ID, default strategy, default minimum ROI, allowed strategies and VAT registration. Read-only — changing settings is web-app only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Sorsa MCP server?
Sorsa is a hosted endpoint at https://sorsa.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 · sorsa.app
claude mcp add --transport http app-sorsa-sorsa 'https://sorsa.app/mcp'
What is the Sorsa MCP server?
Sorsa is an MCP server listed in the public MCP registry as app.sorsa/sorsa. Amazon FBA arbitrage toolkit: product analysis, deal feeds, price alerts and sourcing management. This page covers its hosted endpoint (https://sorsa.app/mcp).
Is the Sorsa MCP server safe to use?
Sorsa scores 69 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 Sorsa MCP server expose?
Sorsa exposes 73 tools: analyse_product, analyse_product_full, get_product_sellers, get_international_prices, calculate_profit, and 68 more. Their descriptions and schemas cost roughly 7,530 tokens of context every time the server is loaded.
Does the Sorsa MCP server require authentication?
No. We connected to Sorsa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sorsa MCP server still maintained?
Sorsa is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.