Nexscope
io.github.nexscopePublished by GitHub account nexscopev1.0.3Updated Oct 24, 2026
Ecommerce data MCP: Amazon, TikTok Shop, Walmart, Temu, Ozon, Shopee, 1688, Etsy, eBay & more
Overview
Remote Nexscope MCP server giving assistants access to ecommerce marketplace data, product and keyword research, and AI image/video generation APIs.
- What you can do
- Search and analyze marketplace products, shops, categories and reviews across Amazon, Walmart, Temu, TikTok Shop, 1688, Shopify, WooCommerce and others
- Research keywords, search demand, traffic sources, niches and competitor metrics
- Run sourcing and image-based product lookups on wholesale and marketplace catalogs
- Submit asynchronous creative tasks such as background removal and video generation, then check task status by task ID
- When to use it
- Useful when an assistant needs ecommerce market research, product selection, keyword or competitor analysis across marketplaces, or programmatic access to Nexscope's creative image and video APIs.
- Requirements
- Remote endpoint at api.nexscope.ai over streamable HTTP. Requires a Nexscope account and an API key sent as a bearer token in the Authorization header, or OAuth sign-in in clients that support it. Creative API access requires an active paid subscription; trial credits do not enable it.
Installation
In SourceWeft
- Open Nexscope in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.nexscope%2Fecommerce/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"nexscope": {
"type": "http",
"url": "https://api.nexscope.ai/mcp"
}
}
}README
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:
All run requests use:
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.
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.
Each command above independently submits a request. To inspect the method, endpoint, and JSON without sending or using credits:
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.
The submission returns a receipt resembling this illustrative documentation sample:
Use the task ID returned by your own request to query the result; do not rerun the POST to check progress:
The query endpoint is:
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/<slug>.json into your own request file, and replace illustrative inputs. Pass the slug and your file to the same client:
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
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
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)
Walmart Marketplace Intelligence (5)
Keyword & Search Demand (15)
TikTok / Social Commerce (54)
Temu Marketplace Intelligence (11)
1688 Sourcing (4)
Shopify Commerce (2)
WooCommerce Public Store Data (11)
Etsy Marketplace (4)
Ozon Marketplace (10)
eBay Marketplace (1)
Shopee Marketplace (2)
Search & Trend Intelligence (3)
AI Content Generation (1)
Patent & IP Risk (25)
Product & Market Research (2)
Amazon Advertising (8)
Patent Intelligence (1)
Creative APIs — 53
Image Generation Models (7)
Video Generation Models (12)
Multimodal AI (34)
Source, coverage, and validation
Snapshot: 2026-09-10, from the official API directory and its public definition service. Counts refer to documented API entries, not every supporting HTTP route. The original 225-entry inventory plus the scoped WooCommerce and SIF additions is included; live documentation can change after each recorded snapshot.
Some definitions use field descriptors rather than standard JSON Schema. Each format is labeled in the catalog. Published request and response samples are illustrative fixtures, not evidence of successful live calls. No authenticated or billable API requests were executed to prepare this repository. See source notes for the precise validation scope.
Run the offline consistency checks:
Contributing and license
For a documentation correction, include the API slug and relevant official documentation link. Never include API keys, account data, or private request logs.
Example code, validation scripts, tests, and workflow configuration are provided under the MIT terms in LICENSE. API documentation, catalog content, definitions, and sample data remain copyright Nexscope; no separate open-content license is granted here. API service use remains subject to Nexscope's applicable terms and account access requirements.
Source: README.md at commit 1115466
Tools
0Version history
3- v1.0.3LatestOct 16, 2026
- v1.0.2Oct 14, 2026
- v1.0.0Oct 14, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.