Remote MCP · Endpoint

PrintSanity MCP server

No. PrintSanity answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
137 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
1 hour agoHandshake completed137 ms
1 day agoHandshake completed386 ms
4 days agoHandshake completed191 ms
7 days agoHandshake completed126 ms
9 days agoHandshake completed151 ms
11 days agoHandshake completed160 ms
13 days agoHandshake completed391 ms
15 days agoHandshake completed227 ms
17 days agoHandshake completed179 ms
19 days agoHandshake completed121 ms
21 days agoHandshake completed354 ms
22 days agoHandshake completed180 ms
23 days agoCredentials required—

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