StickerByVIN logo

StickerByVIN

Look up vehicle details, window-sticker availability, model recalls, and paint-code location from a 17-character VIN.

Install StickerByVIN

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://stickerbyvin.com/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 7h agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 7h ago · Nov 13, 2026, 17:30 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://stickerbyvin.com/mcp

Overview

StickerByVIN accepts a 17-character VIN through a remote MCP endpoint and returns vehicle identification details, window-sticker availability, recall counts, and paint-code location. Its main tool, `check_window_sticker`, covers vehicles sold new in the United States. Reach for it when an agent needs factory vehicle data or wants to check whether a Monroney label is available without retrieving accident, title, or ownership history. The endpoint requires no authentication.

Use cases

  • Decode a vehicle from its 17-character VIN
  • Check whether a factory Monroney label is available
  • Count recalls issued for a vehicle model
  • Find where the vehicle's paint code is printed

Key features

  • Remote MCP endpoint with no authentication
  • 17-character VIN decoding
  • Factory window-sticker availability checks
  • Model recall counts
  • Paint-code location guidance
  • US-market vehicle coverage

Tools1

What StickerByVIN lets your agent do. Expand a tool for its parameters.

Verified live~210 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

What it can do

From the 1 tool this server returned when we ran it.

Read-only tools · 1

Observed 2026-11-13 in an isolated sandbox. A description of reach, not a security audit.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

MaintenanceActively maintainedStatus declared by the project or listing owner.
Tools exposed1Callable tools this server registers over MCP.

How StickerByVIN works

What StickerByVIN does

StickerByVIN provides a VIN lookup through the Model Context Protocol. An MCP client sends a 17-character vehicle identification number to the remote service, and the service returns information about the corresponding vehicle and its factory window-sticker record.

The response can identify the vehicle's year, make, model, trim, engine, drivetrain, body type, and assembly plant. It also indicates whether the original factory window sticker, commonly called a Monroney label, is on file for that VIN. In addition, the service reports how many recalls were issued for the model and explains where the vehicle's paint code is printed.

Coverage is for vehicles sold new in the United States. Original stickers are primarily available for recent models from Ford, Lincoln, Jeep, Ram, Dodge, Chrysler, Chevrolet, GMC, Cadillac, Buick, Toyota, Lexus, Hyundai, Kia, and Nissan.

How it works

StickerByVIN is accessed as a remote MCP server at https://stickerbyvin.com/mcp. The endpoint does not require authentication. An MCP-compatible client can expose the available tool to an agent, which then supplies the VIN when a user asks for vehicle or sticker information.

The lookup is centered on one input: a 17-character VIN. The tool uses that identifier to decode the vehicle and check related factory-sticker and model-recall information. Paint-code guidance identifies where to look on the vehicle; it is not a replacement for inspecting the vehicle itself.

Setup and configuration

Configure an MCP client to use the remote server endpoint:

text
https://stickerbyvin.com/mcp

No API key or other authentication value is required. After adding the endpoint, the client can make check_window_sticker available to an agent. The agent should provide a complete 17-character VIN for each lookup.

Tools and capabilities

check_window_sticker

Use this tool to:

  • Decode the vehicle year, make, model, trim, engine, drivetrain, body, and assembly plant.
  • Check whether the original factory window sticker is on file for the VIN.
  • Count recalls issued for the vehicle's model.
  • Locate the vehicle's paint-code label or marking.

The tool is intended for vehicle identification and factory-sticker checks. It does not return accident history, title history, or ownership history.

Limitations and notes

A valid 17-character VIN is required. Results apply to vehicles sold new in the United States. Sticker availability varies by vehicle, with the strongest coverage focused on recent models from the listed manufacturers; a decoded vehicle does not necessarily mean its original Monroney label is on file. Recall counts are reported for the model rather than as a vehicle-specific recall or ownership record. Paint-code output describes where to find the code, not the code itself.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about StickerByVIN

StickerByVIN is an MCP server that connects AI clients to a remote VIN lookup service. Its `check_window_sticker` tool identifies a vehicle, checks whether its original Monroney label is on file, counts recalls for the model, and shows where to find the paint code. It requires a 17-character VIN and no authentication.

Add `https://stickerbyvin.com/mcp` as a remote MCP server in an MCP-compatible client. No API key or authentication setting is required. Once configured, expose the `check_window_sticker` tool to the agent and provide a complete 17-character VIN.

StickerByVIN returns the vehicle's year, make, model, trim, engine, drivetrain, body, and assembly plant. It also reports window-sticker availability, the model's recall count, and where the paint code is printed.

No, StickerByVIN does not provide accident, title, or ownership history. Its lookup focuses on vehicle decoding, original factory window-sticker availability, model recall counts, and paint-code location.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewStickerByVIN AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/stickerbyvin?style=directory)](https://allmcps.com/mcp/stickerbyvin)
HTML Embed
<a href="https://allmcps.com/mcp/stickerbyvin"><img src="https://allmcps.com/api/badge/stickerbyvin?style=directory" alt="StickerByVIN on AllMCPs" /></a>