@pipeworx/businesswire

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

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

Live press releases from Business Wire’s all-news RSS channel — headline, dateline, publish time, excerpt and Business Wire’s own release id, newest first, across roughly the last seven days of the whole wire.

Tools

• businesswire_latest_releases(since_hours?, limit?) — the newest releases in the current window (up to 100 per call). newest_item_at and oldest_item_at tell a caller how wide the live window is right now.
• businesswire_search_releases(query, since_hours?, limit?) — keyword or company match over headline, dateline and excerpt across the whole window (~3,500 releases measured).
• businesswire_get_release(url) — one specific release by the URL or release_id a prior call returned. Fails clearly (not silently empty) if the release has aged out of the window.

Auth

Keyless. No account, no clickthrough terms.

Data sources

• https://feed.businesswire.com/rss/home/?rss=G1QFDERJXkJcFVJYWQ== — Business Wire’s all-news channel. Measured 2026-09-22: 3,492 items, oldest 2026-09-15, newest 2026-09-22, ~4 MB of XML in under half a second.

Every call re-fetches this window live — it is not an archive. A release older than about a week is no longer in it (the tools say so rather than returning nothing silently).

Why an earlier probe called this wire dead

The wave-1 press-release probe (fleet #2285) recorded Business Wire as “a 993-byte 200 with an empty items array”. Those bytes are a well-formed RSS envelope with zero items whose channel <description> reads “RSS channel ID is not available in the request. Please make sure you have a valid RSS link.” — Business Wire answers a missing or invalid rss= token with HTTP 200 and an error written inside the channel (reproduced at 1,001 bytes with ?rss=bogus). A status code cannot tell that apart from a quiet feed; this pack checks for it and reports it as a broken token, not an empty wire.

Where the feed token comes from

www.businesswire.com sits behind Akamai and answers a non-browser User-Agent with 403 on every path — including its own robots.txt and the RSS index page. feed.businesswire.com is a separate host that serves this pack’s own identity (pipeworx-mcp/1.0) without complaint, and its robots.txt publishes the all-news token in a Sitemap: line. Tokens are opaque per-channel ids; per-industry channels exist (G1QFDERJXkJeEFpRVQ== is “Communications News”) but the index that maps them lives on the blocked host, so this pack reads the all-news channel only.

Item shape

Business Wire’s items carry no issuer tag. The description opens with the wire’s dateline (BENGALURU, India--(BUSINESS WIRE)--Rippling, ...), which this pack splits into dateline and excerpt; the issuer usually leads the excerpt but is not a separate field. Links carry a per-feed feedref= tracking token, stripped into canonical_url. release_id is the feed’s <guid> (e.g. 20260921847964en).

Tools

• businesswire_latest_releases — Latest press releases from Business Wire’s all-news RSS channel (source: businesswire.com). Returns headline,
• businesswire_search_releases — Keyword/company search over Business Wire’s current all-news channel (source: businesswire.com). Matches
• businesswire_get_release — Fetch one specific Business Wire release by its URL or release id (source: businesswire.com), as returned