Remote MCP · Endpoint

Apology MCP server

No. Apology answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/apology
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.56 s
Tools exposed
42 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
apology MCP — wraps StupidAPIs (keyless — no credential needed)
Listing
From the official MCP registry (active).
Recent checks of Apology
CheckedResultHandshake
1 hour agoHandshake completed1.56 s
2 days agoHandshake completed119 ms
4 days agoHandshake completed69 ms
5 days agoHandshake completed62 ms
7 days agoHandshake completed103 ms
8 days agoHandshake completed2.17 s
9 days agoHandshake completed70 ms
12 days agoHandshake completed46 ms
14 days agoHandshake completed58 ms
15 days agoHandshake completed65 ms
17 days agoHandshake completed45 ms
18 days agoHandshake completed41 ms
19 days agoHandshake completed36 ms
20 days agoHandshake completed35 ms
20 days agoHandshake completed999 ms
22 days agoFailed - the request timed out—
23 days agoHandshake completed67 ms

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

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