A remote MCP server that lets an assistant identify a vehicle and look up its specifications, wheel and tire fitment, safety records and fuel efficiency.
What you can do
Resolve a vehicle from a VIN or from year, make and model, returning a single match or asking for more identity details instead of guessing between configurations. Retrieve engine and powertrain specifications such as displacement, cylinders, horsepower, transmission, drivetrain and fuel type. Look up wheel and tire fitment, including OEM tire sizes, bolt pattern, center bore, offset and lug size. Check NHTSA-backed recalls, complaints, investigations, manufacturer communications and safety ratings. Read EPA city, highway and combined MPG, MPGe, range, fuel cost and emissions figures.
When to use it
Useful when an assistant needs reliable, identity-checked vehicle facts for automotive shopping, maintenance, parts or fitment questions, or safety and efficiency comparisons, and should not invent details for ambiguous configurations.
Requirements
A remote endpoint reached over streamable HTTP; no local package or runtime is needed. A required API key is sent in the X-AUTO411-Key header. Network access to the hosted service is required.
Before you install
The service requires an API key in the X-AUTO411-Key header, so treat it as a secret and check the provider's terms and any usage limits. Queries send vehicle identifiers such as VINs or year, make and model to a third-party service. Results are read-only lookups, but ambiguous configurations are reported as needing identity rather than resolved.
Connect X-AUTO411-Key credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.simonizer69%2Fauto411-vehicle-intelligence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Use this when identifying a vehicle from a full VIN or from year, make, and model with optional configuration refinements. Returns MATCHED_SINGLE, NEEDS_IDENTITY, or NO_MATCH and never silently chooses among legitimate configurations.
Use this when engine and powertrain specifications are needed for a vehicle identified by VIN or year, make, and model. Returns normalized supported facts such as engine, displacement, cylinders, horsepower, transmission, drivetrain, and fuel type only after identity resolves safely.
Use this for wheel and tire fitment after identifying a vehicle by VIN or year, make, and model. Returns available OEM tire sizes, bolt pattern / PCD, center bore, wheel offset, and thread / lug size without guessing through ambiguous configurations.
Use this for available NHTSA-backed recalls, complaints, investigations, manufacturer communications, and safety ratings. Safety facts remain explicitly YMM-scoped and never establish configuration identity.
Use this for available EPA city, highway, and combined MPG, MPGe, range, fuel-cost, emissions, and related efficiency facts after vehicle identity resolves safely. Ambiguous EPA variants remain NEEDS_IDENTITY.
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 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.