{ "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-11", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "tool": { "slug": "nexscope", "name": "Nexscope", "vendor": "ECOCREATE TECHNOLOGY PTE. LTD.", "vendorUrl": "https://www.nexscope.ai", "kind": "platform", "category": "web-scrapers", "summary": "Nexscope is a hosted platform for ecommerce sellers with marketplace product, keyword and competitor data for Amazon, TikTok Shop, Walmart, Temu, 1688 and others, plus AI product images and video, through a web app, REST API and remote MCP server.", "url": "https://www.anchorterminal.com/tools/nexscope", "markdownUrl": "https://www.anchorterminal.com/tools/nexscope.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nexscope.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nexscope.json", "dns": "nexscope.grade.anchorterminal.com", "repo": "https://github.com/nexscope-ai/nexscope-ecommerce-api", "license": "Proprietary hosted service under the Nexscope terms (last updated 8 October 2026), whose contracting party is ECOCREATE TECHNOLOGY PTE. LTD. of Singapore. The OpenAPI file's licence is 'Proprietary API; use subject to Nexscope Terms'. In github.com/nexscope-ai/nexscope-ecommerce-api only the example clients, validation scripts, tests and workflow are MIT. The API documentation, catalogue, definitions and sample data stay copyright Nexscope", "transports": [ "streamable-http", "http" ], "remoteUrl": "https://api.nexscope.ai/mcp", "packages": [], "auth": "mixed", "authNotes": "The remote MCP server takes OAuth 2.1 (authorisation code with PKCE, scope `mcp:tools`) in clients that support it, or a Nexscope API key as `Authorization: Bearer nk-...`, which the tool pages call a compatibility option. The REST API takes the same key as a Bearer header. A person signs in and creates the key under API Access, API Keys. The full key is shown once, and keys can be expired, disabled or deleted, per the help page's troubleshooting. No key scopes, rotation rule or key-management API were found. Creative API key access needs an active subscription. Trial credits don't enable it. The OAuth metadata on api.nexscope.ai was not read (https://www.nexscope.ai/mcp-map/amazon-search, https://www.nexscope.ai/help/skills-external-access, https://github.com/nexscope-ai/nexscope-ecommerce-api, checked 2026-11-10).", "pricing": "paid", "pricingNotes": "Credits on a monthly subscription. A Free Trial gives 1,000 credits for 3 days with no card, at 1 API and 1 MCP request a second and 1 concurrent each, with no video API. Starter is $29 a month for 30,000 credits (3 requests a second, 2 concurrent), Growth $55 for 75,000 (5 and 4) and Pro $129 for 150,000 (10 and 8), each half price for the first period, with yearly billing and credits that reset monthly and don't roll over. Pay-as-you-go top-ups buy Data credits only, with no subscription. Each tool has its own credit cost, at least 10 for a Data API call. Amazon Search shows 'from 21 credits per call' and a recent average of 30. Refunds within 7 days if unused, per the terms. The home page listed Growth at $69 on the same day (https://www.nexscope.ai/pricing, https://www.nexscope.ai/mcp-map, https://www.nexscope.ai/terms, checked 2026-11-10).", "priceSummary": "$0.001 / credit", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, the API quickstart, the MCP map, llms.txt, the visible part of the OpenAPI file or the GitHub repository on 2026-11-10. Credits come from a subscription or a Data top-up after a browser sign-in (https://www.nexscope.ai/pricing).", "endpoints": [] }, "toolCount": 382, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-10" }, "docsUrl": "https://www.nexscope.ai/api-docs", "llmsTxt": "https://www.nexscope.ai/llms.txt", "openapi": "https://api.nexscope.ai/openapi.json", "registryName": "io.github.nexscope/ecommerce", "capabilities": [ "web.extract", "shopping.search", "shopping.prices", "seo.keywords", "seo.backlinks", "search.serp", "image.generate", "image.edit", "video.generate", "video.image-to-video" ], "tags": [ "hosted", "official", "closed-source", "mcp", "remote-mcp", "oauth", "api-key", "openapi", "llms-txt", "marketplace", "shopping", "images", "video", "credits", "subscription", "free-trial", "no-card", "new" ], "lastRelease": "2026-11-09", "graded": true, "anchor": { "graded": true, "score": 46.2, "grade": "D", "agentReady": false, "rank": 1191, "ranked": true, "rankOf": 1520, "categoryRank": 28, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 44, "maintenance": 65, "payments": 35, "reliability": 39, "schema": 64, "security": 41, "transparency": 41 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 39, "points": 7.8, "reason": "Hosted lines, graded on the remote MCP server and the REST API at api.nexscope.ai. No status page is linked from the home page, llms.txt, the API quickstart or the MCP map, and none was found (0). With no page there is no incident history to read (5). The pricing page publishes requests a second and concurrency per plan, the same for API and MCP, with 1 and 1 on the trial, 3 and 2 on Starter, 5 and 4 on Growth, 10 and 8 on Pro (15). The quickstart calls 429 an 'execution admission rate limit' and says to honour `Retry-After` on 429 and 503 when present. No idempotency key exists. The repository says 'Do not blindly retry POST requests' and to check whether a task was created before resubmitting, and the MCP tool pages say a reconnecting client should query existing async work rather than resubmit. SoldFetch earned 15 with idempotency keys and SandBase 11 with keys on some writes, so guidance without keys earns 9 (9 of 15). No SLA, and the terms say 'We cannot guarantee the Service will be available at all times' (0). No beta or preview label on the API or the MCP server (10). 0+5+15+9+0+10 = 39.", "checked": "2026-11-10" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 64, "points": 10.4, "reason": "A public OpenAPI 3.1 file at api.nexscope.ai/openapi.json, about 3.8 MB, linked from the quickstart. Visible request bodies are typed with required fields, patterns, enums and `additionalProperties: false`, but responses are open `data` objects and the components section, with the security scheme and the shared error response, wasn't reached. In the repository 166 of 252 request definitions are field descriptors rather than JSON Schema. The hosted tools/list wasn't read. SoldFetch took 17 with untyped responses and SandBase 22 with components unread (19 of 25). llms.txt on www.nexscope.ai and Markdown references for every API in the repository (10). MCP tool descriptions are one line ('Find Amazon products by keyword and marketplace. Results come back as structured JSON.'), with no when-not-to-use. The repository's references carry long trigger text ('trigger this skill whenever their need involves real-time Amazon search results'), not guidance on when to pick another tool (10 of 20). Tool pages list types, defaults, enums and length limits, but the Amazon Search page marks no argument required and omits the `keyword` its own examples pass, and many limits sit in prose (8 of 15). Every API has a request sample, a response fixture and cURL, JavaScript and Python clients, though most fixtures are labelled historical. Errors are an HTTP table, two named codes (11209, 12001) and a semantic error response whose schema wasn't read. MCP errors aren't documented (10 of 15). Path versioning under /v1, MCP v2 beside a legacy v1, and a dated OpenAPI version label, but no public changelog. SandBase earned 7 on the same pattern (7 of 15). 19+10+10+8+10+7 = 64.", "checked": "2026-11-10" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 44, "points": 7.15, "reason": "Read on the MCP server, with the REST API where a line covers it. The MCP map lists 382 tools and says the category manifests 'narrow metadata for your integration; the MCP connection still advertises the full catalog'. That is more than 30 tools with no toolsets, dynamic loading or read-only subset found (5). Search tools page by `page` (about 20 results), with filters such as marketplace, category node, sort and device per tool, but no general pagination model or field selection, and output size depends on each tool (12 of 20). By default business errors answer HTTP 200 with an outer `code`. The `X-Nexscope-Http-Status: semantic` header maps them to HTTP statuses, the OpenAPI file names codes such as `DATA_IMAGE_DOWNLOAD_FAILED` and `CAPABILITY_BACKEND_UNAVAILABLE` in field text, and MCP errors aren't documented. SandBase earned 16 with typed bridge errors (11 of 20). Data calls only read. No idempotency keys and no readOnlyHint or destructiveHint documented. Async jobs return a `taskId` with a poll tool and a rule not to resubmit, and 1688 order, payment-link, receipt and cancel calls need an explicit JSON `true` confirmation (8 of 20). Few required parameters with defaults on most. No official SDK package, only standard-library clients in the repository for JavaScript and Python, which SoldFetch earned 8 for (8 of 15). 5+12+11+8+8 = 44.", "checked": "2026-11-10" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 41, "points": 7.18, "reason": "The MCP server takes OAuth 2.1 with PKCE and one scope, `mcp:tools`, per the tool pages, or a Bearer `nk-` API key. Keys are created by a person under API Access, shown once, and can be expired, disabled or deleted, with no scopes or rotation found. The OAuth metadata on api.nexscope.ai wasn't read. No query-string key option was found. Manifold earned 22 with OAuth and hashed keys whose storage it documents (20 of 30). Most tools read. Writes exist (1688 procurement on the user's own buyer account, Amazon Ads entity operations through an owned connection, paid generation jobs), and the 1688 calls need an explicit JSON `true` per action after a preview, with the guide saying to get the user's approval first. Credits cap spend. No read-only key or tool allowlist (12 of 20). Tools return third-party listings, reviews, social posts and web pages, and no prompt-injection guidance was found. Manifold, the closest marketing-data MCP, took 0 (0). The Account credits and Account usage APIs, `costToken` in data responses and credits charged on task results give per-call visibility. No key-level audit was found (9 of 15). security.txt answered a client error. No disclosure policy, bug bounty or certification found (0 of 20). 20+12+0+9+0 = 41.", "checked": "2026-11-10" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 35, "points": 4.38, "reason": "No x402, MPP or L402 on pricing, the quickstart, the MCP map, llms.txt or the visible OpenAPI paths. Credits come from a subscription or a Data top-up (0). Plans and credits per plan are public without a login ($29 for 30,000, $55 for 75,000, $129 for 150,000), and tool pages show credits per call, such as Amazon Search from 21 credits with a recent average of 30. Many tools on the MCP map list no cost and pricing is marked 'dynamic-credits'. Manifold earned 20 with a cost for every tool (15 of 20). A Free Trial of 1,000 credits for 3 days with 'No credit card required', API and MCP limits included. Creative API keys need a subscription (20). A person signs in through the browser to approve OAuth or create a key, and no keyless or programmatic route was found (0). 0+15+20+0 = 35.", "checked": "2026-11-10" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 65, "points": 5.69, "reason": "Read as a closed service with a public documentation repository. The repository synced the released 1688 procurement contracts on 9 November 2026 and committed again on 10 November (30). No releases or changelog. The dated record is the registry's four versions on 14 and 16 October, repository commits on 8, 9, 20 and 29 October and 2, 9 and 10 November, and source notes dating WooCommerce (29 October) and design search (2 November) additions. SoldFetch earned 10 for dated commits without releases (10 of 20). No public changelog. Support is service@nexscope.ai, WhatsApp and a booked call, untested. The repository's one merged pull request came from the organisation itself, and GitHub's API refused us, so issues weren't read (5 of 15). The official MCP registry lists `io.github.nexscope/ecommerce`, active, latest 1.0.3 of 16 October 2026, read first-hand (15). A CI workflow runs offline catalogue validation and unit tests on standard-library clients with no dependencies. The run results weren't read (5 of 10). 30+10+5+15+5 = 65.", "checked": "2026-11-10" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 41, "points": 3.59, "note": "editorial 33, provenance 48", "reason": "The editorial half. The service is closed. The terms (8 October 2026) name ECOCREATE TECHNOLOGY PTE. LTD. under Singapore law with no registration number or address. The repository's MIT licence covers client code only, and the documentation and definitions stay copyright Nexscope. Scrapewise earned 15 for closed terms with MIT side code (15 of 30). The privacy policy (8 October 2026) says uploads are not used to train AI models and that connected selling-partner data is deleted or de-identified when no longer needed, but 'this policy does not specify a single deletion deadline for all data', and no DPA was found. SandBase took 12 with no retention periods (10 of 30). No deprecation policy or dated notices. The terms promise notice of material changes before they take effect where practicable, and the MCP map keeps a legacy v1 beside v2 (3 of 20). Analytics and advertising vendors are named (Google Analytics, Microsoft Clarity, Ahrefs, Google Ads, X, FirstPromoter), but hosting, AI processing and payment providers only by type, with no data locations. The repository's source notes say supplier references 'are presented as Nexscope', so the data suppliers go unnamed except LinkFox Agent for 1688 authorisation (5 of 20). 15+10+3+5 = 33. The provenance half is computed from the provenance block.", "checked": "2026-11-10" } ], "assessment": { "date": "2026-11-10", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "Read on the MCP server, with the REST API where a line covers it. The MCP map lists 382 tools and says the category manifests 'narrow metadata for your integration; the MCP connection still advertises the full catalog'. That is more than 30 tools with no toolsets, dynamic loading or read-only subset found (5). Search tools page by `page` (about 20 results), with filters such as marketplace, category node, sort and device per tool, but no general pagination model or field selection, and output size depends on each tool (12 of 20). By default business errors answer HTTP 200 with an outer `code`. The `X-Nexscope-Http-Status: semantic` header maps them to HTTP statuses, the OpenAPI file names codes such as `DATA_IMAGE_DOWNLOAD_FAILED` and `CAPABILITY_BACKEND_UNAVAILABLE` in field text, and MCP errors aren't documented. SandBase earned 16 with typed bridge errors (11 of 20). Data calls only read. No idempotency keys and no readOnlyHint or destructiveHint documented. Async jobs return a `taskId` with a poll tool and a rule not to resubmit, and 1688 order, payment-link, receipt and cancel calls need an explicit JSON `true` confirmation (8 of 20). Few required parameters with defaults on most. No official SDK package, only standard-library clients in the repository for JavaScript and Python, which SoldFetch earned 8 for (8 of 15). 5+12+11+8+8 = 44.", "maintenance": "Read as a closed service with a public documentation repository. The repository synced the released 1688 procurement contracts on 9 November 2026 and committed again on 10 November (30). No releases or changelog. The dated record is the registry's four versions on 14 and 16 October, repository commits on 8, 9, 20 and 29 October and 2, 9 and 10 November, and source notes dating WooCommerce (29 October) and design search (2 November) additions. SoldFetch earned 10 for dated commits without releases (10 of 20). No public changelog. Support is service@nexscope.ai, WhatsApp and a booked call, untested. The repository's one merged pull request came from the organisation itself, and GitHub's API refused us, so issues weren't read (5 of 15). The official MCP registry lists `io.github.nexscope/ecommerce`, active, latest 1.0.3 of 16 October 2026, read first-hand (15). A CI workflow runs offline catalogue validation and unit tests on standard-library clients with no dependencies. The run results weren't read (5 of 10). 30+10+5+15+5 = 65.", "payments": "No x402, MPP or L402 on pricing, the quickstart, the MCP map, llms.txt or the visible OpenAPI paths. Credits come from a subscription or a Data top-up (0). Plans and credits per plan are public without a login ($29 for 30,000, $55 for 75,000, $129 for 150,000), and tool pages show credits per call, such as Amazon Search from 21 credits with a recent average of 30. Many tools on the MCP map list no cost and pricing is marked 'dynamic-credits'. Manifold earned 20 with a cost for every tool (15 of 20). A Free Trial of 1,000 credits for 3 days with 'No credit card required', API and MCP limits included. Creative API keys need a subscription (20). A person signs in through the browser to approve OAuth or create a key, and no keyless or programmatic route was found (0). 0+15+20+0 = 35.", "reliability": "Hosted lines, graded on the remote MCP server and the REST API at api.nexscope.ai. No status page is linked from the home page, llms.txt, the API quickstart or the MCP map, and none was found (0). With no page there is no incident history to read (5). The pricing page publishes requests a second and concurrency per plan, the same for API and MCP, with 1 and 1 on the trial, 3 and 2 on Starter, 5 and 4 on Growth, 10 and 8 on Pro (15). The quickstart calls 429 an 'execution admission rate limit' and says to honour `Retry-After` on 429 and 503 when present. No idempotency key exists. The repository says 'Do not blindly retry POST requests' and to check whether a task was created before resubmitting, and the MCP tool pages say a reconnecting client should query existing async work rather than resubmit. SoldFetch earned 15 with idempotency keys and SandBase 11 with keys on some writes, so guidance without keys earns 9 (9 of 15). No SLA, and the terms say 'We cannot guarantee the Service will be available at all times' (0). No beta or preview label on the API or the MCP server (10). 0+5+15+9+0+10 = 39.", "schema": "A public OpenAPI 3.1 file at api.nexscope.ai/openapi.json, about 3.8 MB, linked from the quickstart. Visible request bodies are typed with required fields, patterns, enums and `additionalProperties: false`, but responses are open `data` objects and the components section, with the security scheme and the shared error response, wasn't reached. In the repository 166 of 252 request definitions are field descriptors rather than JSON Schema. The hosted tools/list wasn't read. SoldFetch took 17 with untyped responses and SandBase 22 with components unread (19 of 25). llms.txt on www.nexscope.ai and Markdown references for every API in the repository (10). MCP tool descriptions are one line ('Find Amazon products by keyword and marketplace. Results come back as structured JSON.'), with no when-not-to-use. The repository's references carry long trigger text ('trigger this skill whenever their need involves real-time Amazon search results'), not guidance on when to pick another tool (10 of 20). Tool pages list types, defaults, enums and length limits, but the Amazon Search page marks no argument required and omits the `keyword` its own examples pass, and many limits sit in prose (8 of 15). Every API has a request sample, a response fixture and cURL, JavaScript and Python clients, though most fixtures are labelled historical. Errors are an HTTP table, two named codes (11209, 12001) and a semantic error response whose schema wasn't read. MCP errors aren't documented (10 of 15). Path versioning under /v1, MCP v2 beside a legacy v1, and a dated OpenAPI version label, but no public changelog. SandBase earned 7 on the same pattern (7 of 15). 19+10+10+8+10+7 = 64.", "security": "The MCP server takes OAuth 2.1 with PKCE and one scope, `mcp:tools`, per the tool pages, or a Bearer `nk-` API key. Keys are created by a person under API Access, shown once, and can be expired, disabled or deleted, with no scopes or rotation found. The OAuth metadata on api.nexscope.ai wasn't read. No query-string key option was found. Manifold earned 22 with OAuth and hashed keys whose storage it documents (20 of 30). Most tools read. Writes exist (1688 procurement on the user's own buyer account, Amazon Ads entity operations through an owned connection, paid generation jobs), and the 1688 calls need an explicit JSON `true` per action after a preview, with the guide saying to get the user's approval first. Credits cap spend. No read-only key or tool allowlist (12 of 20). Tools return third-party listings, reviews, social posts and web pages, and no prompt-injection guidance was found. Manifold, the closest marketing-data MCP, took 0 (0). The Account credits and Account usage APIs, `costToken` in data responses and credits charged on task results give per-call visibility. No key-level audit was found (9 of 15). security.txt answered a client error. No disclosure policy, bug bounty or certification found (0 of 20). 20+12+0+9+0 = 41.", "transparency": "The editorial half. The service is closed. The terms (8 October 2026) name ECOCREATE TECHNOLOGY PTE. LTD. under Singapore law with no registration number or address. The repository's MIT licence covers client code only, and the documentation and definitions stay copyright Nexscope. Scrapewise earned 15 for closed terms with MIT side code (15 of 30). The privacy policy (8 October 2026) says uploads are not used to train AI models and that connected selling-partner data is deleted or de-identified when no longer needed, but 'this policy does not specify a single deletion deadline for all data', and no DPA was found. SandBase took 12 with no retention periods (10 of 30). No deprecation policy or dated notices. The terms promise notice of material changes before they take effect where practicable, and the MCP map keeps a legacy v1 beside v2 (3 of 20). Analytics and advertising vendors are named (Google Analytics, Microsoft Clarity, Ahrefs, Google Ads, X, FirstPromoter), but hosting, AI processing and payment providers only by type, with no data locations. The repository's source notes say supplier references 'are presented as Nexscope', so the data suppliers go unnamed except LinkFox Agent for 1688 authorisation (5 of 20). 15+10+3+5 = 33. The provenance half is computed from the provenance block." }, "sources": [ { "what": "home page (product, plans, links, footer, ECOCREATE in page metadata)", "url": "https://www.nexscope.ai/", "seen": "2026-11-10" }, { "what": "pricing (trial, plans, credits, API and MCP limits)", "url": "https://www.nexscope.ai/pricing", "seen": "2026-11-10" }, { "what": "terms (last updated 8 October 2026, ECOCREATE TECHNOLOGY PTE. LTD.)", "url": "https://www.nexscope.ai/terms", "seen": "2026-11-10" }, { "what": "privacy policy (last updated 8 October 2026)", "url": "https://www.nexscope.ai/privacy", "seen": "2026-11-10" }, { "what": "llms.txt", "url": "https://www.nexscope.ai/llms.txt", "seen": "2026-11-10" }, { "what": "launch post ('Updated Aug 07, 2026', API, MCP and Skills, 1,000 starting credits)", "url": "https://www.nexscope.ai/blog/nexscope-ai-agent-launch", "seen": "2026-11-10" }, { "what": "blog author page (Evan Huang, AI Engineer and Agent Developer)", "url": "https://www.nexscope.ai/blog/author/evan-huang", "seen": "2026-11-10" }, { "what": "API quickstart (envelope, error codes, 429 and 503, semantic header, credits)", "url": "https://www.nexscope.ai/api-docs/quickstart?tab=data", "seen": "2026-11-10" }, { "what": "MCP tool map (endpoint, 382 tools, categories, credits, agent instructions block), read in two parts", "url": "https://www.nexscope.ai/mcp-map", "seen": "2026-11-10" }, { "what": "Amazon Search MCP tool page (arguments, OAuth 2.1 PKCE scope `mcp:tools`, `nk-` keys, credits)", "url": "https://www.nexscope.ai/mcp-map/amazon-search?returnTo=%2Fmcp-map%23tool-directory", "seen": "2026-11-10" }, { "what": "agent setup help page (API keys, skills install)", "url": "https://www.nexscope.ai/help/skills-external-access", "seen": "2026-11-10" }, { "what": "security.txt (client error)", "url": "https://www.nexscope.ai/.well-known/security.txt", "seen": "2026-11-10" }, { "what": "OpenAPI 3.1 file, read at the start and near the end (paths, security per operation, error references, components not reached)", "url": "https://api.nexscope.ai/openapi.json", "seen": "2026-11-10" }, { "what": "MCP endpoint, one unauthenticated GET (client error)", "url": "https://api.nexscope.ai/mcp", "seen": "2026-11-10" }, { "what": "official MCP registry entries io.github.nexscope/ecommerce 1.0.0 to 1.0.3", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=nexscope", "seen": "2026-11-10" }, { "what": "API repository (README, catalogue, schemas, clients, source notes, 1688 guide, CI), shallow clone", "url": "https://github.com/nexscope-ai/nexscope-ecommerce-api", "seen": "2026-11-10" }, { "what": "eCommerce skills repository (prompt skills from 18 March 2026), shallow clone", "url": "https://github.com/nexscope-ai/eCommerce-Skills", "seen": "2026-11-10" }, { "what": "npm `nexscope` skills CLI (1.0.0 to 1.0.5, 20 March 2026), tarball read as text", "url": "https://registry.npmjs.org/nexscope", "seen": "2026-11-10" }, { "what": "domain registration (RDAP)", "url": "https://rdap.identitydigital.services/rdap/domain/nexscope.ai", "seen": "2026-11-10" }, { "what": "Wayback Machine availability (closest copy 10 October 2026)", "url": "https://archive.org/wayback/available?url=nexscope.ai\u0026timestamp=20260301", "seen": "2026-11-10" } ], "openQuestions": [ "unchecked: the hosted MCP tools/list, its input schemas, annotations and error shape (no session opened). The tool list and arguments come from the MCP map, one tool page and the repository", "unchecked: the OAuth protected-resource and authorisation-server metadata on api.nexscope.ai, which the batch kept off limits, so dynamic client registration, revocation and token lifetimes are unknown", "unchecked: the OpenAPI file's components section (the `bearerAuth` scheme, `SkillApiSemanticError` and `SkillApiHttpStatus`), which our reader didn't reach in a 3.8 MB file", "unchecked: the MCP docs page (/mcp, linked from the home page and quickstart) and /mcp-docs (linked from the repository), which both answered a client error to our reader", "unchecked: what the per-category endpoints at api.nexscope.ai/mcp/legacy?category=... answer, and whether a client can connect to one category alone", "Whether failed calls are charged. The pricing page and quickstart don't say. The repository mentions a failure refund for the WooCommerce APIs only", "The home page listed Growth at $69 a month ($34.50 first month) while the pricing page listed $55 ($27.50) on 10 November 2026. Recorded, not deducted", "Tool counts differ by source, with 382 on the MCP map, 252 APIs in the repository README, 238 in its source notes. Recorded as documentation drift", "No registration number or address for ECOCREATE TECHNOLOGY PTE. LTD. on the terms or privacy pages, and Singapore's register wasn't searched", "Repository commits after 10 September come from addresses on fzzixun.com, the npm `nexscope` README names git.ziniao.com/nexscope, and the 1688 guide calls LinkFox Agent a strategic partner. No first-hand page states how these relate to ECOCREATE", "unchecked: GitHub stars, issues and CI results (GitHub's API refused us), and npm weekly downloads" ] }, "negative": 0, "verdict": "An agent can reach Amazon, TikTok Shop, Temu, 1688 and other marketplace data, plus image and video models, on one credit balance through a remote MCP server with OAuth or a REST API with a public OpenAPI file. The connection loads 382 tools at once, and there is no status page, changelog or idempotency key.", "bestFor": "Agents that research ecommerce products, competitors, keywords, sourcing and patents across Amazon, TikTok Shop, Walmart, Temu, 1688 and other marketplaces, and that also make listing images and video, on one credit balance.", "strengths": [ "Marketplace product, keyword, competitor and sourcing data across more than ten marketplaces behind one key and one MCP endpoint", "OAuth 2.1 with PKCE and a `mcp:tools` scope on the MCP server, or a Bearer key shown once", "A public OpenAPI 3.1 file and a GitHub repository with request and response definitions, samples and standard-library clients for every documented API", "Per-plan API and MCP request limits published, and a 3-day trial of 1,000 credits with no card", "1688 order, payment-link, receipt and cancel calls each need an explicit JSON `true` confirmation field" ], "weaknesses": [ "The MCP connection advertises the full catalogue of 382 tools, with no toolsets or read-only subset", "No status page, SLA, public changelog or security.txt found", "No idempotency keys, and business errors answer HTTP 200 unless a header asks otherwise", "The privacy policy states no retention periods and names no hosting, AI or data suppliers", "Many Data definitions are field descriptors rather than JSON Schema, and the Amazon Search tool page omits the `keyword` argument its own examples pass" ], "agentNotes": [ "Check the outer `code` is 0 before reading `data`, or send `X-Nexscope-Http-Status: semantic` to get HTTP error statuses.", "Call an image or video tool once, keep the `taskId`, and poll `nexscope_media_task_result`. A second call bills a second job.", "Read the tool's credit cost before a call. Each tool costs at least 10 credits and some cost over 300.", "Before you set a 1688 confirmation field to `true`, show the user the preview and get approval.", "If the server returns 429 or 503, wait for `Retry-After` when present and back off." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 46.2 } ], "editorialScores": { "ergonomics": 44, "maintenance": 65, "payments": 35, "reliability": 39, "schema": 64, "security": 41, "transparency": 33 }, "provenanceScore": 48, "checked": { "categories": { "ergonomics": "2026-11-10", "maintenance": "2026-11-10", "payments": "2026-11-10", "reliability": "2026-11-10", "schema": "2026-11-10", "security": "2026-11-10", "transparency": "2026-11-10" }, "last": "2026-11-10", "oldest": "2026-11-10", "stale": false, "staleAfterDays": 90 }, "scoreHistory": [ { "date": "2026-11-10", "grade": "D", "kind": "listed", "method": "0.7", "score": 46.2 } ] }, "connect": { "http": "curl --fail-with-body -X POST 'https://api.nexscope.ai/api/skill-api/v1/skills/amazon-search/run' \\\n -H \"Authorization: Bearer $NEXSCOPE_API_KEY\" \\\n -H 'Content-Type: application/json' \\\n -H 'X-Nexscope-Http-Status: semantic' \\\n -d '{\"keyword\":\"phone case\",\"page\":1}'", "config": { "mcpServers": { "nexscope": { "headers": { "Authorization": "Bearer YOUR_NEXSCOPE_API_KEY" }, "type": "streamableHttp", "url": "https://api.nexscope.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.extract", "tool": "https://letme.dev/nexscope" }, "notable": [ "One MCP connection advertises the whole catalogue, 382 tools on the MCP map, named `nexscope_\u003cslug\u003e`. The map's category manifests 'narrow metadata for your integration; the MCP connection still advertises the full catalog' (https://www.nexscope.ai/mcp-map)", "Data tools cover Amazon, Walmart, Temu, TikTok Shop, Shopee, Etsy, eBay, Ozon, Mercado Libre, Shopify and WooCommerce stores, 1688 sourcing, Google trends, SEO and backlinks, patents and IP risk. Creative tools resell image and video models such as Seedance, Kling, MiniMax and GPT Image (https://www.nexscope.ai/mcp-map, https://github.com/nexscope-ai/nexscope-ecommerce-api)", "Fourteen 1688 procurement operations act on the user's own authorised 1688 buyer account, including create order, payment URL, confirm receipt and cancel, each needing a JSON `true` confirmation field. Authorisation runs through LinkFox Agent, which the guide calls 'Nexscope's strategic partner in China' (https://github.com/nexscope-ai/nexscope-ecommerce-api/blob/main/docs/1688-procurement-guide.md)", "The repository's source notes say supplier references in display names and descriptions 'are presented as Nexscope', while parameter names such as `includeSellerSpriteData` and slugs such as `chuhaijiang-tiktok-product-search` keep upstream names (https://github.com/nexscope-ai/nexscope-ecommerce-api/blob/main/docs/source-notes.md)", "By default a business error answers HTTP 200 with a nonzero outer `code`. The `X-Nexscope-Http-Status: semantic` header maps them to HTTP error statuses (https://www.nexscope.ai/api-docs/quickstart?tab=data)", "The MCP map tells agents to summarise capabilities by category before asking the user, never to guess required arguments or credentials, and to call asynchronous generation once and poll `nexscope_media_task_result` (https://www.nexscope.ai/mcp-map)" ], "area": "web-data", "details": [ { "label": "Surface listed", "value": "The remote MCP server at https://api.nexscope.ai/mcp and the REST API at https://api.nexscope.ai, both on one credit balance. Read on 10 November 2026 from www.nexscope.ai (home, pricing, terms, privacy, llms.txt, the API quickstart, the MCP map and one tool page, the agent setup help page), the OpenAPI file on api.nexscope.ai, the official MCP registry, RDAP, npm and shallow clones of nexscope-ai/nexscope-ecommerce-api and nexscope-ai/eCommerce-Skills read as text. No account was made, no MCP session opened, no API called and nothing installed or run" }, { "label": "Kind", "value": "Listed as `platform`. The home page leads with the seller web app (data, images and videos for ecommerce, 'Start free' into the app), plans are sold on what the app does, and video creation is app-only on the trial. The REST API and the MCP server are two of several surfaces, so the MCP and API lines are read where the checklist asks about them" }, { "label": "MCP server", "value": "Streamable HTTP at https://api.nexscope.ai/mcp, protocol 2025-11-25, OAuth 2.1 with PKCE (scope `mcp:tools`) or a Bearer `nk-` key. The registry entry `io.github.nexscope/ecommerce` (latest 1.0.3, 16 October 2026) names the same remote. Versions 1.0.0 and 1.0.1 of 14 October named https://api.nexscope.ai/api/skill-api/v2/mcp. Category schema pages sit at api.nexscope.ai/mcp/legacy?category=..., not read. One unauthenticated GET to /mcp answered a client error" }, { "label": "Tools", "value": "382 on the MCP map, in about 50 groups, among them Amazon Ads (55), TikTok Commerce Intelligence (37), multimodal image tools (34), Patent Intelligence (15), Backlinks Authority (15), WooCommerce (11) and video models (12), plus `nexscope_media_task_result` for async jobs. Each tool page lists typed arguments with defaults, enums and length limits, credits per call and a response field table. No annotations are documented. The hosted tools/list was not read" }, { "label": "HTTP API", "value": "OpenAPI 3.1 at https://api.nexscope.ai/openapi.json ('Nexscope Ecommerce Data, SEO, and Creative APIs', version 2026-08-28-public-catalog-v1, about 3.8 MB). Each tool runs at `POST /api/skill-api/v1/skills/{slug}/run`, with short aliases such as `/ai/designSimilaritySearch`, Bearer security per operation and one shared semantic error response for 400 to 504. Visible request bodies are typed with `additionalProperties: false`. Responses are open `data` objects. The components section wasn't reached" }, { "label": "GitHub repository", "value": "nexscope-ai/nexscope-ecommerce-api documents 252 APIs (199 Data, 53 Creative), each with a reference page, a request and response definition (166 as field descriptors, 86 as JSON Schema), a sample payload and a response fixture, and cURL, JavaScript and Python clients using only standard libraries. Eight commits from 10 September to 10 November 2026. A CI workflow runs offline validation. It says 'this repository is not an MCP server implementation'" }, { "label": "Upstream suppliers", "value": "The source notes say supplier references in names and descriptions 'are presented as Nexscope'. Upstream names remain in parameters and slugs (`includeSellerSpriteData`, `chuhaijiang-...`), in letter-coded tool groups on the MCP map (JM, JS, KP, SF, ST, ZY, CJ and others) and a JEV group, and the 1688 guide names LinkFox Agent as 'Nexscope's strategic partner in China'. The terms say market data 'may be incomplete, outdated, or unavailable and should be independently verified'" }, { "label": "Limits and errors", "value": "Per plan, with the same numbers for API and MCP, 1 request a second and 1 concurrent on the trial, 3 and 2 on Starter, 5 and 4 on Growth, 10 and 8 on Pro. 429 is an 'execution admission rate limit' and 503 temporary unavailability, both with `Retry-After` when present. Named codes on the quickstart are 11209 (missing or invalid key) and 12001 (expired website session), which may come back as HTTP 200. The repository advises 'Do not blindly retry POST requests'" }, { "label": "Version history", "value": "Domain registered 4 March 2026. npm `nexscope` 1.0.0 to 1.0.5 on 20 March 2026 installs prompt skills from nexscope-ai/eCommerce-Skills (commits from 18 March 2026), which call no Nexscope API. The launch post, dated 'Updated Aug 07, 2026', names API, MCP and Skills. The API repository dates its snapshot of a public directory of 225 APIs to 10 September 2026. Registry versions 1.0.0 to 1.0.3 on 14 and 16 October 2026. WooCommerce APIs added 29 October, design search 2 November and 1688 procurement 9 November 2026. No changelog" } ], "unitPrices": [ { "item": "Nexscope credit (Starter)", "unit": "credit", "usd": 0.00097, "note": "$29 a month for 30,000 credits, half price in the first month. Credits reset monthly" }, { "item": "Nexscope credit (Pro)", "unit": "credit", "usd": 0.00086, "note": "$129 a month for 150,000 credits" }, { "item": "Amazon Search tool call (Starter)", "unit": "call", "usd": 0.029, "note": "A recent average of 30 credits, range 16 to 94, per the MCP tool page on 10 November 2026. About 20 results a page" }, { "item": "Starter plan", "unit": "month", "usd": 29, "note": "30,000 credits, 3 API and 3 MCP requests a second, 2 concurrent each" } ], "provenance": { "legalEntity": "ECOCREATE TECHNOLOGY PTE. LTD.", "domain": "nexscope.ai", "domainRegistered": "2026-03-04", "domainNote": "RDAP (Identity Digital) gives nexscope.ai a registration date of 4 March 2026 through GoDaddy, with the registrant behind Domains By Proxy. The terms and privacy policy name ECOCREATE TECHNOLOGY PTE. LTD., 'a company incorporated in Singapore', with no registration number or street address.", "endpointOnVendorDomain": true, "terms": "https://www.nexscope.ai/terms", "privacy": "https://www.nexscope.ai/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-10", "notes": [ "The terms (last updated 8 October 2026) name ECOCREATE TECHNOLOGY PTE. LTD. under the laws of Singapore with SIAC arbitration seated in Singapore, cap liability at the amount paid in the six months before a claim, promise no availability, permit the official APIs and MCP integrations within plan limits, forbid bots and scrapers outside them, and give notice of material changes through the service or by email.", "The privacy policy (last updated 8 October 2026) names the same company, says uploaded materials are not used to train AI models, names Google Analytics, Microsoft Clarity, Ahrefs Analytics, Google Ads, X advertising and FirstPromoter, lists hosting, storage, AI processing, payment, email, support and authentication providers only by type, gives no retention periods ('this policy does not specify a single deletion deadline for all data') and mentions no DPA.", "https://www.nexscope.ai/.well-known/security.txt answered a client error. No status page or changelog is linked from the home page, llms.txt, the API quickstart or the MCP map.", "robots.txt on www.nexscope.ai gives `*` and twelve named crawlers, ClaudeBot among them, the same rules and disallows /api/ and /share/. Nothing there was fetched. api.nexscope.ai publishes no robots.txt (/robots.txt answers a JSON login error). Only /openapi.json and one GET to /mcp were sent there, per the batch. The MCP registry's /robots.txt answered a client error.", "firstReleased is 2026-08-07, the date on Nexscope's launch post ('Updated Aug 07, 2026', no earlier publication date shown), which names API, MCP and Skills as the ways to connect an agent and 1,000 free starting credits. The API repository dates its snapshot of an already public directory of 225 APIs to 10 September 2026, and the OpenAPI version label is 2026-08-28-public-catalog-v1. The domain dates from 4 March 2026 and the npm `nexscope` skills CLI from 20 March 2026, but neither reaches the API. lastRelease is 2026-11-09, when the 1688 procurement API contracts were synced as released." ], "score": 48, "checks": [ { "check": "Legal entity named", "value": "ECOCREATE TECHNOLOGY PTE. LTD.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "nexscope.ai, registered 2026-03-04 (under a year)", "points": 0, "max": 15, "state": "no" }, { "check": "Endpoint on the vendor's domain", "value": "api.nexscope.ai", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "published, not read by us yet", "points": 4, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "published, not read by us yet", "points": 4, "max": 10, "state": "part" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "1 named with their role, none with a public profile", "points": 7, "max": 10, "state": "part" }, { "check": "Support route", "value": "a support address, help pages, a community", "points": 5, "max": 5, "state": "ok" } ] }, "humans": { "slug": "nexscope", "checked": "2026-11-10", "company": "ECOCREATE TECHNOLOGY PTE. LTD.", "people": [ { "name": "Evan Huang", "role": "AI Engineer and Agent Developer, Nexscope", "page": "/people/evan-huang/" } ], "peopleNote": "Evan Huang's role is from his author page on the Nexscope blog ('AI Engineer \u0026 Agent Developer, Nexscope'), which links only the company's accounts, so no personal profile is listed. No founder or officer is named on any first-hand page read. The home page, pricing, terms and privacy policy (both last updated 8 October 2026) name only Nexscope and ECOCREATE TECHNOLOGY PTE. LTD., 'a company incorporated in Singapore', with no registration number or address, and the launch post is bylined 'Nexscope Team'. Commit authors on the GitHub repositories and npm maintainers are not roles and were not used, nor was the submitter's name. Repository commits from fzzixun.com addresses, an npm README naming git.ziniao.com/nexscope and the 1688 guide's 'strategic partner in China', LinkFox Agent, are recorded in the dossier, and no first-hand page states a relation between them and ECOCREATE. Ownership is private from the terms' ECOCREATE TECHNOLOGY PTE. LTD. The Singapore register was not read. Investors were looked for on www.nexscope.ai (home, pricing, terms, privacy, llms.txt, the launch post, with no press or funding page linked) and in three web searches for ECOCREATE TECHNOLOGY PTE. LTD., Nexscope with funding and seed, and Nexscope with founder and CEO, which returned unrelated companies, directory pages and Nexscope's own blog. No round, backer or accelerator was found.", "companySocial": { "linkedin": "https://www.linkedin.com/company/nexscope-ai/", "x": "https://x.com/Nexscope_ai", "github": "https://github.com/nexscope-ai" }, "support": { "emails": [ "service@nexscope.ai" ], "urls": [ "https://www.nexscope.ai/api-docs", "https://www.nexscope.ai/mcp-map", "https://www.nexscope.ai/help/skills-external-access" ], "community": [ { "label": "YouTube", "url": "https://www.youtube.com/@Nexscope-AI", "kind": "link" } ], "contactEmails": [ "service@nexscope.ai" ], "contactUrls": [ "https://www.nexscope.ai/coffee-chat" ] }, "sources": [ "https://www.nexscope.ai/", "https://www.nexscope.ai/terms", "https://www.nexscope.ai/privacy", "https://www.nexscope.ai/blog/author/evan-huang", "https://www.nexscope.ai/blog/nexscope-ai-agent-launch", "https://github.com/nexscope-ai/nexscope-ecommerce-api" ], "ownership": { "status": "private", "checked": "2026-11-10", "sources": [ "https://www.nexscope.ai/terms" ] } }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nexscope.json", "live": { "slug": "nexscope", "probe": { "target": "https://api.nexscope.ai/mcp", "method": "get", "lastAt": "2026-11-11T06:47:58.183177825Z", "lastOk": true, "lastStatus": 405, "lastMs": 262, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 271, "p95ms24h": 358, "samples24h": 41, "samples30d": 41, "days": [ { "date": "2026-11-11", "probes": 41, "ok": 41 } ], "since": "2026-11-11T02:53:20.057234625Z" }, "githubStars": 18, "updatedAt": "2026-11-11T06:47:58.183177825Z" }, "streak": { "days": 0, "from": "2026-11-11", "sinceWatching": true, "best": 0 } } }