Plateop vehicle check

com.plateopPublished by plateop.comOfficial publisherv0.1.1Updated Nov 2, 2026

Free used-car facts from the official register (NL, GB, IL, IS, DK) with source and date.

The publisher's own server: Agent Commons

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Remote MCP server that gives an assistant free official-register facts about a used car (NL, GB, IL, IS, DK) plus model-wide inspection statistics.

What you can do
  • Look up one used car by plate and country: register data, inspection due date, odometer verdict, insurance, inspection findings and recalls, each with source and as-of date.
  • Get model-wide periodic inspection statistics for a make and model, with the three most frequent inspection points per source and age band and a citation line.
  • Receive a link where a person can start the full paid report.
When to use it
Useful when someone is evaluating a specific used car and wants free, sourced register facts before buying a paid report, or when comparing how often a make and model fails periodic inspection.
Requirements
A remote Streamable HTTP endpoint; nothing to install locally. No account or API key is declared. Only the five supported country codes (nl, gb, il, is, dk) are served.
Before you install
Every vehicle check answer ends with a link to a paid report (4.95 euro in the Netherlands); the server itself does not charge. Calls forward the caller's IP and any Authorization header to the Plateop app. Per-IP rate limits apply (20 per 10 minutes and 100 per day for vehicle checks).

Installation

In SourceWeft

  1. Open Plateop vehicle check in the dashboard and add it to a workspace.
  2. 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/com.plateop%2Fplateop-check/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "plateop-vehicle-check": {
      "type": "http",
      "url": "https://check.plateop.com/mcp"
    }
  }
}

README

plateop-check-mcp

A remote MCP server (Streamable HTTP, stateless) that gives AI agents the free facts about a used car from Plateop: register data, inspection due date, odometer verdict, insurance, inspection findings and recalls, each with source and as-of date. It is a thin layer over Plateop's public JSON channel (GET /api/rapport/kenteken/{plate}, GET /open/model/<brand>/<model>.json). It has no data layer, no cache, no database and no accounts.

Revenue model: every vehicle_check answer ends with a link for a person to the paid report (4.95 euro in the Netherlands) on the country host, https://<host>.plateop.com/analyse/nieuw, without the plate in the URL. An Authorization header sent by the agent is passed to the app unchanged, so a paid tier later needs no change here.

Source: https://github.com/gvb9/plateop-check-mcp. Deployment: ./server-setup.sh once, then ./deploy.sh. Published in the MCP Registry as com.plateop/plateop-check 0.1.0 (18 Oct 2026); a new version needs a version bump, mcp-publisher login http and mcp-publisher publish (see agent-commons docs/VINDBAARHEID.md).

Tools

ToolWhat it doesPlateop call
vehicle_check(plate, country, language?)Facts per heading as text, raw JSON as structuredContent, then the paid-report line/api/rapport/kenteken/{plate}?taal=
model_inspection_stats(brand, model, country, language?)Per source and age band the 3 most frequent inspection points (the app lists all 300; the answer links to the full JSON), with the citation line/open/model/<brand-slug>/<model-slug>.json

Countries: nl (host nederland), gb (uk), il (israel), is (island), dk (danmark). Each call sends Host and X-Forwarded-Host: <host>.plateop.com (the app reads Host; node:http is used because fetch cannot set it), X-Real-IP and X-Forwarded-For with the agent's IP, and the agent's Authorization header if there is one. Timeout 10 s. App errors (400, 404, 429 with Retry-After, 502, 503) become one plain sentence for the agent.

Routes: POST /mcp, GET / (text), /llms.txt (guide), /health, /privacy, /icon.svg, /.well-known/mcp/server-card.json. server.json is for the MCP Registry (com.plateop/plateop-check).

Left out on purpose: compare_models. The app's /open/vergelijk/<pair>.json only answers for a short frozen list of model pairs on nl, gb and cz, with no way to list them, so a tool would mostly return "not found". Add it when agents ask for it.

Limits (per hashed IP, in memory)

vehicle_check 20 per 10 minutes and 100 per day (the same as the app's own limit); model tool 60 per minute; plain GET routes 600 per hour. No timers, no disk: stale windows are pruned on use and everything resets on restart.

Environment variables

VariableMeaning
PORTListen port, default 3200
PLATEOP_BASE_URLThe Plateop app, default and production value http://127.0.0.1:3105
TRUST_PROXY1 behind nginx: read the caller's IP from X-Real-IP / X-Forwarded-For
IP_SALTOptional. Salt of the IP hash; unset means random per start (limits and the hash in the log reset on restart)

There is no DATA_DIR: nothing is written to disk.

Run

bash
npm installnpm test        # vitest against a fake Plateop (test/fakePlateop.ts); no real callsnpm run buildPLATEOP_BASE_URL=http://127.0.0.1:3105 TRUST_PROXY=1 npm start

Rollout (nothing of this has been done)

  1. On the server: useradd --system plateop-check, mkdir -p /srv/plateop-check /etc/plateop-check, env file /etc/plateop-check/plateop-check.env (root:plateop-check, mode 640) with PORT=3200, PLATEOP_BASE_URL=http://127.0.0.1:3105, TRUST_PROXY=1.
  2. systemd unit plateop-check (like commons): ExecStart=/usr/bin/node /srv/plateop-check/current/dist/index.js, EnvironmentFile=, User=plateop-check, Restart=on-failure.
  3. nginx site zz-plateop-check for check.plateop.com behind Cloudflare, like zz-commons: proxy_pass http://127.0.0.1:3200, proxy_set_header X-Real-IP $remote_addr (or the Cloudflare IP module's value), X-Forwarded-Proto, Host. No DNS change: *.plateop.com already points at the server.
  4. The privacy page promises that the journal keeps the call log for at most 30 days: set MaxRetentionSec=30day in /etc/systemd/journald.conf (or change the sentence in src/privacy.ts).
  5. ./deploy.sh, then curl https://check.plateop.com/health, then one vehicle_check with an MCP client.
  6. Publish server.json to the MCP Registry under com.plateop.
  7. After 30 days count calls per tool and per shortened hash: journalctl -u plateop-check | grep tool=.

Source: README.md at commit f4c0711

Tools

2

vehicle_check

Check a vehicle by plate

Free facts about one used car from the official register: vehicle data, periodic inspection due date, odometer verdict, insurance, inspection findings and recalls, each with source and as-of date. Also returns the link where a person can start the full paid report. Countries: nl, gb, il, is, dk.

Parametersplaterequiredcountryrequiredlanguage

model_inspection_stats

Inspection statistics for a car model

Model-wide periodic inspection statistics (how often a make and model fails or gets findings), with source, as-of date and the citation line to use. Not about one specific car: for that use vehicle_check.

Parametersbrandrequiredmodelrequiredcountryrequiredlanguage

Version history

2
  1. v0.1.1LatestOct 19, 2026
  2. v0.1.0Oct 18, 2026

Score

90% of the applicable checks met

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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Plateop integrations