io.github.physics-star-cat/databutler-vehicles
REMOTE · DATABUTLER.DEV
UK MOT failure data and official UK, French, Japanese and EU vehicle recalls.
Available components
Last scanned (2 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 1 Nov 26 −52
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.90 → unverified ▼ security
- Authorization: partial → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Tool “jp_complaints_summary” rewrote its description, which is the text the model reads security
- Tool “jp_recalls_for_model” rewrote its description, which is the text the model reads security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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://databutler.dev/api/mcp/vehicles
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=databutler.dev | CN=YR2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | RSA 2048 | SHA256-RSA | 57e71073bd6e862c7a4f13070ec548fa698 |
| SANs: databutler.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 databutler.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| databutler.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://databutler.dev/api/mcp/vehicles | Auth required | 403 | |
| http (plaintext) | http://databutler.dev/api/mcp/vehicles | HTTPS enforced | 308 | https://databutler.dev/api/mcp/vehicles |
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 →
eu_safety_gate_recalls EU Safety Gate recalls (stub) ~82
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).
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| model | string | – | – |
No output schema declared.
No examples provided.
fr_recalls_for_model French recalls for a model ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | e.g. peugeot, Mercedes-Benz, VW |
| model | string | – | e.g. 208, Classe A, Golf (optional: omit to list the brand) |
No output schema declared.
No examples provided.
fr_recalls_search French recalls search ~124
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").
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | optional ISO date YYYY-MM-DD — only fiches published on/after it |
| text | string | yes | words that must all appear, e.g. "airbag takata" |
No output schema declared.
No examples provided.
jp_complaints_summary Japanese owner complaints summary ~105
Owner defect reports filed with MLIT's 不具合情報ホットライン (39954 across 313 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.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | e.g. honda |
| model | string | yes | e.g. n-box |
No output schema declared.
No examples provided.
jp_recalls_for_model Japanese recalls for a model ~135
Official Japanese recall filings (国土交通省 MLIT; 3283 filings matched to 313 models sold in Japan, incl. Lexus and imports) 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.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | e.g. toyota, Honda, スズキ |
| model | string | yes | e.g. prius, N-BOX, ジムニー |
No output schema declared.
No examples provided.
uk_mot_reliability UK MOT reliability ~159
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 result lists candidates — retry with year or the exact model name.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | e.g. Volkswagen |
| mileage | number | – | optional current mileage in miles |
| model | string | yes | e.g. Golf — generation resolved via year |
| year | number | – | optional registration year |
No output schema declared.
No examples provided.
uk_mot_vehicle_search UK MOT vehicle search ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | free-text query |
No output schema declared.
No examples provided.
uk_recalls_for_model UK recalls for a model ~233
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 "VAUXHALL CORSA" resolve identically; "Mercedes-Benz", "VW" and "Land Rover" are understood. Covers cars, vans, HGVs, buses, motorcycles, trailers and components, not individual VINs.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | e.g. Vauxhall, Mercedes-Benz, VW, Land Rover |
| model | string | – | e.g. Corsa, A Class, Golf (optional: omit to list the make) |
| since | string | – | optional ISO date YYYY-MM-DD — only recalls launched on/after it |
No output schema declared.
No examples provided.
uk_recalls_search UK recalls search ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | optional ISO date YYYY-MM-DD — only recalls launched on/after it |
| text | string | yes | words that must all appear, e.g. "airbag takata" |
No output schema declared.
No examples provided.
How do I install the io.github.physics-star-cat/databutler-vehicles MCP server?
io.github.physics-star-cat/databutler-vehicles is a hosted endpoint at https://databutler.dev/api/mcp/vehicles, 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 · databutler.dev
claude mcp add --transport http physics-star-cat-databutler-vehicles 'https://databutler.dev/api/mcp/vehicles'
What is the io.github.physics-star-cat/databutler-vehicles MCP server?
io.github.physics-star-cat/databutler-vehicles is an MCP server listed in the public MCP registry as io.github.physics-star-cat/databutler-vehicles. UK MOT failure data and official UK, French, Japanese and EU vehicle recalls. This page covers its hosted endpoint (https://databutler.dev/api/mcp/vehicles).
Is the io.github.physics-star-cat/databutler-vehicles MCP server safe to use?
io.github.physics-star-cat/databutler-vehicles scores 33 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 io.github.physics-star-cat/databutler-vehicles MCP server expose?
io.github.physics-star-cat/databutler-vehicles exposes 9 tools: uk_mot_reliability, uk_mot_vehicle_search, uk_recalls_for_model, uk_recalls_search, fr_recalls_for_model, and 4 more. Their descriptions and schemas cost roughly 1,188 tokens of context every time the server is loaded.
Does the io.github.physics-star-cat/databutler-vehicles MCP server require authentication?
Yes. io.github.physics-star-cat/databutler-vehicles asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.physics-star-cat/databutler-vehicles MCP server still maintained?
io.github.physics-star-cat/databutler-vehicles 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.