Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://gateway.pipeworx.io/vendor-signals/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http io.github.pipeworx-io-vendor-signals https://gateway.pipeworx.io/vendor-signals/mcpRun in a terminal.
{ "mcpServers": { "io.github.pipeworx-io-vendor-signals": { "command": "npx", "args": [ "-y", "mcp-remote", "https://gateway.pipeworx.io/vendor-signals/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchTools
No tool list yet. Remote servers get one after the first health check.
FAQ
Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS (fleet #545).
{ "mcpServers": { "io.github.pipeworx-io-vendor-signals": { "url": "https://gateway.pipeworx.io/vendor-signals/mcp", "headers": {} } }}Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: PIPEWORX_API_KEY.
Vendor Signals is reached over HTTP.
Last checked 2026-11-10. Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS (fleet #545).
From the publisher
README is not crawled yet. Open the repository
Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS (fleet #545).
© 2026 MCP Directory.