Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Nexscope
Overview
Description from the maker (original English)
Ecommerce data MCP: Amazon, TikTok Shop, Walmart, Temu, Ozon, Shopee, 1688, Etsy, eBay & more
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Online shops & payments
- You need to fill in: Authorization
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 0 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- You fill in yourself:
Authorization
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http ecommerce https://api.nexscope.ai/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ecommerce": {
"url": "https://api.nexscope.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"ecommerce": {
"type": "http",
"url": "https://api.nexscope.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
Authorizationsecret HTTP headerBearer API key from Nexscope (or use OAuth sign-in in clients that support it)
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ! Caution
Maker matches the repo
The publisher (nexscope) is not the repo owner (nexscope-ai); someone else may have listed it
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 1743 servers in this category
- Published to the registry more recently than 60% of the other 1743 servers in this category
- Basic checks equal to or better than 44% of the other 1743 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Nexscope safe?
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: Authorization
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 21 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Nexscope Ecommerce API
Connect ecommerce workflows to marketplace data, product research, and AI image and video creation through Nexscope APIs.
238 APIs · 185 Data APIs · 53 Creative APIs · 21 categories
Get an API key · Official API docs · Complete catalog · Integration guide
This repository includes the documented API snapshots listed below, with request/response definitions, editable request samples, and cURL, JavaScript, and Python clients. Use it to connect marketplace research, sourcing, keyword analysis, product imagery, and video creation to your application.
Quick start
1. Get and configure your API key
Open API Access, sign in, and create or copy your user API key. Send it in the Authorization header as a bearer token.
Creative API access requires an active subscription. Trial credits do not enable Creative API key access. Review your account access and current plans before submitting generation requests.
Keep the key on your server. Do not commit it or expose it in a browser application. In Bash or Zsh, enter it without displaying it or putting its value into shell history:
printf 'Nexscope API key: '
read -r -s NEXSCOPE_API_KEY printf '\n' export NEXSCOPE_API_KEY
All run requests use:
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
2. Make your first Data API request
This example calls Amazon Search API for phone case results. It sends a real API request when you execute it with your key.
curl --silent --show-error --fail-with-body --max-time 120 \
-X POST 'https://api.nexscope.ai/api/skill-api/v1/skills/amazon-search/run' \ -H "Authorization: Bearer $NEXSCOPE_API_KEY" \ -H 'Content-Type: application/json' \ -d '{"keyword":"phone case","page":1}'
Response shapes vary by API; follow its current official reference. For Amazon Product Detail, check code === 0 and read business fields from data (for example, data.products and data.total); data may be null. The Amazon Search fixture below retains the original snapshot shape and should be verified against its current reference before integration. Documented response fixture.
3. Use JavaScript, Python, or reusable cURL commands
Clone this repository and run commands from its root. The examples require Node.js 22+, Python 3.10+, or cURL 7.76+; the cURL helper also uses Python 3.10+ to look up and check the request. JavaScript and Python use only standard libraries.
git clone https://github.com/nexscope-ai/nexscope-ecommerce-api.git
cd nexscope-ecommerce-api
Choose ONE client to submit a request:
node examples/javascript/run.mjs amazon-search payloads/amazon-search.json
Alternatively:
python3 examples/python/run.py amazon-search payloads/amazon-search.json
Alternatively:
bash examples/curl/run.sh amazon-search payloads/amazon-search.json
Each command above independently submits a request. To inspect the method, endpoint, and JSON without sending or using credits:
python3 examples/python/run.py amazon-search payloads/amazon-search.json --dry-run
node examples/javascript/run.mjs amazon-search payloads/amazon-search.json --dry-run
JavaScript source · Python source · cURL source
4. Call a Creative API and retrieve its result
All 53 Creative APIs in this snapshot use asynchronous tasks. This example uses Background Remover API.
Create a request with your real, publicly accessible image URL. The input image must meet the API's documented limits, including 385–8192 pixels on both dimensions and a maximum size of 20 MB.
cp payloads/background-remover.json creative-request.json
Edit creative-request.json: replace the example.com image URL with your asset URL.
subType: 1 = general, 2 = portrait, 3 = product, 9 = apparel, 12 = hair, 13 = face.
python3 examples/python/run.py background-remover creative-request.json > creative-task.json cat creative-task.json
The submission returns a receipt resembling this illustrative documentation sample:
{
"taskId": "6b3f1c61-1b7d-4a59-8a7d-3b23e4b0c9e2", "status": "PENDING", "message": "The task has been created. Use taskId to query the result." }
Use the task ID returned by your own request to query the result; do not rerun the POST to check progress:
TASK_ID=$(python3 -c 'import json; print(json.load(open("creative-task.json"))["taskId"])')
python3 examples/python/run.py background-remover --task "$TASK_ID"
Alternatively: node examples/javascript/run.mjs background-remover --task "$TASK_ID"
Alternatively: bash examples/curl/run.sh background-remover --task "$TASK_ID"
The query endpoint is:
GET https://api.nexscope.ai/api/skill-api/v1/skills/background-remover/tasks/{taskId}
Authorization: Bearer YOUR_API_KEY
PENDINGorRUNNING: the task is not complete. Query the same task later; a 5-second starting interval is an application recommendation, not an API rate-limit guarantee.SUCCESS: inspect the returned payload for generated outputs and the actual credits charged.FAILEDorTIMEOUT: stop polling and inspect the error. A new submission is a separate request.
The included clients perform one submission or one status check per command. They do not automatically resubmit or poll indefinitely. See asynchronous integration details.
5. Switch to any API in the catalog
Open its documentation below, copy payloads/ .json into your own request file, and replace illustrative inputs. Pass the slug and your file to the same client:
cp payloads/seedance-2-5-video-generation.json request.json
Edit request.json with your real reference image and desired prompt.
python3 examples/python/run.py seedance-2-5-video-generation request.json
Parameter names, media requirements, conditional fields, and response shapes vary by API. The clients reject reserved example-domain asset URLs; you must also review sample product IDs, search terms, and other values for your intended use.
Errors and response handling
| HTTP status | What to do |
|---|---|
| 200 | Follow the current response contract; when code is present, only 0 indicates business success or acceptance. For asynchronous work, also inspect the documented task status. |
| 400 | Check required fields, types, allowed values, conditional inputs, and media constraints. |
| 401 | Check the bearer header and API key. |
| 403 | Check account permissions, API access, and subscription requirements. |
| 429 | Respect Retry-After when present and back off. |
| 5xx | Inspect the service error. Before resubmitting a generation request, check whether a task was created. |
The helpers surface non-2xx responses and print the returned JSON. They do not currently reject nonzero platform code values; application code must perform that check when the endpoint uses the platform envelope. The Python and JavaScript helpers also exit with an error for FAILED or TIMEOUT task states; cURL reports HTTP status only. Do not blindly retry POST requests: the documentation does not establish an idempotency guarantee.
Repository contents
| Path | Contents |
|---|---|
| docs/data/ | 185 Data API references |
| docs/creative/ | 53 Creative API references |
| catalog/apis.json | Complete inventory, categories, links, endpoints, and definition formats |
| schemas/ | 238 request and 238 response definitions |
| payloads/ | 238 published request samples |
| examples/responses/ | 238 published response fixtures |
| examples/ | cURL, JavaScript, and Python clients for every catalog entry |
| docs/calling-apis.md | Authentication, tasks, media, and MCP guidance |
Complete API catalog
This catalog retains the original 225 entries and adds 11 WooCommerce production APIs (2026-10-29). It also adds two SIF production APIs (2026-11-02, reflecting the 2026-10-31 source contract). Other entries keep their documented snapshot dates. Each entry links to its definitions, sample payload and official reference.
Data APIs — 185
Amazon Marketplace Intelligence (26)
| API | Purpose |
|---|---|
| Amazon ASIN Traffic Summary API | Use Nexscope (Search Intelligence Framework) data to analyze ASIN traffic source composition and exposure distribution, covering current period/previous period/newly entered/exited period comparisons. |
| Amazon Broad Product Search API | Use Nexscope data to search and filter Amazon products, supporting multi-dimensional criteria including price, monthly sales, BSR ranking, gross margin, ratings, fulfillment method, badges, seller origin, and more across multiple Amazon marketplaces. |
| Amazon Category Lookup API | Browse Amazon category nodes or search category metadata by name. |
| Amazon Competitor Lookup API | Use Nexscope data to find and analyze competitors on Amazon, covering 12 marketplaces, with product metrics including sales, BSR, pricing, ratings, and growth trends. |
| Amazon Market Product Detail API | Query Amazon product detail and historical trends by ASIN using Nexscope data, covering 14 marketplaces. |
| Amazon Market Product Search API | Multi-dimensional Amazon product search and filtering based on Nexscope data, covering 14 marketplaces, with support for historical monthly snapshot lookback. |
| Amazon Market Research API | Use Nexscope market list capability to filter Amazon niche markets by category dimensions, supporting market size, competition, top concentration, seller structure, new product share, price/rating/margin ranges, and many other criteria for discovering viable markets and evaluating product selection directions. |
| Amazon Market Statistics API | Use Nexscope market statistics capability to output a market statistics dashboard by category node, including top listing average rating, average price, BSR, sales, seller count, and new product related metrics, suitable for quickly assessing the market quality and competitive landscape of a category. |
| Amazon Niche Info API | Query and analyze Nexscope data for Amazon niche market insights, including market metrics, buyer reviews, competitive landscape, price trends, and growth trends. |
| Amazon Niche Info By ASIN API | Deep analysis of Amazon niche markets by product ASIN, covering monopoly level, brand concentration, new product success rate, and market opportunity score. |
| Amazon Opportunity Search By Metrics API | Amazon reverse product selection: filter Amazon niches and keywords by 30+ business dimensions (market size & growth, price tiers & share, competition density & top concentration, demographics such as age/gender/income, review highlights & pain points) from a metrics pool aggregated from historical business insight reports. |
| [Amazon Policy Feed API](docs/data/amazon-pol
Only the beginning is shown; read the rest in the repo