@pipeworx/mcp-einpresswire 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Mojibake Inc.
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md ADDED
@@ -0,0 +1,153 @@
1
+ # @pipeworx/einpresswire
2
+
3
+ Live press releases from EIN Presswire's public news sitemap — headline,
4
+ publish time, keyword tags and geo location, newest first.
5
+
6
+ Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1679+ live data sources.
7
+
8
+ ## Tools
9
+
10
+ - `einpresswire_latest_releases(since_hours?, limit?)` — the current rolling
11
+ window of releases, newest first. `newest_item_at` tells a caller whether
12
+ the wire is quiet or stalled.
13
+ - `einpresswire_search_releases(query, limit?)` — keyword/company/place match
14
+ over headline, keyword tags and geo location, within the current window
15
+ only (there is no body excerpt in this source).
16
+ - `einpresswire_get_release(url)` — one specific release, matched by the URL
17
+ a prior call returned. Fails clearly (not silently empty) if the release is
18
+ older than roughly 48 hours.
19
+
20
+ ## Auth
21
+
22
+ Keyless. No account, no clickthrough terms.
23
+
24
+ ## Data sources
25
+
26
+ - <https://www.einpresswire.com/sitemap-news> — a Google-News-format XML
27
+ sitemap EIN Presswire itself lists as a `Sitemap:` entry in its
28
+ `robots.txt` (published for crawling, no account, no key). Verified live
29
+ 2026-09-21: HTTP 200, ~780 KB, 705 releases spanning roughly the trailing
30
+ 48 hours.
31
+
32
+ **Why this pack does NOT read RSS**, unlike its two sibling wire packs: EIN
33
+ Presswire's RSS is gated behind a free account. `/all-rss` is an HTML
34
+ directory page, and every category link it lists
35
+ (`/subscribe-rss/<category>`) 302-redirects to `/login`. "Requires an
36
+ account" is explicitly out of scope under the standing no-login sourcing
37
+ rule (logging in to scrape public data is not the same as scraping already-
38
+ public data). The sitemap is the genuinely public, keyless alternative for
39
+ this publisher — denser and fresher than the gated RSS would have been.
40
+
41
+ Because this is a sitemap and not RSS/Atom, the shared `parseFeed` parser
42
+ (`@pipeworx/shared`, built for `<item>`/`<entry>` blocks) does not apply here
43
+ — this pack has its own small `<url>`-block extraction. It does reuse
44
+ `canonicalUrl` from `@pipeworx/shared` for URL dedupe, the same helper the
45
+ RSS-based sibling packs use.
46
+
47
+ No structured issuer field is exposed by this source — the issuer is usually
48
+ the subject of the headline. No body excerpt either; only headline, keyword
49
+ tags, geo location and publish time.
50
+
51
+ ## Quick Start
52
+
53
+ Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
54
+
55
+ ```json
56
+ {
57
+ "mcpServers": {
58
+ "einpresswire": {
59
+ "url": "https://gateway.pipeworx.io/einpresswire/mcp"
60
+ }
61
+ }
62
+ }
63
+ ```
64
+
65
+ ### What this endpoint actually serves
66
+
67
+ `tools/list` at `https://gateway.pipeworx.io/einpresswire/mcp` returns the tools in the table
68
+ above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
69
+ `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
70
+ gateway-wide set. So the tool count you see is larger than this table: a
71
+ single-pack endpoint currently lists roughly 30 shared tools alongside the
72
+ pack's own. The connection's `initialize` response states its exact scope, and
73
+ is the authoritative answer for a given day.
74
+
75
+ This is deliberate, not multiplexing by accident. The meta-tools are what let a
76
+ scoped connection answer a question this pack does not cover — via
77
+ `ask_pipeworx`, which routes across the whole catalog — without you adding a
78
+ second MCP server. There is currently no way to mount a pack endpoint without
79
+ them; if the extra schemas cost you more context than the routing is worth,
80
+ connect to the full gateway once rather than to several pack endpoints.
81
+
82
+ Or connect to the full Pipeworx gateway to get every pack's tools listed
83
+ directly, instead of just this one's:
84
+
85
+ ```json
86
+ {
87
+ "mcpServers": {
88
+ "pipeworx": {
89
+ "url": "https://gateway.pipeworx.io/mcp"
90
+ }
91
+ }
92
+ }
93
+ ```
94
+
95
+ Both URLs reach the same gateway and the same 1679+ data sources. The
96
+ only difference is which pack's tools are listed **directly**; `ask_pipeworx`
97
+ reaches all of them from either one.
98
+
99
+ ## No MCP client? Call it over HTTP
100
+
101
+ ```bash
102
+ curl -X POST https://gateway.pipeworx.io/v1/tools/einpresswire_latest_releases \
103
+ -H 'Content-Type: application/json' \
104
+ -d '{}'
105
+ ```
106
+
107
+ 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":"..."}`.
108
+
109
+ ## Standalone (no gateway account)
110
+
111
+ This package also runs as a local stdio MCP server — no Pipeworx account, no
112
+ gateway round-trip:
113
+
114
+ ```json
115
+ {
116
+ "mcpServers": {
117
+ "einpresswire": {
118
+ "command": "npx",
119
+ "args": ["-y", "@pipeworx/mcp-einpresswire"]
120
+ }
121
+ }
122
+ }
123
+ ```
124
+
125
+ Or run it directly to confirm it starts:
126
+
127
+ ```bash
128
+ npx -y @pipeworx/mcp-einpresswire
129
+ ```
130
+
131
+ It speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`
132
+ for **only** this pack's tools — none of the shared meta-tools the gateway
133
+ connection above adds. Same source, same tools, no ask_pipeworx routing.
134
+
135
+ ## Using with ask_pipeworx
136
+
137
+ Instead of calling tools directly, you can ask questions in plain English —
138
+ this works on the pack endpoint above as well as on the full gateway:
139
+
140
+ ```
141
+ ask_pipeworx({ question: "your question about Einpresswire data" })
142
+ ```
143
+
144
+ The gateway picks the right tool and fills the arguments automatically.
145
+
146
+ ## More
147
+
148
+ - [Docs and guides](https://pipeworx.io/docs)
149
+ - [pipeworx.io](https://pipeworx.io)
150
+
151
+ ## License
152
+
153
+ MIT
package/bin/cli.js ADDED
@@ -0,0 +1,17 @@
1
+ #!/usr/bin/env node
2
+ //
3
+ // Entry point for `npx @pipeworx/mcp-<slug>`.
4
+ //
5
+ // Packs ship as raw TypeScript (no build step — see publish-pack.sh for why:
6
+ // tsx sidesteps every extensionless-import / bare-JSON-import edge case a
7
+ // per-pack tsc build would have to solve one pack at a time). This file
8
+ // registers tsx's ESM loader programmatically, then hands off to src/server.ts,
9
+ // which wraps the pack's {tools, callTool} export in a stdio MCP server.
10
+ //
11
+ // Copied verbatim into every published pack repo by scripts/publish-pack.sh —
12
+ // edit this file, not a per-pack copy.
13
+ import { register } from 'tsx/esm/api';
14
+
15
+ register();
16
+
17
+ await import('../src/server.ts');
package/package.json ADDED
@@ -0,0 +1,32 @@
1
+ {
2
+ "name": "@pipeworx/mcp-einpresswire",
3
+ "version": "0.1.0",
4
+ "description": "EIN Presswire MCP — press releases from EIN Presswire's public news",
5
+ "type": "module",
6
+ "main": "src/index.ts",
7
+ "types": "src/index.ts",
8
+ "bin": {
9
+ "mcp-einpresswire": "bin/cli.js"
10
+ },
11
+ "keywords": ["mcp", "mcp-server", "model-context-protocol", "pipeworx", "einpresswire"],
12
+ "license": "MIT",
13
+ "repository": {
14
+ "type": "git",
15
+ "url": "git+https://github.com/pipeworx-io/mcp-einpresswire.git"
16
+ },
17
+ "scripts": {
18
+ "typecheck": "tsc --noEmit"
19
+ },
20
+ "dependencies": {
21
+ "@modelcontextprotocol/sdk": "^1.30.0",
22
+ "tsx": "^4.19.0"
23
+ },
24
+ "devDependencies": {
25
+ "typescript": "^5.9.3",
26
+ "@cloudflare/workers-types": "^4.20260405.1"
27
+ },
28
+ "pipeworx": {
29
+ "sourceHash": "v1-6ef563b5cca0862f0f65b61aa0a21f9a0344535ce3ef86d59d09f014cbf91ca7",
30
+ "sourceCommit": "70cd53748fc9f9a43ed3681d751bfa96e701efd2"
31
+ }
32
+ }
package/server.json ADDED
@@ -0,0 +1,18 @@
1
+ {
2
+ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
3
+ "name": "io.github.pipeworx-io/einpresswire",
4
+ "title": "Einpresswire",
5
+ "description": "EIN Presswire MCP — press releases from EIN Presswire's public news",
6
+ "version": "0.1.0",
7
+ "websiteUrl": "https://pipeworx.io/packs/einpresswire",
8
+ "repository": {
9
+ "url": "https://github.com/pipeworx-io/mcp-einpresswire",
10
+ "source": "github"
11
+ },
12
+ "remotes": [
13
+ {
14
+ "type": "streamable-http",
15
+ "url": "https://gateway.pipeworx.io/einpresswire/mcp"
16
+ }
17
+ ]
18
+ }