Remote MCP · Endpoint

AutoPrint MCP server

No. AutoPrint answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://autoprintstudio.com/mcp

The last check completed an MCP handshake.

Registry name
com.auto-units/autoprint
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
152 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Print existing artwork on custom wall art, apparel, and gifts.
Website
https://autoprintstudio.com/
Listing
From the official MCP registry (active).
Recent checks of AutoPrint
CheckedResultHandshake
6 days agoHandshake completed152 ms
7 days agoHandshake completed115 ms
7 days agoHandshake completed1.90 s
9 days agoHandshake completed71 ms
10 days agoHandshake completed164 ms
11 days agoHandshake completed411 ms
12 days agoHandshake completed107 ms
13 days agoHandshake completed139 ms
15 days agoHandshake completed206 ms
17 days agoHandshake completed222 ms
20 days agoHandshake completed112 ms
22 days agoHandshake completed110 ms
24 days agoHandshake completed111 ms

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with AutoPrint and makes no claim about it beyond what these checks measured.