Skip to content
mcp/skillhub

Vendor Signals MCP Server

by pipeworx-ioio.github.pipeworx-io/vendor-signalsv0.1.2

Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS

0Node.jsstdioremoteofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active13d ago

Install Vendor Signals MCP server

Install in Claude Code

claude mcp add vendor-signals -- npx -y @pipeworx/mcp-vendor-signals

Remote endpoints

  • streamable-httphttps://gateway.pipeworx.io/vendor-signals/mcp

Freshness

Active — last maintenance signal 13d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-09-26 · 13d ago · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-09-26 · 13d ago · official registry · v0.1.2

FAQ

›How do I install the Vendor Signals MCP server in Claude Code?

Run: claude mcp add vendor-signals -- npx -y @pipeworx/mcp-vendor-signals. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Vendor Signals require an API key?

No required environment variables are declared in its published metadata.

›Can I use Vendor Signals as a remote (hosted) MCP server?

Yes — it offers both a hosted endpoint and a local stdio package.

›Is Vendor Signals in the official MCP registry?

Yes, as io.github.pipeworx-io/vendor-signals.

Alternatives to Vendor Signals

Other documentation MCP servers.

View all