Pixeloa MCP server

• Registry nameai.pixeloa/pixeloaverified in the MCP registry

The registry name sits under pixeloa.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools20
• Server calls itselfpixeloa
• Server version2026-10-18
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 354 ms.

• Its tools do every use case we checked: Turn existing product photos into AR previews at real size; Let shoppers check product size in their own space; Share AR previews through a link or QR code.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it3 of 3 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer1371 ms
• Space in an agent's context≈ 2,904 tokensthe definitions of all its tools (20), which an agent carries on every turn
• Tool definitionsA · 95 of 100
• Typed results0 of 20 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 6 of 20

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• getMe

  Who am I, what plan am I on, and what credits do I have. Requires scope: read_usage.

• listItems

  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.

• createItem

  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…

• getItem

  Get one item, including status and next_allowed_actions. Requires scope: read_catalog.

• updateItem

  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…

• deleteItem

  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…

• confirmScale

  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.

• startGeneration

  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…

• publishItem

  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…

• unpublishItem

  Unpublish the item's public AR page (all embeds go quiet). CHANGES PUBLIC STATE. Requires scope: publish_items.

• getItemLinks

  Public AR URL, embed URL, embed snippets and QR (if generated). Requires scope: read_catalog.

• generateItemQr

  Generate (or regenerate) the item's QR code SVG. Requires scope: create_qr.

• listCatalogs

  List the account's catalogs. Requires scope: read_catalog.

• deleteCatalog

  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…

• addCatalogItem

  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…

• removeCatalogItem

  Remove an item from a catalog. Requires scope: write_catalog.

• listGenerationOptions

  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…

• listCreditLedger

  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.

• listAgents

  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…

• listWebhookEndpoints

  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…