Remote MCP · Endpoint

InkRoom MCP server

No. InkRoom answered an MCP handshake 22 minutes ago.

UpLast checked 22 minutes ago

Server URL

https://mcp.inkroom.ai/

The last check completed an MCP handshake.

Registry name
io.github.InkRoomAI/inkroom
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
200 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Generate, edit and upscale images with references, batch jobs, cost previews and original downloads.
Listing
From the official MCP registry (active).
Recent checks of InkRoom
CheckedResultHandshake
22 minutes agoHandshake completed200 ms
9 days agoHandshake completed197 ms
10 days agoHandshake completed205 ms
11 days agoHandshake completed381 ms
12 days agoHandshake completed368 ms
14 days agoHandshake completed207 ms
14 days agoHandshake completed222 ms
15 days agoHandshake completed216 ms
17 days agoHandshake completed238 ms
19 days agoHandshake completed272 ms
21 days agoHandshake completed234 ms
24 days agoHandshake completed192 ms
26 days agoCredentials required—
28 days agoCredentials required—

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

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