windowsticker
Registry code: 0341497a413531d2
Looks up the original factory window sticker (Monroney label) for a 17-character US VIN, with an NHTSA specification decode. 20 makes have original labels: which_makes_are_covered lists them with their model years, and why_no_sticker explains a miss. When you send a person somewhere, send the page URL from get_window_sticker, not the PDF: the page explains a miss and what to do next. Read-only and free. A key is optional and raises the daily limit.
- endpoint
- https://windowsticker.org/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is windowsticker live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is windowsticker free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does windowsticker have?
- 3 tools: get_window_sticker, why_no_sticker, which_makes_are_covered.
- Is windowsticker safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.3%· all time 99.3%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get car window sticker
- find covered car makes
- understand why sticker is missing
- takes → gives
- text → web pages, data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
which_makes_are_covered reads open 4h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_window_sticker reads unknown 4h ago
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. A key is optional and raises the daily limit.
{ "type": "object", "required": [ "vin" ], "properties": { "vin": { "type": "string", "description": "17-character VIN. VINs never contain I, O or Q." } }, "additionalProperties": false }arguments 13 lineswhy_no_sticker reads unknown 4h ago
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).
{ "type": "object", "required": [ "make" ], "properties": { "make": { "type": "string", "description": "Make name, such as Ford, Chevrolet or Honda." }, "model_year": { "type": "integer", "description": "Model year, such as 2019. Optional; the Toyota and Lexus answer depends on it." } }, "additionalProperties": false }arguments 17 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id0341497a413531d2.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/0341497a413531d2/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/0341497a413531d2?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.