# Window Sticker (remote · windowsticker.org)

Original factory window stickers (Monroney labels) by VIN for 20 makes, plus an NHTSA spec decode.

- Trust score: 78/100 (medium)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `windowsticker.org`: 78/100 (this document), [markdown](https://verifymcp.io/servers/org-windowsticker-window-sticker/windowsticker.md), [page](https://verifymcp.io/servers/org-windowsticker-window-sticker/windowsticker)

## Channel facts

- Endpoint: `https://windowsticker.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 375 tokens (~125/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Window Sticker MCP server?

Window Sticker is a hosted endpoint at https://windowsticker.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-windowsticker-window-sticker 'https://windowsticker.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-windowsticker-window-sticker": {
      "url": "https://windowsticker.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-windowsticker-window-sticker": {
      "type": "http",
      "url": "https://windowsticker.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-windowsticker-window-sticker]
url = "https://windowsticker.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-windowsticker-window-sticker": {
      "type": "remote",
      "url": "https://windowsticker.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-windowsticker-window-sticker --url 'https://windowsticker.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-windowsticker-window-sticker:
    url: "https://windowsticker.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-windowsticker-window-sticker": {
      "Transport": "http",
      "Url": "https://windowsticker.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-windowsticker-window-sticker -t streamable-http -u 'https://windowsticker.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-windowsticker-window-sticker": {
      "type": "http",
      "url": "https://windowsticker.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-29 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 75, +7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-26 (score 67)

First indexed and scored.

## MCP tools (3)

### `get_window_sticker` (~111 tokens)

Get a window sticker by VIN

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. For Toyota, Lexus, Nissan and Infiniti it returns only labels we already hold. Free, no key.

Input parameters:

- `vin` (string, required): 17-character VIN. VINs never contain I, O or Q.

Output parameters:

- `vehicle`: NHTSA vPIC decode. Null when vPIC did not recognise the VIN.
- `vin` (string)
- `warning`
- `windowSticker` (object)

### `which_makes_are_covered` (~52 tokens)

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.

Output parameters:

- `asOf` (string)
- `coverageUrl` (string)
- `notes` (array)
- `sources` (array)

### `why_no_sticker` (~111 tokens)

Why no window 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).

Input parameters:

- `make` (string, required): Make name, such as Ford, Chevrolet or Honda.
- `model_year` (integer): Model year, such as 2019. Optional; the Toyota and Lexus answer depends on it.

Output parameters:

- `headline` (string)
- `make` (string)
- `modelYear`
- `moreUrl` (string)
- `reason` (string)
- `source`
- `steps` (array)
- `supported` (boolean): We have a source of original labels for this make.
- `warning`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-windowsticker-window-sticker/windowsticker#diagnostics

## Score history

- 2026-10-04: 78
- 2026-10-03: 77
- 2026-10-02: 77
- 2026-10-01: 77
- 2026-09-30: 76
- 2026-09-29: 76
- 2026-09-28: 75
- 2026-09-27: 68
- 2026-09-26: 67

## Common questions

### What is the Window Sticker MCP server?

Window Sticker is an MCP server listed in the public MCP registry as org.windowsticker/window-sticker. Original factory window stickers (Monroney labels) by VIN for 20 makes, plus an NHTSA spec decode. This page covers its hosted endpoint (https://windowsticker.org/mcp).

### Is the Window Sticker MCP server safe to use?

Window Sticker scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Window Sticker MCP server expose?

Window Sticker exposes 3 tools: get_window_sticker, which_makes_are_covered, why_no_sticker. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.

### Does the Window Sticker MCP server require authentication?

No. We connected to Window Sticker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Window Sticker MCP server still maintained?

Window Sticker is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://windowsticker.org/mcp
- Website: https://windowsticker.org/api-docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-windowsticker-window-sticker/windowsticker.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-windowsticker-window-sticker/windowsticker.json
- HTML version of this page: https://verifymcp.io/servers/org-windowsticker-window-sticker/windowsticker