Remote MCP · Endpoint

Imagemeta MCP server

No. Imagemeta answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://imagemeta.kaneky.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.kaneky/imagemeta
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
423 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Write SEO metadata (title, alt text, keywords, copyright) into JPEG, PNG, WebP. Paid per call, x402.
Listing
From the official MCP registry (active).
Recent checks of Imagemeta
CheckedResultHandshake
1 hour agoHandshake completed423 ms
9 days agoHandshake completed430 ms
10 days agoHandshake completed387 ms
11 days agoHandshake completed418 ms
12 days agoHandshake completed415 ms
14 days agoHandshake completed413 ms
14 days agoHandshake completed412 ms
15 days agoHandshake completed431 ms
17 days agoHandshake completed424 ms
19 days agoHandshake completed410 ms
21 days agoHandshake completed406 ms
24 days agoHandshake completed551 ms
26 days agoHandshake completed458 ms
28 days agoHandshake completed420 ms

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

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