Skip to content
mcp/skillhub

EWIGSC Product Discovery MCP Server

io.github.rww90931-ops/product-discoveryv0.1.1

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

Node.jsstdioofficial registry

context tax

pending

security

pending

cold start

pending

freshness

pending

Our reading of EWIGSC Product Discovery, from the data

EWIGSC Product Discovery is an MCP server, listed in the official MCP Registry.

We haven't measured its tool list yet, so its token cost is unknown.

It runs locally on your machine over stdio.

Install EWIGSC Product Discovery MCP server

Install in Claude Code

claude mcp add ewigsc-product-discovery -- npx -y ewigsc-product-discovery-mcp

Freshness

Not enough public signals yet to judge maintenance.

  1. Last commit (default branch)

    no data · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-10-17 · 2d ago · official registry · v0.1.1

FAQ

›How do I install the EWIGSC Product Discovery MCP server in Claude Code?

Run: claude mcp add ewigsc-product-discovery -- npx -y ewigsc-product-discovery-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does EWIGSC Product Discovery require an API key?

No required environment variables are declared in its published metadata.

›Can I use EWIGSC Product Discovery as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is EWIGSC Product Discovery in the official MCP registry?

Yes, as io.github.rww90931-ops/product-discovery.

Sources and method

Official MCP Registry entry
updated 2026-10-17
Package registry (npm / PyPI)
listed
Last checked against all sources
2026-10-19

The description, packages and links come from the maintainer's own published metadata. Token cost, security signals, freshness and the reading above are MCPSkillHub's own measurements; see the methodology. Spot an error? Request a correction or claim the listing.