Remote MCP · Endpoint

Kimage MCP server

No. Kimage answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://kimage.kaneky.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.kaneky/kimage
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
418 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Generate original images from text; prompts and results are content-checked. Paid per image, x402.
Listing
From the official MCP registry (active).
Recent checks of Kimage
CheckedResultHandshake
52 minutes agoHandshake completed418 ms
2 days agoHandshake completed174 ms
4 days agoHandshake completed504 ms
5 days agoHandshake completed427 ms
7 days agoHandshake completed487 ms
8 days agoHandshake completed441 ms
9 days agoHandshake completed534 ms
12 days agoHandshake completed412 ms
13 days agoHandshake completed422 ms
15 days agoHandshake completed398 ms
17 days agoHandshake completed396 ms
18 days agoHandshake completed407 ms
19 days agoHandshake completed405 ms
20 days agoHandshake completed404 ms
21 days agoHandshake completed402 ms
21 days agoHandshake completed542 ms

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

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