carsensor Price Range MCP Server for AI Agents

carsensor Price Range MCP Server for AI Agents

If you're building an AI agent, chatbot, or app that needs to answer "is this used car's asking price fair?" — not a guess, but a number grounded in real market data — this MCP server gives you exactly that in a single tool call. resolvePriceRange(carModel, year) returns a market-price range (min / max / median) computed live from carsensor.net's own official price-by-model-year market statistics — the same data carsensor itself publishes on its 相場(market price) pages, turned into a structured, ready-to-use number instead of a page you'd have to read and interpret yourself.

What you get:

underlying data source, no HTML to parse yourself

• One tool, resolvePriceRange, taking just a car model name and a year — no API keys to manage for the

based on) and confidence (normal / low — honestly downgraded, not hidden, when the year can't be fully verified against carsensor's own data; see "Known limitations")

• priceRangeYen: { min, max, median } plus sampleSize (how many real carsensor listings the estimate is

Desktop, Claude Code, your own agent) directly to a stable HTTPS endpoint, or call it as a plain Streamable HTTP MCP server from your own app's code

• Always-on hosting via Apify Standby mode — no server to run yourself. Connect any MCP client (Claude

{
  "ok": true,
  "carModel": "プリウス",
  "year": 2018,
  "priceRangeYen": { "min": 750000, "max": 4772500, "median": 1573112 },
  "sampleSize": 412,
  "confidence": "normal",
  "disclaimer": "carsensor.net上の公開情報(相場ページの価格×年式集計)を基にした参考値です。個体差・装備差・実際の商談結果は反映されません。"
}

Pay-per-event pricing — see "Pricing" below. Full input/output details, setup, and technical design are further down this page.

⚠️ Disclaimer (please read)

You are responsible for how you retrieve and use this data.

• This Actor automatically retrieves information that is publicly available on carsensor.net.

could stop this Actor from working or change its output unexpectedly.**

• **The site owner's Terms of Use, robots.txt, or access blocking could change without notice, which

aggregate data, not a guarantee of any individual vehicle's true value. It does not account for condition, trim/grade differences, or mileage (see "Known limitations"). Always verify a specific vehicle's price on carsensor.net itself before making any purchase or sale decision based on this data.**

• **priceRangeYen is a statistical estimate derived from carsensor's own published price×model-year

Who is this for?

instead of the model's own (often outdated or hallucinated) knowledge of used-car pricing

• AI agents and chatbots that need to ground a "what is this actually worth?" answer in real market data

ready-made price-range lookup instead of scraping and maintaining their own carsensor.net integration

• App/tool developers building car-shopping, valuation, or trade-in estimation features who want a

call-on-demand counterpart to our batch-oriented carsensor-resale-value-scout Actor (which scores whole lists of listings against the same underlying market data)

• Anyone who wants this as a plain MCP tool call rather than a batch scrape — this Actor is the single-tool,

What can't it do (please read before integrating)

carsensor's own model-year aggregate, not a mileage-adjusted estimate. A future version may add this.

• Mileage is not a supported input yet. Only car model and year are used — the price range reflects

"Known limitations" for why, and how caching mitigates this after the first call.

• Model-name resolution can occasionally fail or be slow on first use for an unfamiliar model — see

• This is a statistical estimate, not an appraisal. See the Disclaimer above.

Input / Output

Input (MCP tool call arguments):

Shortened. The full README is on GitHub.