Mcp Server Wheel Size

io.github.AIWerkPublished by GitHub account AIWerkv0.3.3Updated Oct 24, 2026

Wheel-Size.com fitment API: OEM and aftermarket wheel and tyre data for 100k+ vehicles (read-only).

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant look up OEM and aftermarket wheel and tyre fitment data for over 100,000 vehicles via the Wheel-Size.com API.

What you can do
This local MCP server connects an assistant to the Wheel-Size.com fitment API, which holds OEM and aftermarket wheel and tyre data covering more than 100,000 vehicles. The registry description presents the access as read-only, so the assistant can retrieve fitment information rather than change anything. The manifest does not list individual tools, so the exact query surface is not documented here.
When to use it
Worth adding when an assistant needs vehicle wheel or tyre fitment lookups, for example to answer questions about compatible sizes or specifications for a given vehicle. It is not intended for general web search or unrelated automotive data.
Requirements
Runs as a local process over stdio, installed from the npm package @aiwerk/mcp-server-wheel-size, so Node.js and npm are needed. It requires a Wheel-Size.com API key supplied through the environment variable WHEEL_SIZE_API_KEY; the manifest declares no other authentication. Network access to the Wheel-Size.com API is required. Desktop only.
Before you install
The server requires the secret WHEEL_SIZE_API_KEY, which is sent to Wheel-Size.com as part of API calls; keep it out of shared logs and configuration. The manifest declares no authentication beyond that key and lists no tools, so review what the server actually calls before relying on it. The description states the API access is read-only, but this is third-party documentation and not independently verified.

Installation

In SourceWeft

  1. Open Mcp Server Wheel Size in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.