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.

io.github.physics-star-cat/whatbreaks-mot

REMOTE · WHATBREAKS.UK

Real UK MOT failure data by car model and mileage, aggregated from official DfT test results.

Available components

0 this week 85 Trust /100

Last scanned (23 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Security74
  • 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 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 & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 285 tokens (~142/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 −3
    • HSTS header: pass → fail ▼ security
  • 26 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “mot_reliability” rewrote its description, which is the text the model reads security
    • Tool “mot_vehicle_search” rewrote its description, which is the text the model reads security
    • Schema quality: 113 → 142 ▼ functional
    • Schema quality: excellent → good functional
  • 4 Oct 26 0
    • Authorization: unverified → partial ▲ security
    • Tool “mot_reliability” rewrote its description, which is the text the model reads security
    • Tool “mot_reliability” changed its title: MOT reliability by model cosmetic
    • Tool “mot_vehicle_search” changed its title: Search vehicles by make/model cosmetic
  • 30 Sept 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://whatbreaks.uk/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.whatbreaks.uk CN=Amazon RSA 2048 S20,O=Amazon,C=US 1 Nov 2026 18 May 2027 RSA 2048 SHA256-RSA 41ddaa80f2ad7e4c0b365a82de7d5fcc
SANs: *.whatbreaks.uk, whatbreaks.uk
CN=Amazon RSA 2048 S20,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 8 Jul 2026 7 Jul 2029 RSA 2048 SHA256-RSA b95efa916a4e6cff9d8348f039fd125b981b5bd
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of whatbreaks.uk. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
whatbreaks.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
x-content-type-options nosniff
x-frame-options DENY

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://whatbreaks.uk/api/mcp Verified 200
http (plaintext) http://whatbreaks.uk/api/mcp HTTPS enforced 301 https://whatbreaks.uk/api/mcp
MCP tools · 2 exposed · ~214 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
mot_reliability ~160

Real UK MOT failure data for a used car: the share of initial MOT tests that failed, overall and per category (overall and at a given mileage), how that compares with cars of the same age and mileage, and the riskiest components with typical failure mileages. Use whenever a user is buying, comparing or maintaining a used car sold in the UK. Data is aggregated from official DfT MOT test results — real outcomes, not estimates. Responses carry a whatbreaks.uk attribution line.

NameTypeReqDescription
makestringyese.g. Volkswagen
mileagenumber–optional current mileage in miles
modelstringyese.g. Golf — generation resolved via year
yearnumber–optional registration year

No output schema declared.

No examples provided.

mot_vehicle_search ~54

Search the covered vehicles (528 UK model generations) by free text. Use to check coverage or disambiguate before calling mot_reliability.

NameTypeReqDescription
qstringyesfree-text query, e.g. "focus"

No output schema declared.

No examples provided.

Install

How do I install the io.github.physics-star-cat/whatbreaks-mot MCP server?

io.github.physics-star-cat/whatbreaks-mot is a hosted endpoint at https://whatbreaks.uk/api/mcp, 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 · whatbreaks.uk

# add to Claude Code
claude mcp add --transport http physics-star-cat-whatbreaks-mot 'https://whatbreaks.uk/api/mcp'
Common questions

What is the io.github.physics-star-cat/whatbreaks-mot MCP server?

io.github.physics-star-cat/whatbreaks-mot is an MCP server listed in the public MCP registry as io.github.physics-star-cat/whatbreaks-mot. Real UK MOT failure data by car model and mileage, aggregated from official DfT test results. This page covers its hosted endpoint (https://whatbreaks.uk/api/mcp).

Is the io.github.physics-star-cat/whatbreaks-mot MCP server safe to use?

io.github.physics-star-cat/whatbreaks-mot scores 85 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/whatbreaks-mot MCP server expose?

io.github.physics-star-cat/whatbreaks-mot exposes 2 tools: mot_reliability, mot_vehicle_search. Their descriptions and schemas cost roughly 214 tokens of context every time the server is loaded.

Does the io.github.physics-star-cat/whatbreaks-mot MCP server require authentication?

No. We connected to io.github.physics-star-cat/whatbreaks-mot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.physics-star-cat/whatbreaks-mot MCP server still maintained?

io.github.physics-star-cat/whatbreaks-mot 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 io.github.physics-star-cat/whatbreaks-mot MCP server?

VerifyMCP ran 13 checks on io.github.physics-star-cat/whatbreaks-mot, 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.