Remote MCP · Endpoint

Pixeloa MCP server

No. Pixeloa answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://pixeloa.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.pixeloa/pixeloa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.36 s
Tools exposed
20 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Turn product photos into true-scale 3D models and AR pages, then publish, embed and catalog them.
Listing
From the official MCP registry (active).
Recent checks of Pixeloa
CheckedResultHandshake
34 minutes agoHandshake completed1.36 s
8 days agoHandshake completed1.28 s
9 days agoHandshake completed747 ms
11 days agoHandshake completed901 ms
12 days agoHandshake completed1.12 s
12 days agoHandshake completed618 ms
14 days agoHandshake completed815 ms
14 days agoHandshake completed631 ms
16 days agoHandshake completed683 ms
19 days agoHandshake completed693 ms
21 days agoHandshake completed750 ms
24 days agoHandshake completed926 ms
26 days agoHandshake completed545 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 Pixeloa and makes no claim about it beyond what these checks measured.