
Car Image API MCP server
Which MCP servers are Car Image API's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-11-03
- Registry namedev.carimage/catalogverified in the MCP registry
The registry name sits under carimage.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-11-03
- Tools7
- Server calls itselfcar-image-catalog
- Server version1.38.1
- Protocol version2025-06-18
On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 110 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 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: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer160 ms
- Space in an agent's context≈ 1,681 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results6 of 7 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · Put a consistent vehicle photo on each listing
- not sure · Preview wrap colours on a customer's own vehicle model
- not sure · Fill dealer stock records before lot photos arrive
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
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 →
resolve_vehicleFree. The first call for any picture of a car, including one you chose yourself: turn a request such as "red 2018 Mazda MX-5 Miata side view" into the catalog vehicle and exact get_car_image parameters (vehicle_id, make, model, year…
search_vehiclesFree. Browse the open vehicle catalog (1,608 makes, 42,318 models, 1990-2027) by make and/or model with typo tolerance. Returns canonical make/model names, the years each model exists and match kind; a model hit carries a stable vehicle…
preview_car_imageFree, no account needed. The picture of a catalog vehicle that its public page on carimage.dev already shows, when one is stored: a 600 px WebP with ready-to-paste markdown, the view and paint it is in, and every stored view and paint…
list_image_optionsFree. List the supported camera views (with yaw angles and aliases), the fifteen preset colors with hex swatches (any other paint is a hex color), size presets, output formats, current pricing and catalog coverage. Use it when you need to…
get_pricingFree, no account needed. The pricing document: every plan's monthly and yearly price, its vehicle images a month (a vehicle image is one vehicle in one color from one angle, delivered as often as needed), included credits (for 3D models…
search_helpFree. Find source-linked answers about pricing, terms, licensing, manufacturer rights, policies, Enterprise, delivery and account support. Suitable for drafting replies to customer questions. Submit one question at a time without personal…
describe_apiFree. Return a compact reference of the Car Image REST API (methods, paths, parameters, credit costs, response headers, error codes, agent notes) for writing code that calls the API directly, with SDK (`@meterapp/car-image-sdk`) and CLI…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"catalog": {
"type": "http",
"url": "https://carimage.dev/api/mcp/catalog"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http carimage https://carimage.dev/api/mcp/catalogclaude.ai, ChatGPT and other clients: add https://carimage.dev/api/mcp/catalog as a custom connector in the settings.
- dev.carimage/car-imageanswers, requires sign-inverified in the MCP registry
OpenAPI spec
59 paths, read 2026-11-03. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.