Connect Window Sticker and your agent gets 3 tools, among them get_window_sticker, which_makes_are_covered, why_no_sticker. It answers at https://windowsticker.org/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 27 September 2026; the last check, on 11 November 2026, succeeded.
Original factory window stickers (Monroney labels) by VIN for 20 makes, plus an NHTSA spec decode.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_window_sticker | Look up the original factory window sticker (Monroney label) for a 17-character VIN, with an NHTSA specification decode. Returns links, never the PDF itself: `page` is the result page to give a person, and `pdf` is the label when one exists Inputs: vin |
which_makes_are_covered | The 20 makes that return an original factory window sticker, by source, with the model years each answers for and the last day it returned a label. Every other make gets a specification decode only. |
why_no_sticker | Why a make, or a make and model year, has no window sticker here, and where to get one instead. Covers makes we get labels for (Ford only while a car is new, Toyota from 2025) and makes we don’t (Honda, Mazda, Tesla). Inputs: make, model_year |
Every block below points at https://windowsticker.org/mcp. Pick your client and copy.
claude mcp add --transport http window-sticker https://windowsticker.org/mcp
{
"mcpServers": {
"window-sticker": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://windowsticker.org/mcp"]
}
}
}{
"mcpServers": {
"window-sticker": {
"url": "https://windowsticker.org/mcp"
}
}
}{
"servers": {
"window-sticker": {
"type": "http",
"url": "https://windowsticker.org/mcp"
}
}
}{
"context_servers": {
"window-sticker": {
"url": "https://windowsticker.org/mcp"
}
}
}{
"mcpServers": {
"window-sticker": {
"serverUrl": "https://windowsticker.org/mcp"
}
}
}{
"mcpServers": {
"window-sticker": {
"url": "https://windowsticker.org/mcp"
}
}
}name: Window Sticker
version: 0.0.1
schema: v1
mcpServers:
- name: Window Sticker
type: streamable-http
url: https://windowsticker.org/mcp{
"mcpServers": {
"window-sticker": {
"httpUrl": "https://windowsticker.org/mcp"
}
}
}{
"mcpServers": {
"window-sticker": {
"type": "http",
"url": "https://windowsticker.org/mcp"
}
}
}{
"mcpServers": {
"window-sticker": {
"url": "https://windowsticker.org/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwindowsticker.org%2Fmcp&type=streamable_http&id=window-sticker&name=Window%20Sticker
It answered our last check on 11 November 2026 in 259 ms. Over 4 checks since 27 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by windowsticker.org and served from windowsticker.org, the vendor's own domain: https://windowsticker.org/mcp.
3, as returned by the server's own tools/list on 16 November 2026: get_window_sticker, which_makes_are_covered, why_no_sticker.
It answered our last check on 11 November 2026 in 259 ms. Over 4 checks since 27 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://windowsticker.org/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: org.windowsticker. Endpoint host: windowsticker.org. ARD identifier: urn:air:org.windowsticker:mcp:window-sticker.
First indexed 26 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.