vendor_signal_sweep

Pack: vendor-signals · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/vendor_signal_sweep for the schema, then POST the same URL with its arguments for the data.

Recent shipping activity across every tracked software vendor at once, newest first — a single sweep for “which of these accounts have been active this week”. Use for prospecting and account prioritisation rather than researching one company: it surfaces which vendors shipped, how many changes each had, and the latest headline per vendor. Optionally narrow to a set of domains to match a target list. Example: vendor_signal_sweep({ days: 7 }); vendor_signal_sweep({ domains: [“stripe.com”, “twilio.com”], days: 14 }). Keyless.

Parameters

Example call

Arguments

{
  "days": 7
}

curl

curl -X POST https://gateway.pipeworx.io/vendor-signals/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"vendor_signal_sweep","arguments":{"days":7}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('vendor_signal_sweep', {
  "days": 7
});

More examples

{
  "domains": [
    "stripe.com",
    "twilio.com"
  ],
  "days": 14
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

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

See Getting Started for client-specific install steps.