Pixly
REMOTE · PIXLY.APP
Every visual AI tool for property listings — staging, enhancement, decluttering, cinematic video.
Available components
Last scanned (3 minutes ago)
Scores higher than 99% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 9050 tokens (~258/item across 35 items; 35 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
- Structured output schemas are declared (74% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 36 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 12 Oct 26 0
- Tool “get_job” rewrote its description, which is the text the model reads security
- Tool coverage: 81% → 74% ▼ functional
- Schema quality: 7534 → 9050 ▼ functional
- New tool “create_listing” functional
- New tool “list_listings” functional
- New tool “plan_photos” functional
- New tool “update_listing” functional
- “before_after_image” added an optional parameter “listingId” cosmetic
- “before_after_reel” added an optional parameter “listingId” cosmetic
- “blur_faces_plates” added an optional parameter “listingId” cosmetic
- “cinematic_motion” added an optional parameter “listingId” cosmetic
- “day_to_night” added an optional parameter “listingId” cosmetic
- “declutter_photo” added an optional parameter “listingId” cosmetic
- “draw_floor_plan” added an optional parameter “listingId” cosmetic
- “edit_staged_photo” added an optional parameter “listingId” cosmetic
- “enhance_photo” added an optional parameter “listingId” cosmetic
- “flythrough_video” added an optional parameter “listingId” cosmetic
- “get_job” added an optional parameter “jobIds” cosmetic
- “list_library” added an optional parameter “listingId” cosmetic
- “makeover_exterior” added an optional parameter “listingId” cosmetic
- “photo_to_video” added an optional parameter “listingId” cosmetic
- “plot_sign” added an optional parameter “listingId” cosmetic
- “remove_furniture” added an optional parameter “listingId” cosmetic
- “render_floor_plan” added an optional parameter “listingId” cosmetic
- “replace_lawn” added an optional parameter “listingId” cosmetic
- “replace_sky” added an optional parameter “listingId” cosmetic
- “reset_season” added an optional parameter “listingId” cosmetic
- “restyle_room” added an optional parameter “listingId” cosmetic
- “straighten_photo” added an optional parameter “listingId” cosmetic
- “touch_up_exterior” added an optional parameter “listingId” cosmetic
- “upscale_hd” added an optional parameter “listingId” cosmetic
- “virtual_staging” added an optional parameter “listingId” cosmetic
- “watermark_photos” added an optional parameter “listingId” cosmetic
- “get_job” made “jobId” optional cosmetic
- 3 Oct 26 0
- Schema quality: 5649 → 6905 ▼ functional
- Tool coverage: 97% → 92% ▼ functional
- New tool “before_after_image” functional
- New tool “blur_faces_plates” functional
- New tool “draw_floor_plan” functional
- New tool “straighten_photo” functional
- New tool “view_pixly_photo” functional
- New tool “watermark_photos” functional
- 2 Oct 26 0
- Tool “before_after_reel” rewrote its description, which is the text the model reads security
- New tool “flythrough_video” functional
- “before_after_reel” reworded the description of “videoIntent” cosmetic
- Tool “before_after_reel” changed its title: Before/After Reel → Before & After Video cosmetic
- 1 Oct 26 −3
- Resource “pixly-result-card” was removed ▼ functional
- The server no longer declares the “resources” capability functional
- Server version: 1.4.0 → 1.5.0 functional
- 30 Sept 26 +3
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- First check of Schema quality: 100 functional
- New resource “pixly-result-card” functional
- Server version: 1.3.1 → 1.4.0 functional
- Server version: 1.3.0 → 1.3.1 functional
- “virtual_staging” reworded the description of “style” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −1
- Tool “virtual_staging” rewrote its description, which is the text the model reads security
- Server version: 1.2.1 → 1.3.0 functional
- New tool “render_floor_plan” functional
- “virtual_staging” reworded the description of “r2Path” cosmetic
- “cinematic_motion” reworded the description of “r2Path” cosmetic
- “day_to_night” reworded the description of “r2Path” cosmetic
- “declutter_photo” reworded the description of “r2Path” cosmetic
- “enhance_photo” reworded the description of “r2Path” cosmetic
- “makeover_exterior” reworded the description of “r2Path” cosmetic
- “photo_to_video” reworded the description of “r2Path” cosmetic
- “plot_sign” reworded the description of “r2Path” cosmetic
- “remove_furniture” reworded the description of “r2Path” cosmetic
- “replace_lawn” reworded the description of “r2Path” cosmetic
- “replace_sky” reworded the description of “r2Path” cosmetic
- “reset_season” reworded the description of “r2Path” cosmetic
- “restyle_room” reworded the description of “r2Path” cosmetic
- “touch_up_exterior” reworded the description of “r2Path” cosmetic
- “upscale_hd” reworded the description of “r2Path” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://pixly.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pixly.app | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a5a6e85c01688ad8135c1d66cb765bc9 |
| SANs: pixly.app, *.pixly.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pixly.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| pixly.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://pixly.app/.well-known/oauth-protected-resource/api/mcp", scope="tools"
Bearer resource_metadata="https://pixly.app/.well-known/oauth-protected-resource/api/mcp", scope="tools"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://pixly.app/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://pixly.app/api/mcp |
| Authorisation server | https://pixly.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pixly.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://pixly.app/api/mcp | HTTPS enforced | 301 | https://pixly.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
virtual_staging Virtual Staging ~567
AI virtual staging: furnish and style an empty (or badly furnished) room photo in a chosen interior design style — also the tool for "redesign this room" or "show this room in another style". HD, watermark-free results. Costs credits from the user's Pixly balance.
| Name | Type | Req | Description |
|---|---|---|---|
| customInstructions | string | – | Optional: ONLY a wish the user stated beyond the style and room, in their words (e.g. "add a reading chair", "no rug"). Leave it out otherwise — Pixly writes the staging prompt itself (keeps walls, w… |
| imageUrl | string | – | Public https URL of the source photo, or a data: URI. Either imageUrl or r2Path is required. |
| listingId | string | – | A property folder (from list_listings or create_listing) to put the result in. Results of a photo that is already in a folder go there by themselves. |
| numImages | integer | – | Ignored — staging always returns one image. Call again for another take. |
| r2Path | string | – | Storage path of a photo already in the user's Pixly library (from list_library, or returned by an upload ticket) — the alternative to imageUrl. |
| roomType | string | – | Room type hint; omit to let vision infer it from the photo |
| stagingQuality | string | – | Ignored — the Pro tier is retired. Every staging costs 1 credit. |
| style | string | yes | Interior style id. One of: modern-minimal, scandinavian, industrial, mid-century-modern, japandi, contemporary, transitional, urban-chic, bauhaus, organic-modern, brutalist, italian-modern, tradition… |
| Name | Type | Req | Description |
|---|---|---|---|
| completedAt | string | – | – |
| createdAt | string | – | – |
| creditsCharged | number|null | – | – |
| error | string | – | – |
| jobId | string | yes | Pass to get_job to poll |
| jobs | array | – | Several jobs at once (get_job with jobIds, or a plan's steps): each one's jobId, status and results |
| note | string | – | – |
| quote | object | – | Present when status is "awaiting_confirmation": nothing ran and nothing was charged yet — the price and settings the user is asked to confirm |
| resultPaths | array | – | Storage path of each result — pass one as r2Path (or beforeR2Path, a photos[] item) to run another tool on this result |
| resultUrls | array | – | Present when completed; valid 7 days |
| status | string | yes | pending | processing | completed | failed — anything not completed/failed is still running |
| type | string | – | – |
No examples provided.
watermark_photos Watermark Photos ~202
Free (no credits): put the agent's or agency's mark on listing photos — text (name, phone) and/or the logo saved on their Pixly account — in a corner or the middle, up to 10 photos per call. Returns every marked photo at once.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | string | – | A property folder (from list_listings or create_listing) to put the result in. Results of a photo that is already in a folder go there by themselves. |
| photos | array | yes | The photos to mark, 1–10. Each item takes imageUrl or r2Path. |
| position | string | – | – |
| size | string | – | – |
| text | string | – | The text, e.g. "Smith Realty · 555-0100". Optional when the account has a saved logo. |
| useLogo | boolean | – | Add the logo saved on the account (Pixly floor plan settings), when there is one. |
| Name | Type | Req | Description |
|---|---|---|---|
| completedAt | string | – | – |
| createdAt | string | – | – |
| creditsCharged | number|null | – | – |
| error | string | – | – |
| jobId | string | yes | Pass to get_job to poll |
| jobs | array | – | Several jobs at once (get_job with jobIds, or a plan's steps): each one's jobId, status and results |
| note | string | – | – |
| quote | object | – | Present when status is "awaiting_confirmation": nothing ran and nothing was charged yet — the price and settings the user is asked to confirm |
| resultPaths | array | – | Storage path of each result — pass one as r2Path (or beforeR2Path, a photos[] item) to run another tool on this result |
| resultUrls | array | – | Present when completed; valid 7 days |
| status | string | yes | pending | processing | completed | failed — anything not completed/failed is still running |
| type | string | – | – |
No examples provided.
How do I install the Pixly MCP server?
Pixly is a hosted endpoint at https://pixly.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pixly.app
claude mcp add --transport http app-pixly-pixly 'https://pixly.app/api/mcp'
What is the Pixly MCP server?
Pixly is an MCP server listed in the public MCP registry as app.pixly/pixly. Every visual AI tool for property listings, staging, enhancement, decluttering, cinematic video. This page covers its hosted endpoint (https://pixly.app/api/mcp).
Is the Pixly MCP server safe to use?
Pixly scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pixly MCP server expose?
Pixly exposes 35 tools: virtual_staging, edit_staged_photo, cinematic_motion, photo_to_video, before_after_reel, and 30 more. Their descriptions and schemas cost roughly 8,909 tokens of context every time the server is loaded.
Does the Pixly MCP server require authentication?
Yes. Pixly asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Pixly MCP server still maintained?
Pixly is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.