Integration

DVLA Vehicle Enquiry Service integration

The DVLA Vehicle Enquiry Service (VES) looks up a vehicle registered in Great Britain by its registration number and returns what the Driver and Vehicle Licensing Agency holds about it: make, colour, fuel type, engine capacity, CO2 emissions, year of manufacture, first registration month, vehicle tax status and due date, MOT status and expiry date, export marking and the date of the last V5C logbook. Useful to check a vehicle before a purchase, enrich a fleet or insurance record, or verify that a car is taxed and has a valid MOT. It returns no keeper or owner details. Authentication is an API key issued by the DVLA on registration (one key per company), sent in the x-api-key header; DVLA has paused new registrations during system upgrades. Requests are throttled per second, per client usage plan and across all clients; over the limit the API answers 429.

Connect DVLA Vehicle Enquiry Service How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in DVLA Vehicle Enquiry Service.Built from the 1 DVLA Vehicle Enquiry Service tool below, on the connection you add once.

What you can do with DVLA Vehicle Enquiry Service

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

get_vehicle_detailsGet vehicle detailsPOSTLook up a GB vehicle's DVLA record by registration number

Use DVLA Vehicle Enquiry Service from Claude Code, Cursor or Codex

Connect DVLA Vehicle Enquiry Service in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its DVLA Vehicle Enquiry Service operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect DVLA Vehicle Enquiry Service

Create your workspace
Sign up free. Nothing to install.
Connect DVLA Vehicle Enquiry Service once
Add your DVLA Vehicle Enquiry Service connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.