Skip to content

Car Background AI MCP server

ai.carbackground/carbackgroundcarbackground.aistreamable-httpv1.0.2Scanned

Replace car photo backgrounds, hide license plates and add dealer logos for vehicle listings.

13 tools: 4 can delete or cancel things, 5 change things and 4 only read.

Tools: 4 delete, 0 irreversible, 5 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 0
  • No findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

4 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Car Background AI MCP server can do

The Car Background AI MCP server is published by carbackground.ai, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (4 tools: refine_background, delete_background, delete_logo and change_plan) and create or change data (5 tools: create_background, generate_background, hide_license_plates, upload_logo and 1 more). 4 tools only read.

5 tools bring in text other people can write (create_background, refine_background, generate_background and 2 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Nov 19, 2026, version 1.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Deletes or cancels 4Claude Code: deny
  • change_planChange the plan of a workspace that already has a subscription, to a `price_id` from list_plans.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Change subscription plan
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • delete_backgroundPermanently delete one of the workspace's custom backgrounds, e.g.No findings

    Why it is in this group

    • The name "delete_background" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Delete custom background
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • refine_backgroundAdjust a custom background that already exists and render a new preview, e.g.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Refine custom background
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
Changes things 5Claude Code: ask
  • create_backgroundCreate a new reusable background scene for the workspace, such as the dealer's own showroom, a branded studio or a specific outdoor setting.Reads text others writeNo findings

    Why it is in this group

    • The name "create_background" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create custom background
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • create_checkoutStart a first subscription for a workspace that has none, e.g.No findings

    Why it is in this group

    • The name "create_checkout" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create checkout link
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • generate_backgroundReplace the background of one car photo with a chosen scene: the main tool for turning a phone photo into a listing photo.Reads text others writeNo findings

    Why it is in this group

    • The name "generate_background" says "generate": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Replace photo background
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • hide_license_platesHide the license plates in a car photo without changing anything else, for privacy before publishing a listing.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • title: Hide license plates
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • get_creditsRead the workspace's current credit balance, returned as `balance`.No findings

    Why it is in this group

    • The name "get_credits" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Get credit balance
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_backgroundsList 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…No findings

    Why it is in this group

    • The name "list_backgrounds" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List backgrounds
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_logosList the logos stored for the workspace, to get the `id` that other tools need.No findings

    Why it is in this group

    • The name "list_logos" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List logos
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_plansList 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.No findings

    Why it is in this group

    • The name "list_plans" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List subscription plans
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://api.carbackground.ai/.well-known/oauth-protected-resource/mcp
RFC 9728 protected resource metadata
https://api.carbackground.ai/.well-known/oauth-protected-resource/mcp
Authorization servers
https://aszncnzkiaocslspitwp.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http carbackground https://api.carbackground.ai/mcp
claude mcp add --transport http carbackground https://api.carbackground.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__carbackground__list_backgrounds",
      "mcp__carbackground__get_credits",
      "mcp__carbackground__list_logos",
      "mcp__carbackground__list_plans"
    ],
    "ask": [
      "mcp__carbackground__create_background",
      "mcp__carbackground__generate_background",
      "mcp__carbackground__hide_license_plates",
      "mcp__carbackground__upload_logo",
      "mcp__carbackground__create_checkout"
    ],
    "deny": [
      "mcp__carbackground__refine_background",
      "mcp__carbackground__delete_background",
      "mcp__carbackground__delete_logo",
      "mcp__carbackground__change_plan"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as carbackground. Review it before you use it.

Capability tags behind 5 rules
  • mcp__carbackground__create_background untrusted-input
  • mcp__carbackground__refine_background untrusted-input
  • mcp__carbackground__generate_background untrusted-input
  • mcp__carbackground__hide_license_plates untrusted-input
  • mcp__carbackground__upload_logo untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.carbackground/carbackground/verify?hash=debf0796e8d7dee7cbfcc17b2259e5e652338d7e9cc65b61f96d6befc4f3ed47" | jq -e '.changed == false'

Pinned hash debf0796e8d7, from Nov 19, 2026, 06:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.carbackground/carbackground/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.carbackground/carbackground
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.carbackground/carbackground.svg)](https://radar.anlyon.com/servers/ai.carbackground/carbackground)

Source: MCP Registry · repository. Synced Nov 19, 2026, 06:17 UTC.

Car Background AI MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Car Background AI MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Car Background AI MCP server delete data?

Yes. 4 tools can delete, cancel or revoke something: refine_background, delete_background, delete_logo and change_plan.

Can the Car Background AI MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Car Background AI MCP server have?

13 tools: 4 destructive, 5 write, 4 read. refine_background, delete_background, delete_logo, change_plan, create_background, generate_background, hide_license_plates, upload_logo and 5 more.

Does the Car Background AI MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Car Background AI MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Car Background AI MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.