Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
CheckFitment 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.
96/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
Bolt patterns and wheel specs by vehicle, wheel and tire fitment, spacer and gear ratio maths.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http checkfitment-mcp 'https://checkfitment.com/mcp?src=mcp'
# 2 — ask your agent for something these tools do
# bolt_pattern_lookup, wheel_fitment_check, tire_size_compare and 3 more
CheckFitment costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CHAll 1 server
checkfitment1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 checkfitment-mcp 'https://checkfitment.com/mcp?src=mcp'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
6 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.
Use for "what is the bolt pattern on a 2019 Ford F-150", lug torque, center bore, thread size, OEM wheel size, offset or tire size of a vehicle, or "will these wheels fit my car" when the vehicle is named. Looks the vehicle up in the CheckFitment dataset (a fixed set of vehicles, each spec cited to manufacturer documents and marked verified or unverified). If the vehicle or year is not in the data
| Parameter | Type | Required | Notes |
|---|---|---|---|
| make | string | yes | e.g. Ford, Toyota, Jeep |
| model | string | yes | e.g. F-150, Tacoma, Wrangler |
| year | integer | no | — |
| wheel_center_bore_mm | number | no | Optional: center bore of a wheel you want to check against the hub. |
Use to compare a current wheel (and tire) with a new one: how far the outer edge pokes toward the fender and the inner edge toward the suspension, the diameter and ride-height change, speedometer effect, backspacing, and whether the new tire width suits the new rim width. With measured clearances (outer: tire edge to fender lip; inner: to the nearest suspension part, both on the current setup) it
| Parameter | Type | Required | Notes |
|---|---|---|---|
| current_wheel_width_in | number | yes | — |
| current_offset_mm | number | yes | — |
| current_tire | string | no | Current tire size. Metric like 265/70R17 (P or LT prefix allowed) or flotation like 33x12.50R17; no load index or speed rating. |
| new_wheel_width_in | number | yes | — |
| new_offset_mm | number | yes | — |
| new_tire | string | no | New tire size. Metric like 265/70R17 (P or LT prefix allowed) or flotation like 33x12.50R17; no load index or speed rating. |
| outer_clearance_mm | number | no | Measured on the current setup: tire sidewall to fender lip. |
| inner_clearance_mm | number | no | Measured on the current setup: inner sidewall to the nearest suspension or body part. |
Use for "what changes if I go from 265/70R17 to 285/75R17", "how far off is my speedometer with 33s", or odometer error after a tire change. Returns diameter, width, sidewall and ride-height change, the true speed when the speedometer shows a given value, the odometer error and how serious it is.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| old_tire | string | yes | Factory or current tire. Metric like 265/70R17 (P or LT prefix allowed) or flotation like 33x12.50R17; no load index or speed rating. |
| new_tire | string | yes | New tire. Metric like 265/70R17 (P or LT prefix allowed) or flotation like 33x12.50R17; no load index or speed rating. |
| speed_shown | number | no | Speedometer reading to convert (default 60). |
Use for "do I need spacers", "what spacer gets +35 wheels to +20", "is a 10 mm slip-on spacer safe". A spacer lowers the effective offset by its thickness. Returns the spacer needed for a target offset (and the nearest common size), the effective offset, track change, whether it is slip-on or bolt-on territory, and, with stud, stud_protrusion_mm and wheel_pad_thickness_mm, the slip-on thread-engag
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset_mm | number | yes | Offset (ET) of the wheel. |
| target_offset_mm | number | no | — |
| spacer_mm | number | no | — |
| stud | string | no | — |
| stud_protrusion_mm | number | no | Stud length past the hub face. |
| wheel_pad_thickness_mm | number | no | Thickness of the wheel mounting pad. |
Use for "what does my 3.73 axle behave like on 35s", "what ratio do I need to regear for 33s", RPM at highway speed after a tire change, or the crawl ratio (with transfer-case low ratio and first gear). Returns the effective ratio, RPM before and after in a 1:1 gear, the ratio that restores stock feel, the nearest gear set actually sold and how serious the change is.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| old_tire | string | yes | Factory tire. Metric like 265/70R17 (P or LT prefix allowed) or flotation like 33x12.50R17; no load index or speed rating. |
| new_tire | string | yes | New tire. Metric like 265/70R17 (P or LT prefix allowed) or flotation like 33x12.50R17; no load index or speed rating. |
| axle_ratio | number | yes | Current axle (differential) ratio, e.g. 3.73. |
| speed_mph | number | no | Road speed for the RPM figures (default 65). |
| transfer_case_low_ratio | number | no | — |
| first_gear_ratio | number | no | — |
Use for "what is 5x114.3 in inches", "is 5x114.3 the same as 5x115", "will 6x135 wheels fit 6x139.7", or which vehicles use a pattern. Converts mm and inch notation, lists look-alike patterns that do not interchange, the vehicles in the dataset with that pattern, the lug tightening order and typical torque ranges by stud size (guidance only).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pattern | string | yes | 5x114.3, 5x4.5, 6x139.7, 8x6.5 … |
Free
$0 forever
- 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 CheckFitment or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.1.0 · scanned 25 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestc31cdcf57378e7f6cfea4894b7cd4e9edac3c6b71dc85354b65312ee06ddf0b1
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| bolt_pattern_lookup | no tags | |
| wheel_fitment_check | no tags | |
| tire_size_compare | no tags | |
| wheel_spacer_calculator | no tags | |
| gear_ratio_calculator | untrusted-input | untrusted-input: keyword "crawl" |
| bolt_pattern_facts | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc31cdcf57378e7f6
Scanned2026-10-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish CheckFitment can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.