Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Databutler Vehicles is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
UK MOT failure data and official UK, French, Japanese and EU vehicle recalls.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http databutler-vehicles-mcp https://databutler.dev/api/mcp/vehicles
# 2 — ask your agent for something these tools do
# uk_mot_reliability, uk_mot_vehicle_search, uk_recalls_for_model and 6 more
Databutler Vehicles costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http databutler-vehicles-mcp https://databutler.dev/api/mcp/vehiclesReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Real UK MOT failure data for a used car: per-category failure rates (overall and interpolated at a given mileage) and the riskiest components with typical failure mileages, for one model generation. Live proxy to whatbreaks.uk (same operator; aggregated from DfT anonymised MOT results). Use when a user is buying, comparing or maintaining a car sold in the UK. If several generations match, the resu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| make | string | yes | e.g. Volkswagen |
| model | string | yes | e.g. Golf — generation resolved via year |
| year | number | no | optional registration year |
| mileage | number | no | optional current mileage in miles |
Search the 530 UK model generations covered by the MOT dataset by free text (e.g. "focus", "golf"). Use to check coverage or disambiguate a generation before uk_mot_reliability. Live proxy to whatbreaks.uk.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | free-text query |
Official UK vehicle safety recalls (DVSA, Open Government Licence; 4876 recalls launched 2016-01-01 → 2027-02-03, 272 makes) for a make and model: recall number, launch date, concern, defect and remedy text (DVSA's English originals), build-date range, vehicles affected and a GOV.UK recall-checker link. Omitting model lists the make's recalls and model names. "Vauxhall Corsa", "vauxhall corsa" and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| make | string | yes | e.g. Vauxhall, Mercedes-Benz, VW, Land Rover |
| model | string | no | e.g. Corsa, A Class, Golf (optional: omit to list the make) |
| since | string | no | optional ISO date YYYY-MM-DD — only recalls launched on/after it |
Keyword search across all served DVSA recalls (make, model names, concern, defect and remedy text), newest first, optionally since a date. Text is English ("airbag", "fire", "steering rack", "takata", "high voltage battery"); every word must appear. Suited to cross-make questions such as recent EV battery fire recalls in the UK.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | words that must all appear, e.g. "airbag takata" |
| since | string | no | optional ISO date YYYY-MM-DD — only recalls launched on/after it |
Official French vehicle recall notices (RappelConso, DGCCRF open data; 1663 automobile fiches 2018-01-19 → 2026-08-07) for a brand and model: fiche number, date, risks, defect description (motif, in French), commercialisation periods and the official fiche link. Omit model to list a brand. Matches by a reviewed alias table plus whole-word text match; each fiche says which.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand | string | yes | e.g. peugeot, Mercedes-Benz, VW |
| model | string | no | e.g. 208, Classe A, Golf (optional: omit to list the brand) |
Keyword search across all RappelConso automobile fiches (brand, model text, label, defect description, risks), newest first, optionally since a date. Text is French and lowercase ("airbag", "incendie", "takata", "batterie haute tension"). Use for cross-brand questions ("recent EV battery fire recalls in France").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | words that must all appear, e.g. "airbag takata" |
| since | string | no | optional ISO date YYYY-MM-DD — only fiches published on/after it |
Official Japanese recall filings (国土交通省 MLIT; 919 filings matched to 75 popular JDM models) for a make and model: notification number, date, defective device, affected vehicles, situation and remedy (Japanese originals) and the official filing PDF. Accepts English (Toyota Prius, Honda N-BOX) or Japanese (トヨタ プリウス) names.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| make | string | yes | e.g. toyota, Honda, スズキ |
| model | string | yes | e.g. prius, N-BOX, ジムニー |
Owner defect reports filed with MLIT's 不具合情報ホットライン (19659 across 75 models): total reports for a model and the breakdown by defective device (brakes, lights, engine, body…) from the newest sample. Reports are unverified owner submissions — compare shapes, not raw counts. Accepts English or Japanese names.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| make | string | yes | e.g. honda |
| model | string | yes | e.g. n-box |
STUB — not yet live. EU Safety Gate (RAPEX) vehicle alerts are being added; until then this returns covered:false with the official Safety Gate URL and points to fr_recalls_* (RappelConso republishes the Safety Gate automobile alerts that concern France).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand | string | no | — |
| model | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Databutler Vehicles or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Databutler Vehicles can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.