Car Image API catalog
REMOTE · CARIMAGE.DEV
Free vehicle lookups, image options, pricing and stored car image previews. No account needed.
Available components
Last scanned (2 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1662 tokens (~207/item across 8 items; 7 tools + 1 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (86% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
- Supports UI / widget rendering.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.
- 5 Nov 26 0
- Tool “search_vehicles” rewrote its description, which is the text the model reads security
- Schema quality: 235 → 207 ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- New resource “car-image-card” functional
- 4 Nov 26 +1
- Tool “search_vehicles” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 74
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 5 Nov 2026 · Probed https://carimage.dev/api/mcp/catalog
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=carimage.dev | CN=YR2,O=Let's Encrypt,C=US | 5 Nov 2026 | 3 Feb 2027 | RSA 2048 | SHA256-RSA | 6e8a161817755798a2370c3c3f319b8b634 |
| SANs: carimage.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of carimage.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| carimage.dev. | 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=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://carimage.dev/api/mcp/catalog | Verified | 200 | |
| http (plaintext) | http://carimage.dev/api/mcp/catalog | HTTPS enforced | 308 | https://carimage.dev/api/mcp/catalog |
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 →
describe_api Describe the REST API ~115
Free. 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 (`npx @meterapp/car-image`) equivalents. Optional endpoint filter.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | – | Filter by path fragment or keyword, e.g. "images/car", "image-urls", "vin", "3d". Omit for the full compact reference. |
No output schema declared.
No examples provided.
get_pricing Get current pricing ~150
Free, 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, make logos and upgrades; credits are not sold), limits per tier and features, the one-time Image Packs (add_ons), the free tier and live 3D model cost. There is no overage. Every plan and pack has a checkout_url that works before signup (sign-in, then Stripe Checkout; nothing is charged until the human pays): hand it to the human with the price. Use before explaining costs or choosing a plan.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| request_id | string | yes | – |
No examples provided.
list_image_options List image options ~66
Free. 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 validate or explain what can be requested.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
preview_car_image Preview a stored car image ~296
Free, 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. Never renders: another view, paint or size, or a vehicle with nothing stored, is an image from the account server (create_car_image_urls, 1 credit). Pass the vehicle id from resolve_vehicle or search_vehicles, plus the view and color the human asked for. Say it is a preview, and name its view and color when they differ from the request.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | The paint the human asked for, if any (a preset, a CSS color name or a hex). Preferred when a picture in that paint is stored; never recolored here. |
| vehicle | string | yes | Stable vehicle id such as veh_395yw8tn73ff8, as resolve_vehicle (params.vehicle_id), search_vehicles and decode_vin return it. The preferred way to name a vehicle: it cannot be misspelled. It names t… |
| view | string | – | The view the human asked for, if any. A stored picture in that view is preferred; otherwise the vehicle page's main picture is returned and the result says which view it is. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| request_id | string | yes | – |
| summary | string | – | – |
No examples provided.
resolve_vehicle Resolve free text to image parameters ~207
Free. 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, view, color), plus alternative candidates and a confidence of high, medium or low. A make and model are read by the rules the image tools read them with, so this names the vehicle they would render. Pass params.vehicle_id as vehicle to get_car_image, create_car_image_urls or create_3d_model. Ask the human to choose when confidence is low or several candidates fit, and tell them when params.year is not the year they asked for (extracted.year).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What the human asked for, in words: year, make and model, plus the view and color when they named them, e.g. "red 2024 porsche 911 side view". |
| Name | Type | Req | Description |
|---|---|---|---|
| cli | string | yes | – |
| data | object | yes | – |
No examples provided.
search_help Search product help ~137
Free. 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 information or full emails; queries are recorded privately to improve articles. Cite sources, do not invent missing answers or contract exceptions, and escalate unanswered parts to support.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | One product question. Do not include personal information, credentials or full customer emails; queries are recorded privately to improve help articles. |
| report_gap | boolean | – | Set true when prior results did not answer this question, to flag missing context for staff. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| request_id | string | yes | – |
No examples provided.
search_vehicles Search the vehicle catalog ~224
Free. Browse the open vehicle catalog (1,608 makes, 42,333 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 id per year (ids, and id when the query names one year) to pass as `vehicle` to the image and 3D tools. Use it to list a make's models, to see which years exist or to let the human choose between similar models; when you already know which car is wanted, resolve_vehicle is the one call that names it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (1-25). |
| query | string | yes | Free text: make and/or model, optional year, typos tolerated, e.g. "porshe 911" or "2019 f150". Fewer words find more: every word must be in the name of one catalog vehicle. |
| year | integer | – | Restrict results to one model year. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
How do I install the Car Image API catalog MCP server?
Car Image API catalog is a hosted endpoint at https://carimage.dev/api/mcp/catalog, 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 · carimage.dev
claude mcp add --transport http dev-carimage-catalog 'https://carimage.dev/api/mcp/catalog'
What is the Car Image API catalog MCP server?
Car Image API catalog is an MCP server listed in the public MCP registry as dev.carimage/catalog. Free vehicle lookups, image options, pricing and stored car image previews. No account needed. This page covers its hosted endpoint (https://carimage.dev/api/mcp/catalog).
Is the Car Image API catalog MCP server safe to use?
Car Image API catalog scores 75 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 Image API catalog MCP server expose?
Car Image API catalog exposes 7 tools: resolve_vehicle, search_vehicles, preview_car_image, list_image_options, get_pricing, and 2 more. Their descriptions and schemas cost roughly 1,195 tokens of context every time the server is loaded.
Does the Car Image API catalog MCP server require authentication?
No. We connected to Car Image API catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Car Image API catalog MCP server still maintained?
Car Image API catalog is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.