Car Background AI
REMOTE · API.CARBACKGROUND.AI
Replace car photo backgrounds, hide license plates and add dealer logos for vehicle listings.
Available components
Last scanned (19 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 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 Security89
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2961 tokens (~227/item across 13 items; 13 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 0
- Server version: 1.0.1 → 1.0.2 functional
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Tool “change_plan” rewrote its description, which is the text the model reads security
- Tool “create_background” rewrote its description, which is the text the model reads security
- Tool “create_checkout” rewrote its description, which is the text the model reads security
- Tool “delete_background” rewrote its description, which is the text the model reads security
- Tool “delete_logo” rewrote its description, which is the text the model reads security
- Tool “generate_background” rewrote its description, which is the text the model reads security
- Tool “get_credits” rewrote its description, which is the text the model reads security
- Tool “hide_license_plates” rewrote its description, which is the text the model reads security
- Tool “list_backgrounds” rewrote its description, which is the text the model reads security
- Tool “list_logos” rewrote its description, which is the text the model reads security
- Tool “list_plans” rewrote its description, which is the text the model reads security
- Tool “refine_background” rewrote its description, which is the text the model reads security
- Tool “upload_logo” rewrote its description, which is the text the model reads security
- Schema quality: 134 → 227 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- 16 Nov 26 +40
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 97 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: good functional
- 15 Nov 26 36
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 21 Nov 2026 · Probed https://api.carbackground.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=carbackground.ai | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a942268c3743886513c0c850724e012f |
| SANs: carbackground.ai, api.carbackground.ai, *.api.carbackground.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 api.carbackground.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| carbackground.ai. | No DS | 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 error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://api.carbackground.ai/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://api.carbackground.ai/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://api.carbackground.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.carbackground.ai/mcp |
| Authorisation server | https://aszncnzkiaocslspitwp.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.carbackground.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.carbackground.ai/mcp | HTTPS enforced | 301 | https://api.carbackground.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 →
change_plan Change subscription plan ~190
Change the plan of a workspace that already has a subscription, to a `price_id` from list_plans. Always call it first with `confirm: false`, which for an upgrade returns a preview of the prorated charge and charges nothing, and get the user's agreement to that amount. With `confirm: true` an upgrade charges the payment method on file immediately and adds the photos at once, while a smaller plan charges nothing now and is booked to start at the next renewal. For a workspace without a subscription it returns `no_active_subscription`; use create_checkout there instead. It cannot cancel a subscription; the user does that in the app. Needs an OAuth sign-in: with an API key it returns an error pointing to the app.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | false previews an upgrade; true applies the change. |
| price_id | string | yes | A `price_id` from list_plans. |
No output schema declared.
No examples provided.
create_background Create custom background ~250
Create a new reusable background scene for the workspace, such as the dealer's own showroom, a branded studio or a specific outdoor setting. Use it when none of the scenes in list_backgrounds fits; it does not edit a car photo (that is generate_background), and to adjust a custom background that already exists use refine_background instead of creating another. Give a `description`, `reference_image_urls`, or both; add `base_background_id` to start from a built-in scene and describe only what to change. Renders a preview with a demo car and returns it as an image plus the new background's `id`, ready to pass to generate_background. Costs one credit; a rejected or failed request is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| base_background_id | string | – | A built-in background `id` to start from; the description then says what to change. |
| description | string | – | The scene: walls, floor, lighting, setting. E.g. 'A bright showroom with light oak flooring and floor-to-ceiling windows'. |
| name | string | – | Display name. Suggested if omitted. |
| reference_image_urls | array | – | Up to three public image URLs of the place or style to recreate. |
No output schema declared.
No examples provided.
create_checkout Create checkout link ~218
Start a first subscription for a workspace that has none, e.g. when get_credits shows too few credits. Take `price_id` from list_plans; `currency` picks one of that plan's fixed local prices and `buyer` decides VAT handling for EU and UK buyers. This call charges nothing: it returns a Stripe checkout `url` for the user to open and pay, and the plan's photos are added once the payment completes. For a workspace that already subscribes it returns `already_subscribed`; use change_plan there instead. Needs an OAuth sign-in: with an API key it returns an error pointing to the app.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | – | EU and UK buyers: `business` collects a VAT number (reverse charge), `personal` adds VAT. |
| currency | string | – | A key of the plan's `currency_options` (e.g. `eur`) to pay the fixed local price. Omit for USD. |
| price_id | string | yes | A `price_id` from list_plans. |
No output schema declared.
No examples provided.
delete_background Delete custom background ~142
Permanently delete one of the workspace's custom backgrounds, e.g. a scene the user no longer wants in their list. It cannot be undone through this server; a deleted scene has to be made again with create_background. Photos already generated with it are not affected, and no credits are charged or refunded. Only custom backgrounds (`custom: true` in list_backgrounds) can be deleted, never built-in ones. To change a scene instead of removing it, use refine_background. Returns the `id` with `deleted: true`, or `not_found` for an unknown id.
| Name | Type | Req | Description |
|---|---|---|---|
| background_id | string | yes | The `id` of a custom background. |
No output schema declared.
No examples provided.
delete_logo Delete logo ~183
Permanently delete one of the workspace's stored logos, e.g. an outdated logo or to free one of the seven slots before upload_logo. It cannot be undone through this server; the logo has to be uploaded again to restore it. Photos already generated keep the logo they were made with, and later generate_background calls can no longer use this `id`. Get the `id` from list_logos, and pass the same `type` the logo was listed under (`logo` by default, or `plate`). Free. Returns the `id` with `deleted: true`, or `not_found` when the id is unknown for that type.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A logo `id` from list_logos. |
| type | string | – | `logo` (default): logos drawn on finished photos. `plate`: designs put on the license plate. |
No output schema declared.
No examples provided.
generate_background Replace photo background ~409
Replace the background of one car photo with a chosen scene: the main tool for turning a phone photo into a listing photo. The car is kept as photographed and gets shadows, lighting and reflections that match the scene. Works on exterior, interior and detail shots. Pick `background_id` with list_backgrounds first and use the same one for every photo of a car. In the same call it can hide the plate (`hide_license_plate`, with `license_plate_style` and, for `logo`, a `license_plate_logo` from list_logos), draw a dealer `logo`, reframe to an `aspect_ratio`, centre the car or show it washed. To hide the plate without changing the background use hide_license_plates; to make a new scene use create_background. One photo per call; the source photo is not modified. Costs one credit, and a failed generation is not charged. Can take up to a minute. Returns a signed `image_url` of the high-resolution result, valid for 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | Output aspect ratio. Omit to keep the photo's own. |
| background_id | string | yes | A background `id` from list_backgrounds. |
| center_car | boolean | – | Experimental: centre, enlarge and level the car like a listing photo. |
| clean_car | boolean | – | Experimental: show the car freshly washed. |
| hide_license_plate | boolean | – | Hide a legible license plate (exterior photos). |
| image_url | string | yes | Public HTTPS URL of the car photo (JPEG, PNG or WebP). |
| license_plate_logo | object | – | Required with license_plate_style `logo`. |
| license_plate_style | string | – | With hide_license_plate: `plain` (default) replaces it with a blank plate, `blur` blurs it, `logo` shows the dealer's plate logo (set license_plate_logo). |
| logo | object | – | Draw one of the workspace's logos on the result. |
No output schema declared.
No examples provided.
get_credits Get credit balance ~111
Read the workspace's current credit balance, returned as `balance`. One credit is one photo from generate_background or one preview from create_background or refine_background; hide_license_plates uses none. Call it before a batch to check there are enough credits, or after an insufficient-credits error. Read-only and free; takes no parameters. It does not show plans or prices: when the balance is too low, use list_plans, then create_checkout (no subscription yet) or change_plan (existing subscription).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hide_license_plates Hide license plates ~211
Hide the license plates in a car photo without changing anything else, for privacy before publishing a listing. Use this when the background should stay as it is; when the background is being replaced as well, set `hide_license_plate` on generate_background instead of calling both. `style` chooses a blur (default) or a solid `block`, and `block_color` sets the block's colour. Uses no credits: it is included with an active subscription, up to a fair-use monthly limit, and returns `subscription_required` for a workspace without one. The source photo is not modified; the result is returned as an image, with the areas that were hidden listed as `plates`.
| Name | Type | Req | Description |
|---|---|---|---|
| block_color | string | – | Hex colour of the block, e.g. #FFFFFF. Default black. |
| image_url | string | yes | Public HTTPS URL of the car photo (JPEG, PNG or WebP). |
| style | string | – | Blur the plate (default) or cover it with a block. |
No output schema declared.
No examples provided.
list_backgrounds List backgrounds ~120
List the background scenes available for car photos: built-in studios, showrooms and outdoor settings, plus the workspace's own custom backgrounds (`custom: true`, made with create_background or in the app). Call this first to pick a scene: each entry has a preview image, an example with a car, and the `id` that generate_background takes as `background_id` (custom ones also go to refine_background and delete_background). Read-only and free; takes no parameters and returns every scene in one response. For logos use list_logos instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_logos List logos ~161
List the logos stored for the workspace, to get the `id` that other tools need. `type` selects which set is returned: `logo` (default) for dealer logos drawn on finished photos, passed as `logo.id` to generate_background, or `plate` for designs shown on the license plate, passed as `license_plate_logo.id`. Each entry has `id`, `type`, `image_url` and `created_at`. Also call it before delete_logo, or before upload_logo to see whether the logo is already stored. Read-only and free. For background scenes use list_backgrounds instead.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | `logo` (default): logos drawn on finished photos. `plate`: designs put on the license plate. |
No output schema declared.
No examples provided.
list_plans List subscription plans ~129
List the subscription plans on offer, to quote prices or to get the `price_id` that create_checkout (workspace without a subscription) and change_plan (existing subscription) take. Each plan has its monthly photo allowance (`credits`), billing interval and price: `unit_amount` is in the smallest unit of `currency` (USD), and `currency_options` lists the fixed local prices whose keys create_checkout accepts as `currency`. Read-only and free; takes no parameters and is the same for every caller. It does not show the workspace's own balance: use get_credits for that.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
refine_background Refine custom background ~183
Adjust a custom background that already exists and render a new preview, e.g. after create_background when the preview is close but not right. `description` is only the change to make ('make the floor darker and the lighting warmer'); everything else in the scene is kept, and `reference_image_urls` can show the look to move towards. The background is updated in place under the same `id` and name, so later generate_background calls use the refined scene; photos already generated are not changed. Works on custom backgrounds only, not built-in ones; to start a different scene use create_background. Returns the new preview image. Costs one credit; a rejected or failed request is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| background_id | string | yes | The `id` of a custom background. |
| description | string | yes | What to change. |
| reference_image_urls | array | – | – |
No output schema declared.
No examples provided.
upload_logo Upload logo ~229
Store a logo for the workspace so it can be put on photos later. It does not change any photo by itself: pass the returned `id` to generate_background as `logo.id`, or as `license_plate_logo.id` for a `plate` logo. The file is fetched from `image_url` once and a copy is kept (PNG, WebP or JPEG up to 5 MB; a transparent background works best). `type` is `logo` (default) for dealer logos or `plate` for license plate designs, where `background` sets the plate colour behind a transparent logo. Up to seven per type: when full, remove one with delete_logo first. Check list_logos before uploading to avoid duplicates. Free. Returns the stored logo with its `id`.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | – | Plate logos only: hex colour behind a transparent logo. Default white. |
| image_url | string | yes | Public HTTPS URL of the logo. |
| type | string | – | `logo` (default): logos drawn on finished photos. `plate`: designs put on the license plate. |
No output schema declared.
No examples provided.
How do I install the Car Background AI MCP server?
Car Background AI is a hosted endpoint at https://api.carbackground.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 · api.carbackground.ai
claude mcp add --transport http ai-carbackground-carbackground 'https://api.carbackground.ai/mcp'
What is the Car Background AI MCP server?
Car Background AI is an MCP server listed in the public MCP registry as ai.carbackground/carbackground. Replace car photo backgrounds, hide license plates and add dealer logos for vehicle listings. This page covers its hosted endpoint (https://api.carbackground.ai/mcp).
Is the Car Background AI MCP server safe to use?
Car Background AI scores 78 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 Car Background AI MCP server expose?
Car Background AI exposes 13 tools: list_backgrounds, create_background, refine_background, delete_background, generate_background, and 8 more. Their descriptions and schemas cost roughly 2,536 tokens of context every time the server is loaded.
Does the Car Background AI MCP server require authentication?
Yes. Car Background AI 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 Car Background AI MCP server still maintained?
Car Background AI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Car Background AI MCP server?
VerifyMCP ran 13 checks on Car Background AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.