The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Einpresswire listing page.
Live press releases from EIN Presswire's public news sitemap — headline, publish time, keyword tags and geo location, newest first.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
einpresswire_latest_releases(since_hours?, limit?) — the current rolling
window of releases, newest first. newest_item_at tells a caller whether
the wire is quiet or stalled.einpresswire_search_releases(query, limit?) — keyword/company/place match
over headline, keyword tags and geo location, within the current window
only (there is no body excerpt in this source).einpresswire_get_release(url) — one specific release, matched by the URL
a prior call returned. Fails clearly (not silently empty) if the release is
older than roughly 48 hours.Keyless. No account, no clickthrough terms.
Sitemap: entry in its
robots.txt (published for crawling, no account, no key). Verified live
2026-09-21: HTTP 200, ~780 KB, 705 releases spanning roughly the trailing
48 hours.Why this pack does NOT read RSS, unlike its two sibling wire packs: EIN
Presswire's RSS is gated behind a free account. /all-rss is an HTML
directory page, and every category link it lists
(/subscribe-rss/<category>) 302-redirects to /login. "Requires an
account" is explicitly out of scope under the standing no-login sourcing
rule (logging in to scrape public data is not the same as scraping already-
public data). The sitemap is the genuinely public, keyless alternative for
this publisher — denser and fresher than the gated RSS would have been.
Because this is a sitemap and not RSS/Atom, the shared parseFeed parser
(@pipeworx/shared, built for <item>/<entry> blocks) does not apply here
— this pack has its own small <url>-block extraction. It does reuse
canonicalUrl from @pipeworx/shared for URL dedupe, the same helper the
RSS-based sibling packs use.
No structured issuer field is exposed by this source — the issuer is usually the subject of the headline. No body excerpt either; only headline, keyword tags, geo location and publish time.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/einpresswire/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, 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:
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/einpresswire_latest_releases. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
Or run it directly to confirm it starts:
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
The gateway picks the right tool and fills the arguments automatically.
MIT