Newswire Com MCP server

@pipeworx/newswire-com

Live press releases from Newswire.com's public newsroom RSS feed — headline, publish time and sub-headline excerpt, newest first, for the 50 most recent releases. Newswire.com is an Issuer Direct wire, sibling to ACCESS Newswire, and carries a large share of the same releases.

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

Tools

window of releases, newest first (up to 50). newestitemat tells a caller whether the feed is quiet or stalled.

• newswirecomlatestreleases(sincehours?, limit?) — the current rolling

headline and excerpt, within the current window only.

• newswirecomsearch_releases(query, limit?) — keyword/company match over

a prior call returned. Fails clearly (not silently empty) if the release has scrolled out of the current window.

• newswirecomget_release(url) — one specific release, matched by the URL

Auth

Keyless. No account, no clickthrough terms. newswire.com/robots.txt disallows only the per-tag feeds and asks for Crawl-delay: 5; the gateway's per-call result cache keeps polling well below that.

Data sources

channel. Measured 2026-09-22: 50 items spanning roughly a day.

• — the newsroom "Press Releases"

Every call re-fetches this same rolling 50-item window live — it is not an archive. searchreleases only ever searches what is currently in the window and getrelease can miss something that has already fallen out of it (the tool says so explicitly rather than returning an empty result).

This feed carries no issuer field — the company name lives only in the headline or sub-headline — so issuer is null on every row rather than a guess parsed out of the headline.

The /feeds index page lists ~650 per-beat feeds (/newsroom/rss/beat/) and two "custom" feeds; every beat probed returned a bare nginx 404 and both custom feeds return HTTP 410 Gone (2026-09-22), so this pack does not enumerate them.

Relationship to ACCESS Newswire

ACCESS Newswire (formerly ACCESSWIRE) serves every feed path (/users/rss, /rss, /rss.xml, its sitemap index) and every article page behind a Cloudflare managed challenge (HTTP 403, cf-mitigated: challenge); its only open feeds, /feed/rss2 and /feed/atom, are its corporate blog, not the wire. Measured 2026-09-22: 12 of the 20 releases on ACCESS Newswire's newsroom landing page appeared verbatim in this feed. This pack is therefore the closest keyless, machine-readable surface to that wire — partial, not a mirror (fleet #2286).

Quick Start

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

{
  "mcpServers": {
    "newswire-com": {
      "url": "https://gateway.pipeworx.io/newswire-com/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/newswire-com/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.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

Shortened. The full README is on GitHub.