Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

UK Data: US vehicle safety (NHTSA)

REMOTE · UKDATA.RELINESS.CO.UK

US vehicle safety from NHTSA: recalls, owner complaints, crash-test ratings and VIN checks

+3 this week 75 Trust /100

Last scanned (22 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security69
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • 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
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1697 tokens (~169/item across 10 items; 10 tools + 0 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 Management47
  • Stability observed for 14 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 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.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 69

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://ukdata.reliness.co.uk/mcp/vehicles-safety

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=reliness.co.uk CN=WE1,O=Google Trust Services,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA256 f1d4f4e9f24c919b0e13c306162294a4
SANs: reliness.co.uk, ukdata.reliness.co.uk, *.ukdata.reliness.co.uk
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ukdata.reliness.co.uk. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
co.uk. DS published 11810 8 Verified
reliness.co.uk. No DS 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=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ukdata.reliness.co.uk/mcp/vehicles-safety Verified 200
http (plaintext) http://ukdata.reliness.co.uk/mcp/vehicles-safety Served over HTTP 200
MCP tools · 10 exposed · ~1,697 tokens

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 →

Tool Tokens
complaint_by_odi_number ~130

Read one NHTSA owner safety complaint by its ODI number: vehicle, components, crash, fire, injuries and deaths reported, incident and filing dates, partial VIN and the owner's own description. For lawyers, investigators, journalists and owners following up a complaint found with vehicle_complaints. Source: NHTSA Office of Defects Investigation complaints. The account is the owner's own and is not verified by NHTSA. (cost: 1 credit)

NameTypeReqDescription
odinumberstring–integer, required, NHTSA ODI complaint number, e.g. 11772096

No output schema declared.

No examples provided.

recall_campaign_details ~132

Look up one recall by its NHTSA campaign number (for example 20V314000, as printed on a US recall letter) and get the defect, risk, remedy, the number of vehicles potentially affected and every make, model and year it covers. For owners, journalists, lawyers and fleet managers. Source: NHTSA Recalls API. It does not say whether a specific vehicle has been repaired. (cost: 1 credit)

NameTypeReqDescription
campaignNumberstring–string, required, NHTSA campaign number, e.g. 20V314000 or 20V-314

No output schema declared.

No examples provided.

vehicle_complaints ~199

What goes wrong with this car? Summarises owner-filed safety complaints to NHTSA for a make, model and model year: total complaints, crashes, fires, injuries and deaths reported, the most-complained-about components, and the latest complaints with their text. For used-car buyers, owners and researchers. Source: NHTSA Office of Defects Investigation complaints. Complaints are unverified owner reports, not proven defects, and counts partly reflect how many cars were sold. (cost: 1 credit)

NameTypeReqDescription
limitstring–integer, optional, latest complaints to list, 1-50, default 10
makestring–string, required, vehicle make, e.g. honda
modelstring–string, required, US model name, e.g. accord
modelYearstring–integer, required, model year, e.g. 2019

No output schema declared.

No examples provided.

vehicle_crash_ratings ~173

How safe is this car in a crash? Returns the US NCAP 5-Star Safety Ratings for a make, model and model year, one entry per body style or drivetrain: overall, frontal (driver and passenger), side barrier and side pole, and rollover stars with the rollover risk percentage. For family car buyers comparing models. Source: NHTSA NCAP. These are US tests; Euro NCAP scores for UK-market cars are separate and not comparable star for star. (cost: 1 credit)

NameTypeReqDescription
makestring–string, required, vehicle make, e.g. honda
modelstring–string, required, US model name, e.g. accord
modelYearstring–integer, required, model year, e.g. 2019

No output schema declared.

No examples provided.

vehicle_driver_assist_features ~167

Does this car have lane departure warning or forward collision warning as standard? Returns whether electronic stability control, forward collision warning and lane departure warning are standard, optional or not available, per body style, for a make, model and model year. For buyers comparing trims and insurers. Source: NHTSA NCAP records. It covers only these three technologies and only cars in the NCAP programme; it does not cover automatic emergency braking or other features. (cost: 1 credit)

NameTypeReqDescription
makestring–string, required, vehicle make, e.g. honda
modelstring–string, required, US model name, e.g. accord
modelYearstring–integer, required, model year, e.g. 2019

No output schema declared.

No examples provided.

vehicle_manufacturer_details ~179

Who is this vehicle manufacturer and where are they registered? Returns NHTSA registration details for manufacturers matching a name or manufacturer ID: legal and common name, trading names, address and country, manufacturer type (for example completed vehicle manufacturer, vehicle alterer, importer), vehicle types and weight classes, named principal and last update. For supplier research, KYB and procurement checks. Source: NHTSA vPIC. Name matching is partial, so expect related firms such as dealers; personal contact emails are left out. (cost: 1 credit)

NameTypeReqDescription
limitstring–integer, optional, max manufacturers to return, 1-50, default 10
manufacturerstring–string, required, manufacturer name (partial match, e.g. honda) or NHTSA manufacturer ID (e.g. 988)

No output schema declared.

No examples provided.

vehicle_models_for_make_year ~177

Which models did this make produce in a given model year? Lists the model names NHTSA holds for a make and year, A to Z, so an agent can check the exact model name before a recall, complaint or crash-rating lookup. For dealers, form-filling and data cleaning. Source: NHTSA vPIC. It includes every vehicle type the make registered (cars, motorcycles, trucks) with US model names, and does not give trims or specifications. (cost: 1 credit)

NameTypeReqDescription
limitstring–integer, optional, max models to return, 1-100, default 25
makestring–string, required, vehicle make, e.g. honda
modelYearstring–integer, required, model year, e.g. 2019

No output schema declared.

No examples provided.

vehicle_problem_counts ~162

How many complaints, recalls and federal defect investigations does this model have? Returns the three counts NHTSA links to a make, model and model year, as a quick screen when comparing cars. Source: NHTSA NCAP records. Counts are not adjusted for sales volume, so a popular model will show more; only models in the NCAP programme are covered. Use vehicle_recalls and vehicle_complaints for the detail. (cost: 1 credit)

NameTypeReqDescription
makestring–string, required, vehicle make, e.g. honda
modelstring–string, required, US model name, e.g. accord
modelYearstring–integer, required, model year, e.g. 2019

No output schema declared.

No examples provided.

vehicle_recalls ~221

Are there recalls on this car? Lists every US safety recall NHTSA holds for a make, model and model year, newest first, with the faulty component, the risk, the remedy and do-not-drive or park-outside warnings. For owners, used-car buyers and fleet managers. Source: NHTSA Recalls API. It lists recalls for the model, not whether a particular car has been repaired (check that by VIN with the maker or at nhtsa.gov), and it does not cover UK (DVSA) recalls. (cost: 1 credit)

NameTypeReqDescription
limitstring–integer, optional, max recalls to return, 1-100, default 25
makestring–string, required, vehicle make, e.g. honda, ford, tesla
modelstring–string, required, US model name, e.g. accord, f-150, model 3
modelYearstring–integer, required, model year, e.g. 2019

No output schema declared.

No examples provided.

wmi_manufacturer_lookup ~157

Who made the vehicle with this VIN prefix? Decodes a World Manufacturer Identifier (the first 3 characters of a VIN, or 6 for small makers whose third character is 9) to the manufacturer, make, vehicle type and broad region, and accepts a full 17-character VIN to read its prefix. For fleet, import, parts and used-car checks. Source: NHTSA vPIC. It identifies the maker only, not the specific vehicle; use a full VIN decoder for model and specification. (cost: 1 credit)

NameTypeReqDescription
wmistring–string, required, 3- or 6-character WMI (e.g. 1HG) or a full 17-character VIN

No output schema declared.

No examples provided.

Install

How do I install the UK Data: US vehicle safety (NHTSA) MCP server?

UK Data: US vehicle safety (NHTSA) is a hosted endpoint at https://ukdata.reliness.co.uk/mcp/vehicles-safety, 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 · ukdata.reliness.co.uk

# add to Claude Code
claude mcp add --transport http uk-co-reliness-vehicles-safety 'https://ukdata.reliness.co.uk/mcp/vehicles-safety'
Common questions

What is the UK Data: US vehicle safety (NHTSA) MCP server?

UK Data: US vehicle safety (NHTSA) is an MCP server listed in the public MCP registry as uk.co.reliness/vehicles-safety. US vehicle safety from NHTSA: recalls, owner complaints, crash-test ratings and VIN checks. This page covers its hosted endpoint (https://ukdata.reliness.co.uk/mcp/vehicles-safety).

Is the UK Data: US vehicle safety (NHTSA) MCP server safe to use?

UK Data: US vehicle safety (NHTSA) 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 UK Data: US vehicle safety (NHTSA) MCP server expose?

UK Data: US vehicle safety (NHTSA) exposes 10 tools: vehicle_recalls, recall_campaign_details, vehicle_complaints, complaint_by_odi_number, vehicle_crash_ratings, and 5 more. Their descriptions and schemas cost roughly 1,697 tokens of context every time the server is loaded.

Does the UK Data: US vehicle safety (NHTSA) MCP server require authentication?

No. We connected to UK Data: US vehicle safety (NHTSA) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the UK Data: US vehicle safety (NHTSA) MCP server still maintained?

UK Data: US vehicle safety (NHTSA) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the UK Data: US vehicle safety (NHTSA) MCP server?

VerifyMCP ran 13 checks on UK Data: US vehicle safety (NHTSA), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.