@pipeworx/mcp-einpresswire 0.1.0 → 0.1.1
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/README.md +2 -2
- package/package.json +3 -3
- package/server.json +1 -1
- package/src/index.ts +36 -1
- package/src/server.ts +1 -1
package/README.md
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
Live press releases from EIN Presswire's public news sitemap — headline,
|
|
4
4
|
publish time, keyword tags and geo location, newest first.
|
|
5
5
|
|
|
6
|
-
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to
|
|
6
|
+
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1683+ live data sources.
|
|
7
7
|
|
|
8
8
|
## Tools
|
|
9
9
|
|
|
@@ -92,7 +92,7 @@ directly, instead of just this one's:
|
|
|
92
92
|
}
|
|
93
93
|
```
|
|
94
94
|
|
|
95
|
-
Both URLs reach the same gateway and the same
|
|
95
|
+
Both URLs reach the same gateway and the same 1683+ data sources. The
|
|
96
96
|
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
|
|
97
97
|
reaches all of them from either one.
|
|
98
98
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pipeworx/mcp-einpresswire",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"description": "EIN Presswire MCP — press releases from EIN Presswire's public news",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "src/index.ts",
|
|
@@ -26,7 +26,7 @@
|
|
|
26
26
|
"@cloudflare/workers-types": "^4.20260405.1"
|
|
27
27
|
},
|
|
28
28
|
"pipeworx": {
|
|
29
|
-
"sourceHash": "v1-
|
|
30
|
-
"sourceCommit": "
|
|
29
|
+
"sourceHash": "v1-559581f872501d0346bac3f69d3cbe08137a03dc29b6f95cad42f21edc2c9244",
|
|
30
|
+
"sourceCommit": "4fa4c64448be06f4a2ee4cee19f756f3558a7cad"
|
|
31
31
|
}
|
|
32
32
|
}
|
package/server.json
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"name": "io.github.pipeworx-io/einpresswire",
|
|
4
4
|
"title": "Einpresswire",
|
|
5
5
|
"description": "EIN Presswire MCP — press releases from EIN Presswire's public news",
|
|
6
|
-
"version": "0.1.
|
|
6
|
+
"version": "0.1.1",
|
|
7
7
|
"websiteUrl": "https://pipeworx.io/packs/einpresswire",
|
|
8
8
|
"repository": {
|
|
9
9
|
"url": "https://github.com/pipeworx-io/mcp-einpresswire",
|
package/src/index.ts
CHANGED
|
@@ -687,7 +687,42 @@ async function fetchWithTimeout(
|
|
|
687
687
|
),
|
|
688
688
|
);
|
|
689
689
|
}
|
|
690
|
-
|
|
690
|
+
// Fleet #2382. Everything that isn't a timeout/abort here is a genuine
|
|
691
|
+
// NETWORK-LEVEL failure — DNS resolution, connection refused, TLS handshake,
|
|
692
|
+
// Cloudflare's own "Network connection lost." — meaning `fetch()` itself
|
|
693
|
+
// threw and no HTTP response of any kind was ever received. Until this fix
|
|
694
|
+
// that raw exception was rethrown VERBATIM: a bare `TypeError: fetch failed`
|
|
695
|
+
// (or the Workers-runtime equivalent) names no upstream, carries no class
|
|
696
|
+
// token, and reads exactly like a defect in OUR code — because it says
|
|
697
|
+
// nothing about the call at all. It landed in `error`, the tier that means
|
|
698
|
+
// "Pipeworx has a defect", for every one of the (at the time of writing)
|
|
699
|
+
// ~470 packs that call this helper directly with no wrapper of their own.
|
|
700
|
+
//
|
|
701
|
+
// `dexscreener` hit this independently (fleet #1579) and fixed it with a
|
|
702
|
+
// bespoke per-pack try/catch around `fetchWithTimeout`. That fix is correct
|
|
703
|
+
// but only covers one pack; every other caller of this shared helper still
|
|
704
|
+
// leaked the raw exception. Moving the same fix HERE — the one place that
|
|
705
|
+
// already carries the timeout case — covers every pack that uses
|
|
706
|
+
// `fetchWithTimeout` without a wrapper, for free, and without widening
|
|
707
|
+
// `classifyToolError`'s regex list: the fix is giving the message a proper
|
|
708
|
+
// `upstream_down:` token at the point the two facts (no response was ever
|
|
709
|
+
// received, and which host we were trying to reach) are actually in hand,
|
|
710
|
+
// not teaching the classifier to guess from prose after the fact.
|
|
711
|
+
//
|
|
712
|
+
// Safe on the same grounds as the timeout branch above: no argument a
|
|
713
|
+
// caller passes can make `fetch()` itself throw a connection-level error,
|
|
714
|
+
// so this is always an availability failure, never a caller mistake. Same
|
|
715
|
+
// `markInternalOrigin` treatment — an origin we run that never answered is
|
|
716
|
+
// still ours, not a third party's outage.
|
|
717
|
+
const raw = err instanceof Error ? err.message : String(err);
|
|
718
|
+
throw new Error(
|
|
719
|
+
markInternalOrigin(
|
|
720
|
+
`upstream_down: could not reach ${name} at all (${raw.slice(0, 160)}). ` +
|
|
721
|
+
`No request reached ${name}, so this says NOTHING about whether the arguments you passed ` +
|
|
722
|
+
'are valid — do not re-check them on the strength of this error. Retry shortly.',
|
|
723
|
+
url,
|
|
724
|
+
),
|
|
725
|
+
);
|
|
691
726
|
}
|
|
692
727
|
}
|
|
693
728
|
|
package/src/server.ts
CHANGED
|
@@ -9,7 +9,7 @@ import { CallToolRequestSchema, ListToolsRequestSchema } from '@modelcontextprot
|
|
|
9
9
|
import pack from './index.js';
|
|
10
10
|
|
|
11
11
|
const server = new Server(
|
|
12
|
-
{ name: '@pipeworx/mcp-einpresswire', version: '0.1.
|
|
12
|
+
{ name: '@pipeworx/mcp-einpresswire', version: '0.1.1' },
|
|
13
13
|
{ capabilities: { tools: {} } },
|
|
14
14
|
);
|
|
15
15
|
|