Great Britain road traffic counts from the DfT: count points, vehicles per day by type, hourly
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Optional. Bearer <key> for more than the free daily allowance; free key from POST https://ukdata.reliness.co.uk/keys
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Gives the total distance driven on all roads in one GB council area each year, in million vehicle miles (and vehicle km), for all motor vehicles and for cars and taxis, plus the area's road length, newest year first. Answers "how much traffic is there in Leeds and is it growing" for council officers, net-zero and carbon plans, and consultants comparing areas. Minor-road traffic is a DfT estimate; this endpoint does not split vans, HGVs or buses (use region_traffic_by_vehicle_type for that at region level). (cost: 1 credit)
integer, optional, a single year; default is the most recent years
integer, optional, how many recent years when year is not given, 1-40, default 10
integer, required, DfT local authority id (from traffic_local_authority_find, e.g. Leeds is 63)
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http uk-roads-traffic https://ukdata.reliness.co.uk/mcp/uk-roads-traffic
Headers
Authorization (optional, not in the config above): Optional. Bearer <key> for more than the free daily allowance; free key from POST https://ukdata.reliness.co.uk/keysGives the total distance driven on all roads in one GB council area each year, in million vehicle miles (and vehicle km), for all motor vehicles and for cars and taxis, plus the area's road length, newest year first. Answers "how much traffic is there in Leeds and is it growing" for council officers, net-zero and carbon plans, and consultants comparing areas. Minor-road traffic is a DfT estimate; this endpoint does not split vans, HGVs or buses (use region_traffic_by_vehicle_type for that at region level). (cost: 1 credit)
| Argument | Type | Description |
|---|---|---|
| year | string | integer, optional, a single year; default is the most recent years |
| years | string | integer, optional, how many recent years when year is not given, 1-40, default 10 |
| local_authority_id | string | integer, required, DfT local authority id (from traffic_local_authority_find, e.g. Leeds is 63) |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"year": {
"type": "string",
"description": "integer, optional, a single year; default is the most recent years"
},
"years": {
"type": "string",
"description": "integer, optional, how many recent years when year is not given, 1-40, default 10"
},
"local_authority_id": {
"type": "string",
"description": "integer, required, DfT local authority id (from traffic_local_authority_find, e.g. Leeds is 63)"
}
}
}Gives annual traffic in one GB region (English regions, Scotland or Wales) by vehicle type, in million vehicle miles: cars and taxis, vans, HGVs, buses and coaches, motorcycles and pedal cycles, plus road length, newest year first. Useful for market sizing (for example van or HGV traffic for fleet services), journalism and coursework. Regional totals only; for a single council use local_authority_traffic_totals, and for one road use road_traffic_flow_at_point. (cost: 1 credit)
| Argument | Type | Description |
|---|---|---|
| year | string | integer, optional, a single year; default is the most recent years |
| years | string | integer, optional, how many recent years when year is not given, 1-40, default 10 |
| region_id | string | integer, required, DfT region id 1-11 (from traffic_regions_list, e.g. 7 East of England, 3 Scotland, 6 London) |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"year": {
"type": "string",
"description": "integer, optional, a single year; default is the most recent years"
},
"years": {
"type": "string",
"description": "integer, optional, how many recent years when year is not given, 1-40, default 10"
},
"region_id": {
"type": "string",
"description": "integer, required, DfT region id 1-11 (from traffic_regions_list, e.g. 7 East of England, 3 Scotland, 6 London)"
}
}
}Gives average annual daily flow (AADF) at one DfT count point: the average number of vehicles passing per day over a year, both directions together, split into cars and taxis, vans, HGVs, buses, motorbikes and pedal cycles, newest year first. Answers "how many cars pass this site a day" and "is traffic on this road rising" for shop, billboard, EV charger or planning work. Some years are estimated by DfT rather than counted, and each row says which; it does not cover live traffic or congestion. (cost: 1 credit)
| Argument | Type | Description |
|---|---|---|
| year | string | integer, optional, a single year such as 2024; default is the most recent years |
| years | string | integer, optional, how many recent years to return when year is not given, 1-30, default 10 |
| count_point_id | string | integer, required, DfT count point id (from traffic_count_points_on_road or traffic_count_points_in_council) |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"year": {
"type": "string",
"description": "integer, optional, a single year such as 2024; default is the most recent years"
},
"years": {
"type": "string",
"description": "integer, optional, how many recent years to return when year is not given, 1-30, default 10"
},
"count_point_id": {
"type": "string",
"description": "integer, required, DfT count point id (from traffic_count_points_on_road or traffic_count_points_in_council)"
}
}
}Returns the hour-by-hour manual traffic counts DfT recorded at one count point on its survey day, by direction of travel, with each direction's busiest hour and 12-hour total. Answers peak-hour questions such as "how busy is this road at 8am" for transport consultants and planning statements. Counts cover one weekday between 07:00 and 19:00 in the survey year, not averages or night-time, and many points are only surveyed every few years. (cost: 1 credit)
| Argument | Type | Description |
|---|---|---|
| year | string | integer, optional, survey year; default is the most recent year with a manual count |
| direction | string | string, optional, N, S, E, W or C (combined); default all directions |
| count_point_id | string | integer, required, DfT count point id |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"year": {
"type": "string",
"description": "integer, optional, survey year; default is the most recent year with a manual count"
},
"direction": {
"type": "string",
"description": "string, optional, N, S, E, W or C (combined); default all directions"
},
"count_point_id": {
"type": "string",
"description": "integer, required, DfT count point id"
}
}
}Finds the DfT local authority id, ONS code and region for a council from its name (partial names work, e.g. "Leeds", "Bristol", "Kingston"), or from an ONS code such as E08000035. Use it before local_authority_traffic_totals or traffic_count_points_in_council. Covers Great Britain councils as DfT lists them, including some former councils kept for older years; it is not a postcode lookup. (cost: 1 credit)
| Argument | Type | Description |
|---|---|---|
| name | string | string, required, council name or part of it, or an ONS code like E08000035 |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"name": {
"type": "string",
"description": "string, required, council name or part of it, or an ONS code like E08000035"
}
}
}Lists the 11 Great Britain regions DfT uses for traffic statistics (the nine English regions, Scotland and Wales) with their DfT region ids, ONS codes and country. Use it to get the region_id for region_traffic_by_vehicle_type. Northern Ireland is not covered by DfT road traffic statistics. (cost: 1 credit)
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 6, 2026.