vendor_recent_changes

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_recent_changes for the schema, then POST the same URL with its arguments for the data.

What a software vendor shipped recently — changelog entries, release notes and product announcements with the date and a link to the source. Built for account research and outreach timing: “what did Stripe ship this month”, “has Vercel released anything lately”, “recent changes at supabase.com”. Look the vendor up by name or by domain (the domain is what a CRM or target list joins on). Returns each change with its published date, title, summary and URL. Says explicitly whether a vendor is tracked-but-quiet or not tracked at all, because those mean different things. Example: vendor_recent_changes({ vendor: “stripe”, days: 30 }); vendor_recent_changes({ vendor: “vercel.com” }). Keyless.

Parameters

Example call

Arguments

{
  "vendor": "stripe",
  "days": 30
}

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_recent_changes","arguments":{"vendor":"stripe","days":30}}}'

TypeScript (@pipeworx/sdk)

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

const result = await pipeworx.call('vendor_recent_changes', {
  "vendor": "stripe",
  "days": 30
});

More examples

{
  "vendor": "vercel.com"
}

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.