Vendor Signals MCP server

Vendor Signals — what your accounts just shipped

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

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

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: "vendornottracked" 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.

vendorsignalsweep 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: vendordocsources (seeded by scripts/ingest-vendor-signals.mjs --seed). Schema: supabase/migrations/vendorsignals.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///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.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/vendor-signals/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.