vendor_coverage
Pack: vendor-signals · Endpoint: https://gateway.pipeworx.io/vendor-signals/mcp
Which software vendors are tracked for changelog and release activity, and how healthy each feed is — the vendor name, its domain, what kind of source is watched (changelog feed vs GitHub releases), when it was last polled successfully, and how many changes are on file. Call this before concluding a vendor has been quiet: a vendor that is not on this list has no data rather than no activity. Example: vendor_coverage({}); vendor_coverage({ vendor: “stripe” }). Keyless.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
vendor | string | no | Optional — check one vendor by name or domain |
Example call
Arguments
{}
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_coverage","arguments":{}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('vendor_coverage', {});
More examples
{
"vendor": "stripe"
}
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"vendor-signals": {
"url": "https://gateway.pipeworx.io/vendor-signals/mcp"
}
}
}
See Getting Started for client-specific install steps.