# UK Data: GB road traffic counts (DfT) (remote · ukdata.reliness.co.uk)

Great Britain road traffic counts from the DfT: count points, vehicles per day by type, hourly

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `ukdata.reliness.co.uk`: 75/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-reliness-uk-roads-traffic/mcp-uk-roads-traffic.md), [page](https://verifymcp.io/servers/uk-co-reliness-uk-roads-traffic/mcp-uk-roads-traffic)

## Channel facts

- Endpoint: `https://ukdata.reliness.co.uk/mcp/uk-roads-traffic`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.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-11-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1067 tokens (~177/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 UK Data: GB road traffic counts (DfT) MCP server?

UK Data: GB road traffic counts (DfT) is a hosted endpoint at https://ukdata.reliness.co.uk/mcp/uk-roads-traffic, 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 uk-co-reliness-uk-roads-traffic 'https://ukdata.reliness.co.uk/mcp/uk-roads-traffic'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-reliness-uk-roads-traffic": {
      "url": "https://ukdata.reliness.co.uk/mcp/uk-roads-traffic"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-reliness-uk-roads-traffic": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/uk-roads-traffic"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-co-reliness-uk-roads-traffic]
url = "https://ukdata.reliness.co.uk/mcp/uk-roads-traffic"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-reliness-uk-roads-traffic": {
      "type": "remote",
      "url": "https://ukdata.reliness.co.uk/mcp/uk-roads-traffic",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-reliness-uk-roads-traffic --url 'https://ukdata.reliness.co.uk/mcp/uk-roads-traffic' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-reliness-uk-roads-traffic:
    url: "https://ukdata.reliness.co.uk/mcp/uk-roads-traffic"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-reliness-uk-roads-traffic": {
      "Transport": "http",
      "Url": "https://ukdata.reliness.co.uk/mcp/uk-roads-traffic"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-reliness-uk-roads-traffic -t streamable-http -u 'https://ukdata.reliness.co.uk/mcp/uk-roads-traffic'
```

### Other

```json
{
  "mcpServers": {
    "uk-co-reliness-uk-roads-traffic": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/uk-roads-traffic"
    }
  }
}
```

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-11-20 (score 75, +1)

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

### 2026-11-18 (score 74, +1)

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

### 2026-11-15 (score 73, +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-11-13 (score 72, +1)

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

### 2026-11-11 (score 71, +1)

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

### 2026-11-09 (score 70, +1)

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

### 2026-11-08 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 69)

First indexed and scored.

## MCP tools (6)

### `road_traffic_flow_at_point` (~227 tokens)

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)

Input parameters:

- `count_point_id` (string): integer, required, DfT count point id (from traffic_count_points_on_road or traffic_count_points_in_council)
- `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

### `road_traffic_hourly_counts` (~185 tokens)

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)

Input parameters:

- `count_point_id` (string): integer, required, DfT count point id
- `direction` (string): string, optional, N, S, E, W or C (combined); default all directions
- `year` (string): integer, optional, survey year; default is the most recent year with a manual count

### `local_authority_traffic_totals` (~215 tokens)

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)

Input parameters:

- `local_authority_id` (string): integer, required, DfT local authority id (from traffic_local_authority_find, e.g. Leeds is 63)
- `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_traffic_by_vehicle_type` (~212 tokens)

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)

Input parameters:

- `region_id` (string): integer, required, DfT region id 1-11 (from traffic_regions_list, e.g. 7 East of England, 3 Scotland, 6 London)
- `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

### `traffic_local_authority_find` (~146 tokens)

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)

Input parameters:

- `name` (string): string, required, council name or part of it, or an ONS code like E08000035

### `traffic_regions_list` (~82 tokens)

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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-reliness-uk-roads-traffic/mcp-uk-roads-traffic#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 72
- 2026-11-13: 72
- 2026-11-12: 71
- 2026-11-11: 71
- 2026-11-10: 70
- 2026-11-09: 70
- 2026-11-08: 69
- 2026-11-07: 69

## Common questions

### What is the UK Data: GB road traffic counts (DfT) MCP server?

UK Data: GB road traffic counts (DfT) is an MCP server listed in the public MCP registry as uk.co.reliness/uk-roads-traffic. Great Britain road traffic counts from the DfT: count points, vehicles per day by type, hourly. This page covers its hosted endpoint (https://ukdata.reliness.co.uk/mcp/uk-roads-traffic).

### Is the UK Data: GB road traffic counts (DfT) MCP server safe to use?

UK Data: GB road traffic counts (DfT) scores 75 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 UK Data: GB road traffic counts (DfT) MCP server expose?

UK Data: GB road traffic counts (DfT) exposes 6 tools: road_traffic_flow_at_point, road_traffic_hourly_counts, local_authority_traffic_totals, region_traffic_by_vehicle_type, traffic_local_authority_find, traffic_regions_list. Their descriptions and schemas cost roughly 1,067 tokens of context every time the server is loaded.

### Does the UK Data: GB road traffic counts (DfT) MCP server require authentication?

No. We connected to UK Data: GB road traffic counts (DfT) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the UK Data: GB road traffic counts (DfT) MCP server still maintained?

UK Data: GB road traffic counts (DfT) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the UK Data: GB road traffic counts (DfT) MCP server?

VerifyMCP ran 13 checks on UK Data: GB road traffic counts (DfT), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ukdata.reliness.co.uk/mcp/uk-roads-traffic
- Website: https://ukdata.reliness.co.uk/
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-reliness-uk-roads-traffic/mcp-uk-roads-traffic.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-reliness-uk-roads-traffic/mcp-uk-roads-traffic/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uk-co-reliness-uk-roads-traffic/mcp-uk-roads-traffic.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-reliness-uk-roads-traffic/mcp-uk-roads-traffic
