Remote MCP · Endpoint

Prnewswire MCP server

No. Prnewswire answered an MCP handshake 13 hours ago.

UpLast checked 13 hours ago

Server URL

https://gateway.pipeworx.io/prnewswire/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/prnewswire
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
PR Newswire MCP — press releases from PR Newswire's all-releases feed.
Listing
From the official MCP registry (active).
Recent checks of Prnewswire
CheckedResultHandshake
13 hours agoHandshake completed71 ms
2 days agoHandshake completed59 ms
4 days agoHandshake completed54 ms
6 days agoHandshake completed48 ms
8 days agoHandshake completed89 ms
9 days agoHandshake completed219 ms
10 days agoHandshake completed85 ms
13 days agoHandshake completed39 ms
14 days agoHandshake completed48 ms
16 days agoHandshake completed41 ms
17 days agoHandshake completed61 ms
19 days agoHandshake completed44 ms
20 days agoHandshake completed1.19 s
21 days agoHandshake completed41 ms
21 days agoHandshake completed41 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Prnewswire and makes no claim about it beyond what these checks measured.