Remote MCP · Endpoint

PrintSanity MCP server

No. PrintSanity answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://printsanity.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.chartsmartdev/printsanity
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
135 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Checks AI-made flyers, cards and posters will print right. Fixes proportions and broken QR codes.
Listing
From the official MCP registry (active).
Recent checks of PrintSanity
CheckedResultHandshake
7 hours agoHandshake completed135 ms
4 days agoHandshake completed461 ms
14 days agoHandshake completed141 ms
15 days agoHandshake completed203 ms
15 days agoHandshake completed154 ms
17 days agoHandshake completed203 ms
18 days agoHandshake completed149 ms
19 days agoHandshake completed132 ms
20 days agoHandshake completed136 ms
21 days agoHandshake completed137 ms
23 days agoHandshake completed386 ms
26 days agoHandshake completed191 ms
28 days agoHandshake completed126 ms

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

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