MCP servers observed by Lowdown
io.github.nexscope/ecommerce MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 30 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.nexscope/ecommerce
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.nexscope/ecommerce?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 24 → 30
What tools does it list?
30 tools on 2026-11-16:
nexscope_1688_product_billboardnexscope_1688_product_detailnexscope_1688_product_searchnexscope_1688_search_by_imagenexscope_ai_apparel_image_set_photography_v3nexscope_ai_background_generatornexscope_ai_clothes_changer_for_tops_bottomsnexscope_ai_hand_repairnexscope_ai_model_pose_generationnexscope_ai_model_scene_background_replacementnexscope_ai_model_swapnexscope_ai_model_swap_2_0nexscope_ai_product_marketing_image_set_v4nexscope_ai_suit_virtual_try_onnexscope_ai_video_reclonenexscope_aliexpress_access_task_resultnexscope_aliexpress_category_productsnexscope_aliexpress_category_variantsnexscope_aliexpress_google_organic_searchnexscope_aliexpress_page_readnexscope_aliexpress_product_detailnexscope_aliexpress_product_searchnexscope_aliexpress_task_resultnexscope_amazon_ads_api_accessnexscope_amazon_ads_reportingnexscope_amazon_ads_sp_audience_reportnexscope_amazon_ads_sp_insights_report_downloadnexscope_amazon_ads_sp_insights_report_statusnexscope_amazon_ads_sp_search_impression_share_reportnexscope_amazon_advertising
MCP Registry declaration
- Registry name:
io.github.nexscope/ecommerce - Declared version: 1.0.3
- Status: active
- Declared hosts:
api.nexscope.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.nexscope/ecommerce", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.nexscope/ecommerce?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).