Remote MCP · Endpoint

Einpresswire MCP server

No. Einpresswire answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/einpresswire
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
104 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
EIN Presswire MCP — press releases from EIN Presswire's public news
Listing
From the official MCP registry (active).
Recent checks of Einpresswire
CheckedResultHandshake
1 day agoHandshake completed104 ms
4 days agoHandshake completed60 ms
6 days agoHandshake completed339 ms
7 days agoHandshake completed126 ms
9 days agoHandshake completed55 ms
10 days agoHandshake completed218 ms
11 days agoHandshake completed55 ms
14 days agoHandshake completed48 ms
15 days agoHandshake completed69 ms
17 days agoHandshake completed249 ms
19 days agoHandshake completed49 ms
20 days agoHandshake completed925 ms
21 days agoHandshake completed801 ms
22 days agoHandshake completed57 ms
22 days agoHandshake completed69 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 Einpresswire and makes no claim about it beyond what these checks measured.