Pixeloa
REMOTE · PIXELOA.AI
Turn product photos into true-scale 3D models and AR pages, then publish, embed and catalog them.
Available components
Last scanned (17 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 23 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (deleteItem). See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2014 tokens (~91/item across 22 items; 20 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Oct 26 64
First indexed and scored.
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 23 Oct 2026 · Probed https://pixeloa.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pixeloa.ai | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | aaeb04510fdb1a2d0ebc6810966ace2a |
| SANs: pixeloa.ai, staging.pixeloa.ai, *.staging.pixeloa.ai | ||||||
| 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 pixeloa.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| pixeloa.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| permissions-policy | camera=(self), microphone=(), geolocation=(), payment=(self), accelerometer=(self), gyroscope=(self), magnetometer=(self), xr-spatial-tracking=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pixeloa.ai/mcp | Verified | 200 | |
| http (plaintext) | http://pixeloa.ai/mcp | HTTPS enforced | 301 | https://pixeloa.ai/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 →
addCatalogItem ~129
Add an item to a catalog (appends unless position is given). Both the catalog and the item must belong to the key's account (404 otherwise). 409 conflict when the item is not ready (details.status says where it is), is not eligible for catalogs, is unlisted (link only), or is already in the catalog. Requires scope: write_catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
| item_id | string | yes | – |
| position | integer | – | – |
No output schema declared.
No examples provided.
confirmScale ~101
Confirm the item's real-world dimensions (cm). Allowed once analysis has finished (status 'awaiting_confirmation', or 'failed' with a completed analysis) and before generation. Moves the item to 'confirmed'. Requires scope: confirm_scale.
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions_cm | object | yes | – |
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
| notes | string | – | – |
No output schema declared.
No examples provided.
createItem ~170
Create an item from 1–4 image URLs and start analysis. Images are fetched server-side (https only, size- and type-checked against the active provider's limits). The first image is the primary/front view. Image URLs must be publicly reachable and must not point at pixeloa.ai itself (host them on your own site, a CDN, or a public bucket). The item enters 'analyzing'; poll GET /v1/items/{id} until next_allowed_actions contains confirm_scale. Requires scope: upload_images.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
| image_urls | array | yes | – |
| owner_dims_cm | object | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
deleteCatalog ~113
Delete a catalog (unpublishes its public page first). Permanent. A published catalog is unpublished first so its public page, QR and embeds go quiet; item memberships are removed (the items themselves are untouched); if it was the primary catalog that pointer clears. The platform demo catalog cannot be deleted (409 conflict). CHANGES PUBLIC STATE. Requires scope: write_catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
No output schema declared.
No examples provided.
deleteItem ~99
Delete an item (unpublishes first; removes images and models). Permanent. A published item is unpublished first so its AR page and embeds go quiet, then its images, models and QR are removed. Requires the same scope as creating items. CHANGES PUBLIC STATE. Requires scope: upload_images.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
No output schema declared.
No examples provided.
generateItemQr ~58
Generate (or regenerate) the item's QR code SVG. Requires scope: create_qr.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
No output schema declared.
No examples provided.
getItem ~33
Get one item, including status and next_allowed_actions. Requires scope: read_catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
No output schema declared.
No examples provided.
getItemLinks ~38
Public AR URL, embed URL, embed snippets and QR (if generated). Requires scope: read_catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
No output schema declared.
No examples provided.
getMe ~31
Who am I, what plan am I on, and what credits do I have. Requires scope: read_usage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
listAgents ~81
List the account's agent identities. An agent is an identity OWNED by the account (kind agent or service). Keys attach to an agent; the agent gets actor identity, an optional daily credit cap and its own audit trail, but every call still runs as the owner. Agents are created and suspended by a human in the dashboard. Requires scope: read_usage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
listCatalogs ~21
List the account's catalogs. Requires scope: read_catalog.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
listCreditLedger ~82
The account's credit ledger (newest first, cursor-paginated). Every debit and credit: generation charges, refunds, plan allocations, top-ups. Query: limit (1–100), cursor (created_at from next_cursor). Requires scope: read_usage.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from a previous page |
| limit | integer | – | – |
No output schema declared.
No examples provided.
listGenerationOptions ~94
Generation options available to this account and their current credit cost. Read before spending. Each option lists credit_cost (what POST /v1/items/{id}/generate will debit for that provider), release_stage, image limits and output formats; is_default marks the provider used when the item has none pinned. GET /v1/items/{id} additionally returns generation.estimated_credit_cost for that item. Requires scope: read_usage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
listItems ~89
List the account's items (newest first, cursor-paginated). Query: limit (1–100, default 25), cursor (created_at ISO string from next_cursor), status. Requires scope: read_catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from a previous page (created_at ISO string) |
| limit | integer | – | – |
| status | string | – | Filter by item status |
No output schema declared.
No examples provided.
listWebhookEndpoints ~112
List the account's webhook endpoints and the event types. Endpoints are created by a human in the dashboard (Account → API keys → Webhooks); a key can list them but never add or redirect one. Deliveries are signed with Pixeloa-Signature (t=<unix>,v1=<hex HMAC-SHA256(secret, t + "." + body)>), retried with backoff for up to 12h, and auto-disabled after 20 consecutive failures. Requires scope: read_usage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publishItem ~144
Publish the item's public AR page. Makes the item public (this is the owner's publish decision; items created via the API start private) subject to the plan's published-item limit (403 plan_limit_reached), verifies eligibility (409 conflict with details.state / details.blockers when the model, scale or category policy blocks it), mints the public slug on first publish and returns the item with public.ar_url and public.embed_url set. Check item.publishable before calling. CHANGES PUBLIC STATE. Requires scope: publish_items.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
No output schema declared.
No examples provided.
removeCatalogItem ~62
Remove an item from a catalog. Requires scope: write_catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
| itemId | string | yes | UUID |
No output schema declared.
No examples provided.
startGeneration ~171
Start 3D generation (spends the account's credits). Requires status 'confirmed' with confirmed dimensions (a 'failed' generation may be attempted again on the same item; it was refunded and has no result). A 'ready' item is never regenerated in place; for another result create a new item from the images. Asynchronous: poll GET /v1/items/{id} until model.available is true. Fails with 402 insufficient_credits when the balance is too low, 409 conflict when the state does not allow it. SPENDS CREDITS: confirm with the account owner unless they delegated this. Requires scope: start_generation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
No output schema declared.
No examples provided.
unpublishItem ~64
Unpublish the item's public AR page (all embeds go quiet). CHANGES PUBLIC STATE. Requires scope: publish_items.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
No output schema declared.
No examples provided.
updateItem ~163
Update the item's public-page settings (product CTA link). Sets the 'view product' button shown on the public AR page and embeds. product_url must be a public https URL on your own site, and it may not point at pixeloa.ai itself or a private network (422 validation_error otherwise). Pass null to clear it (the label clears with it). product_cta_label (max 60 chars) overrides the default button text. Clicks are counted in the owner's analytics. Requires scope: publish_items.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID |
| idempotency_key | string | – | Optional Idempotency-Key: repeat-safe retries return the original result. |
| product_cta_label | string|null | – | – |
| product_url | string|null | – | – |
No output schema declared.
No examples provided.
How do I install the Pixeloa MCP server?
Pixeloa is a hosted endpoint at https://pixeloa.ai/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 · pixeloa.ai
claude mcp add --transport http ai-pixeloa-pixeloa 'https://pixeloa.ai/mcp'
What is the Pixeloa MCP server?
Pixeloa is an MCP server listed in the public MCP registry as ai.pixeloa/pixeloa. Turn product photos into true-scale 3D models and AR pages, then publish, embed and catalog them. This page covers its hosted endpoint (https://pixeloa.ai/mcp).
Is the Pixeloa MCP server safe to use?
Pixeloa scores 66 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 Pixeloa MCP server expose?
Pixeloa exposes 20 tools: getMe, listItems, createItem, getItem, updateItem, and 15 more. Their descriptions and schemas cost roughly 1,855 tokens of context every time the server is loaded.
Does the Pixeloa MCP server require authentication?
No. We connected to Pixeloa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pixeloa MCP server still maintained?
Pixeloa is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.