@pipeworx/vendor-signals

Connect: https://gateway.pipeworx.io/vendor-signals/mcp · Install: one-click buttons

Tools: 3

Changelog entries, release notes and product announcements for 31 tracked software vendors, dated and linked, joinable by domain against a target list.

The GTM read

“This account just shipped X” is a reason to reach out. That is the unit here — a dated, sourced change attached to a vendor — not developer news, which dev-feeds already carries.

Tools

Auth

Keyless.

The distinction this pack is built around

“Tracked but quiet” and “not tracked” are different answers, and a seller acts differently on each. Returning an empty list for both would make an unwatched account look like a dormant one.

• Tracked and quiet → found: true, count: 0 plus a note saying it is a real quiet period.
• Not tracked → found: false, reason: "vendor_not_tracked" and an explicit statement that this is missing coverage, not missing activity.
• Feed currently failing → flagged on the response, because an empty result then means unknown, not inactive.

vendor_signal_sweep returns quiet_vendors for the same reason: a vendor in neither list is not tracked at all.

Scope

Structured publisher feeds only — changelog RSS/Atom and GitHub releases. Deliberately not a general web-diffing crawler. Titles, summaries and links are stored; full page content is never retained.

Vendor list: vendor_doc_sources (seeded by scripts/ingest-vendor-signals.mjs --seed). Schema: supabase/migrations/*_vendor_signals.sql.

Things the next person would otherwise rediscover

• A dead feed does not error — it returns zero entries and looks healthy. Slack’s changelog feed answers HTTP 200 with text/html and no entries; six of thirty candidates behaved this way (Cloudflare, Linear, Twilio, Datadog, Atlassian, Slack on their first-guess URLs). Every candidate was probed before seeding, and the poller treats zero parseable entries as a failure, not a quiet success, so a rotted feed surfaces in vendor_coverage instead of silently reporting “no changes” forever.
• GitHub releases.atom is the reliable fallback when a vendor has no changelog feed — https://github.com/<org>/<repo>/releases.atom works for most vendors with a public SDK, and is how Twilio, Linear, Datadog and Slack are covered here.
• Vercel’s feed returns ~1,500 entries where most return 10. Any per-source assumption of a small page is wrong.
• Prefer: return=minimal answers 201 with an empty body, not 204 — code that switches on 204 alone will try to parse nothing.

Tools

• vendor_recent_changes — 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 S
• vendor_signal_sweep — 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 prioritis
• vendor_coverage — 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), w