Remote MCP · Endpoint

Pixly MCP server

No. Pixly answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://pixly.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.pixly/pixly
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
550 ms
Tools exposed
35 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Every visual AI tool for property listings — staging, enhancement, decluttering, cinematic video.
Listing
From the official MCP registry (active).
Recent checks of Pixly
CheckedResultHandshake
5 hours agoHandshake completed550 ms
2 days agoHandshake completed204 ms
4 days agoHandshake completed621 ms
5 days agoHandshake completed169 ms
7 days agoHandshake completed578 ms
8 days agoHandshake completed540 ms
9 days agoHandshake completed216 ms
12 days agoHandshake completed544 ms
13 days agoHandshake completed530 ms
15 days agoHandshake completed555 ms
16 days agoHandshake completed521 ms
17 days agoHandshake completed524 ms
19 days agoHandshake completed534 ms
19 days agoHandshake completed551 ms
20 days agoHandshake completed531 ms
21 days agoHandshake completed539 ms
22 days agoHandshake completed515 ms

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