EWIGSC Product Discovery

io.github.rww90931-opsPublished by GitHub account rww90931-opsv0.1.1Updated Oct 26, 2026

Search and compare EWIGSC wigs, toppers, and extensions; find first-party care guidance.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search and compare EWIGSC wigs, toppers and extensions, and find the brand's own care guidance.

What you can do
  • Search EWIGSC wigs, toppers and extensions
  • Compare products across the catalog
  • Retrieve first-party care guidance for the items found
When to use it
Useful when someone is shopping for or comparing EWIGSC hair products and wants an assistant to look up options and care advice from the brand itself.
Requirements
Runs as a local process installed from the npm package ewigsc-product-discovery-mcp over stdio; no accounts, API keys or environment variables are declared. Desktop-only client required.
Before you install
The catalog is limited to one brand's products, so results are not a general market comparison. No tool list or documentation is published, so what it can do beyond search, comparison and care guidance is unclear.

Installation

In SourceWeft

  1. Open EWIGSC Product Discovery in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestOct 17, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.