Remote MCP · Endpoint

Epo Publication Server MCP server

No. Epo Publication Server answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://gateway.pipeworx.io/epo-publication-server/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/epo-publication-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
47 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
EPO European Publication Server (EPS) MCP
Listing
From the official MCP registry (active).
Recent checks of Epo Publication Server
CheckedResultHandshake
42 minutes agoHandshake completed47 ms
8 days agoHandshake completed89 ms
9 days agoHandshake completed89 ms
11 days agoHandshake completed108 ms
12 days agoHandshake completed113 ms
13 days agoHandshake completed176 ms
14 days agoHandshake completed75 ms
15 days agoHandshake completed145 ms
16 days agoHandshake completed328 ms
19 days agoHandshake completed56 ms
22 days agoHandshake completed131 ms
24 days agoHandshake completed64 ms
26 days agoHandshake completed1.96 s

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

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