Vendor Signals MCP MCP server

An MCP server provided by Pipeworx that tracks software vendor documentation and changelog changes to generate account signals. It offers tools to retrieve recent changes from specific vendors, sweep across all tracked vendors for recent activity, and check the coverage health of tracked vendors, supporting account research and outreach timing.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Pipeworx

MCP endpoint (Streamable HTTP)

https://gateway.pipeworx.io/vendor-signals/mcp

Vendor documentation

What you can do with it

Retrieve recent changelog entries and release notes for a specific software vendor
Sweep across all tracked vendors to identify recent shipping activity for prospecting
Check which software vendors are tracked and the health of their data feeds

Tools advertised by the last live check:

ask_pipeworx
ask_pipeworx_beta
ask_pipeworx_grounded
search_within
deep_research
discover_tools
resolve_entity
compare_entities
subscribe
unsubscribe
list_subscriptions
recent_alerts
entity_profile
recent_changes
validate_claim
company_facts
scan_dependency
bet_research
polymarket_arbitrage
polymarket_edges
polymarket_kalshi_spread
polymarket_fill_risk
polymarket_edge_tracker
kalshi_weather_edge
resolution_audit
resolution_diff
release_calendar_markets
pipeworx_trending
suggest_questions
generate_llms_txt
ai_visibility_check
scan_competitor_ai_presence
pipeworx_feedback
remember
recall
forget
vendor_recent_changes
vendor_signal_sweep
vendor_coverage

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http vendor-signals-mcp https://gateway.pipeworx.io/vendor-signals/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add vendor-signals-mcp --url https://gateway.pipeworx.io/vendor-signals/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vendor-signals-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "vendor-signals-mcp": {
      "url": "https://gateway.pipeworx.io/vendor-signals/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "vendor-signals-mcp": {
      "type": "streamableHttp",
      "url": "https://gateway.pipeworx.io/vendor-signals/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vendor-signals-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "vendor-signals-mcp": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/vendor-signals/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http vendor-signals-mcp https://gateway.pipeworx.io/vendor-signals/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "vendor-signals-mcp": {
      "url": "https://gateway.pipeworx.io/vendor-signals/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "vendor-signals-mcp": {
      "serverUrl": "https://gateway.pipeworx.io/vendor-signals/mcp"
    }
  }
}

See all 1,583

Do you run Vendor Signals MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing