Remote MCP · Endpoint

InkFE Print MCP server

No. InkFE Print answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.inkfe.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.inkfe/print
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
113 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Personalize business-card templates, review proofs, and prepare Shopify checkout.
Listing
From the official MCP registry (active).
Recent checks of InkFE Print
CheckedResultHandshake
1 hour agoHandshake completed113 ms
2 days agoHandshake completed64 ms
4 days agoHandshake completed144 ms
5 days agoHandshake completed79 ms
7 days agoHandshake completed78 ms
8 days agoHandshake completed256 ms
9 days agoHandshake completed80 ms
12 days agoHandshake completed102 ms
13 days agoHandshake completed85 ms
15 days agoHandshake completed159 ms
17 days agoHandshake completed103 ms
18 days agoHandshake completed93 ms
19 days agoHandshake completed103 ms
20 days agoHandshake completed93 ms
20 days agoHandshake completed626 ms
21 days agoHandshake completed3.40 s
22 days agoHandshake completed3.09 s

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 InkFE Print and makes no claim about it beyond what these checks measured.