Remote MCP · Endpoint

Globenewswire MCP server

No. Globenewswire answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/globenewswire
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
GlobeNewswire MCP — press releases from GlobeNewswire's public-company feed.
Listing
From the official MCP registry (active).
Recent checks of Globenewswire
CheckedResultHandshake
42 minutes agoHandshake completed98 ms
9 days agoHandshake completed153 ms
10 days agoHandshake completed162 ms
11 days agoHandshake completed107 ms
12 days agoHandshake completed58 ms
14 days agoHandshake completed141 ms
15 days agoHandshake completed102 ms
15 days agoHandshake completed150 ms
17 days agoHandshake completed187 ms
19 days agoHandshake completed63 ms
22 days agoHandshake completed55 ms
24 days agoHandshake completed78 ms
26 days agoHandshake completed469 ms
28 days agoHandshake completed525 ms

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

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 Globenewswire and makes no claim about it beyond what these checks measured.