·  54 tools on record  ·  297 archived pricing pages  ·  data synced 2026-10-31Methodology  ·  How we earn money
Independent. No vendor can pay
for placement or a verdict.
Seller Tools Index.Receipts for seller software

Inspection report

SellerBridge

Open source MCP server from sakshsiw. Tool list: code-checked7.

The answer

0

What can it change in your account?

None of the 3 tools on record can change data.

name based Read and write here are inferred from tool names and descriptions, not from a test.

AreaAccessWrite toolsRead tools
Orders· Orders no tool on record00
Ads· Ads no tool on record00
ListingsR Listings read only01
Pricing· Pricing no tool on record00
Inventory· Inventory no tool on record00
Reports· Reports no tool on record00
Finance· Finance no tool on record00

Record

The facts on file.

Type
open-source
Vendor or owner
sakshsiw
License
no license (all rights reserved)3
Authentication
LWA refresh token, OAuth (mentioned), AWS SigV44
Transport
stdio
Marketplaces
BR, DE, ES, IN, IT, JP, MX, UK, US6
Pricing
Not published5
Last commit
Mar 25, 2026
Last release
Not published
GitHub stars
0
Tool list from
code-checked7
Links
Repository1, documentation2

Tools

All 3 tools we found.

Grouped by what they do to your data. The access column shows why we put a tool there.

read Reads data 3

ToolDescriptionAreaAccess basis
execute-external-apiExecute HTTP requests to external REST APIs (non-Amazon APIs)Othername based
execute-sp-apiExecute Amazon Selling Partner API requests with specified endpoint and parametersOthername based
explore-sp-api-catalogGet information about SP-API endpoints and parametersListingsname based

Method

How we checked this server.

We read the tool definitions in the source code. We did not run the server against a seller account.7

Not tested with credentials. We did not connect this server to a seller or ads account. A tool marked read can still have side effects we could not see, and a vendor can add write tools at any time. Check the list again before you grant access.

Areas come from keywords in tool names, as explained on the matrix page.

Notes

Sources for this report

  1. 1Source repository or product pagegithub.com
  2. 2Documentationgithub.com
  3. 3License: GitHub API repo.license (search 2026-10-30)
  4. 4Authentication: static scan of repo (env names / code patterns)
  5. 5Pricing: https://github.com/sakshsiw/SellerBridgegithub.com
  6. 6Marketplaces: marketplace IDs found in code
  7. 7Our MCP inventory of Oct 30, 2026: tool list, access marks, stars and last commit. GitHub repository search (22 queries, unauthenticated) -> shallow clone -> static extraction (extract_tools.py) -> optional runtime tools/list (mcp_probe.py); vendor/official from public docs. access=read|write is a name/description heuristic unless access_basis says otherwise.