Amazon Seller Operations
PYPI · AMAZON-SELLER-OPERATIONS-MCP · 2 COMPONENTS
Amazon account health, listing, FBA inventory, fee, PPC, review, and appeal intelligence.
Last scanned (2 hours ago)
Scores higher than 61% of PyPI servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 175 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 288 tokens (~24/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 92% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed pypi/amazon-seller-operations-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_hook | unreviewed | legacy backend root module |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
draft_appeal Draft Appeal ~35
Draft an Amazon-formatted appeal for human review.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | yes | – |
| context | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_account_health Get Account Health ~22
Return ODR, cancellation, late shipment, and policy health.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_fee_breakdown Get Fee Breakdown ~29
Return FBA/referral/storage fee breakdown and true margin.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_inventory_health Get Inventory Health ~24
Return FBA stock, reorder points, stranded inventory, and storage fees.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_license_status Get License Status ~27
Return payment/license readiness for AtulHritik-Mcp-Suite without exposing secrets.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_live_connector_status Get Live Connector Status ~23
Return Amazon SP-API and Ads connector readiness without exposing secrets.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_ppc_recommendations Get Ppc Recommendations ~30
Return bid, budget, and negative keyword recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_review_sentiment Get Review Sentiment ~31
Return review themes and complaint velocity.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | – |
| days | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_suppressed_listings Get Suppressed Listings ~21
Return suppressed listings with reasons and fix steps.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
health Health ~4
No description provided.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
test_amazon_ads_connection Test Amazon Ads Connection ~20
Run a read-only Amazon Ads smoke check.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
test_amazon_sp_connection Test Amazon Sp Connection ~22
Run a read-only Amazon SP-API smoke check.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Amazon Seller Operations MCP server?
Amazon Seller Operations runs locally as a PyPI package, launched with uvx amazon-seller-operations-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · amazon-seller-operations-mcp
claude mcp add atul0016-amazon-seller-operations -- uvx amazon-seller-operations-mcp
What is the Amazon Seller Operations MCP server?
Amazon Seller Operations is an MCP server listed in the public MCP registry as io.github.atul0016/amazon-seller-operations. Amazon account health, listing, FBA inventory, fee, PPC, review, and appeal intelligence. This page covers its PyPI package (amazon-seller-operations-mcp).
Is the Amazon Seller Operations MCP server safe to use?
Amazon Seller Operations scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Amazon Seller Operations MCP server expose?
Amazon Seller Operations exposes 12 tools: health, get_license_status, get_live_connector_status, test_amazon_sp_connection, test_amazon_ads_connection, and 7 more. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.
Is the Amazon Seller Operations MCP server still maintained?
Amazon Seller Operations 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.