Remote MCP · Endpoint
Galley Render MCP server
Yes, as of 2 hours ago: the server returned an HTTP error.
DownLast checked 2 hours ago
Server URL
https://mcp.galleyrender.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- com.galleyrender/galley-render
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 20 tools
- Uptime, last 30 days
- 61.1% from 18 checks
- Described by its publisher as
- JSON in, PDF out. Render invoices, certificates, reports and cards from a template and a payload.
- Website
- https://galleyrender.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 10 days ago | Handshake completed | 255 ms |
| 12 days ago | Handshake completed | 138 ms |
| 15 days ago | Handshake completed | 261 ms |
| 17 days ago | Handshake completed | 171 ms |
| 19 days ago | Handshake completed | 154 ms |
| 21 days ago | Handshake completed | 273 ms |
| 23 days ago | Handshake completed | 329 ms |
| 25 days ago | Handshake completed | 236 ms |
| 26 days ago | Handshake completed | 106 ms |
| 28 days ago | Handshake completed | 148 ms |
| 29 days ago | Handshake completed | 150 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 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 Galley Render and makes no claim about it beyond what these checks measured.