UK Open Data MCP Server avatar

UK Open Data MCP Server

Pricing

from $3.00 / 1,000 read operations

Go to Apify Store
UK Open Data MCP Server

UK Open Data MCP Server

UK open data MCP server for Claude, ChatGPT, Cursor and other AI agents. Police-recorded crime near a point (approximate locations) and stop and search from data.police.uk, plus MPs, bills and Commons votes from UK Parliament open data. 14 read-only tools, deep research ready.

Pricing

from $3.00 / 1,000 read operations

Rating

0.0

(0)

Developer

MrBridge

MrBridge

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

19 days ago

Last modified

Categories

Features

Limited permissionsSingle-tenantServer interface

Share

📊 UK Open Data MCP Server

UK Open Data MCP Server is an MCP server that gives Claude, ChatGPT, Cursor, VS Code and other AI agents two sets of UK open data: police-recorded crime, outcomes, stop and search and neighbourhood policing from data.police.uk, and MPs, peers, bills and House of Commons votes from the UK Parliament APIs. It has 14 read-only tools, including the search and fetch pair that ChatGPT deep research uses.

Ask Claude "who is the MP for SW1A 2AA, and how did they vote in the last Commons divisions?". It calls uk_search_members with the postcode, then uk_search_commons_divisions for that member, and answers with the name, party, constituency and a vote-by-vote list with the result of each division. Every answer carries the licence statement of its source, ready to quote.

Quick start

  1. Copy your API token from Apify Console > Settings > API & Integrations.
  2. Add https://mrbridge--uk-open-data-mcp.apify.actor/mcp to your AI client with the header Authorization: Bearer <token>. The Connect section below has a ready-made snippet for each client.
  3. Ask a question such as "which bills about renting are before Parliament, and at what stage?"

What this server exposes

This server wraps two official UK open data sources: data.police.uk (street-level crime, crime outcomes, stop and search, neighbourhood policing teams and police forces for England, Wales and Northern Ireland) and three UK Parliament APIs (Members, Bills and Commons Votes). It exposes 12 read-only tools with the uk_ prefix, plus the search and fetch pair that ChatGPT deep research expects, over members, bills and House of Commons votes. No upstream needs a key or an account, and the server stores nothing about its callers beyond a shared response cache. Police tools take WGS84 coordinates, so a postcode has to be geocoded first, while the member search takes the postcode directly.

Tools

ToolWhat it answersBilled event
uk_get_street_crimesGet street-level crimes around a point or inside an areatool-read
uk_get_crime_outcomesGet the outcomes of one crimetool-read
uk_get_stop_and_searchGet stop and search records around a point or inside an areatool-read
uk_get_neighbourhoodGet the neighbourhood policing team of a locationtool-action
uk_get_police_forceList police forces or get one forcetool-read
uk_get_police_data_availabilityGet the months, categories and forces covered by police datatool-read
uk_search_membersSearch MPs and members of the House of Lordstool-read
uk_get_memberGet one MP or peertool-action
uk_search_billsSearch UK Parliament billstool-read
uk_get_billGet one UK Parliament billtool-read
uk_search_commons_divisionsSearch House of Commons votestool-read
uk_get_commons_divisionGet one House of Commons votetool-read
searchSearchtool-read
fetchFetchtool-read

uk_get_street_crimes: Get street-level crimes around a point or inside an area

Use this when you need the crimes and anti-social behaviour recorded by the police in England, Wales or Northern Ireland within 1 mile of a point, or inside a custom polygon, for one month: totals by category and a page of records with their approximate street and latest outcome. Do not use for stop and search (uk_get_stop_and_search), the case history of one crime (uk_get_crime_outcomes) or turning a postcode into coordinates (use a geocoding tool first). Parameters: latitude and longitude (e.g. 52.629729 and -1.131592) or polygon (3 to 50 [lat, lng] pairs), month (YYYY-MM, default the latest published month), category (slug from uk_get_police_data_availability, e.g. "burglary", default "all-crime"), limit (1 to 100, default 20), offset, response_format ("detailed" adds outcome counts, location type, street id and context). Locations are anonymised snap points, never exact addresses.

ParameterTypeRequiredExample
latitudenumberno52.629729
longitudenumberno-1.131592
polygonarray of arrayno[[52.268,0.543],[52.794,0.238],[52.13,0.478]]
monthstringno"2026-03"
categorystringno"burglary"
limitintegerno20
offsetintegerno0
response_format"concise" or "detailed"no"concise"

Returns { area, month, category, total, records_without_location, by_category[], by_outcome[], crimes[], pagination, attribution }. Upstream: data.police.uk. Cache: daily (1 day). Read-only.

uk_get_crime_outcomes: Get the outcomes of one crime

Use this when you need the case history of one crime published by data.police.uk: every police and court outcome recorded for it, in date order, with the crime category, month and approximate street. Do not use for finding crimes in an area (uk_get_street_crimes) or for anti-social behaviour incidents, which have no crime id and no outcomes. Parameters: crime_id (the 64-character crime_id of a uk_get_street_crimes record, e.g. "e11dade0a92a912d12329b9b2abb856ac9520434ad6845c30f503e9901d140f1"), response_format ("detailed" adds location type and context). The Police Service of Northern Ireland and the British Transport Police publish no outcomes.

ParameterTypeRequiredExample
crime_idstringyes"e11dade0a92a912d12329b9b2abb856ac9520434ad6845c30f503e9901d140f1"
response_format"concise" or "detailed"no"concise"

Returns { crime, outcomes[], latest_outcome, attribution }. Upstream: data.police.uk. Cache: daily (1 day). Read-only.

uk_get_stop_and_search: Get stop and search records around a point or inside an area

Use this when you need police stop and search activity in England and Wales within 1 mile of a point or inside a polygon for one month: totals by object of search, outcome, search type, legislation, age range, gender and officer-defined ethnicity, plus a page of records. Do not use for crimes (uk_get_street_crimes) or for a force that did not publish stop and search that month (uk_get_police_data_availability lists the publishing forces). Parameters: latitude and longitude (e.g. 52.629729 and -1.131592) or polygon (3 to 50 [lat, lng] pairs), month (YYYY-MM, default the latest published month), limit (1 to 50, default 20), offset, response_format ("detailed" adds per-record age range, gender, both ethnicities, legislation, clothing removal and operation, and the self-defined ethnicity counts). Locations are anonymised and ages are published as ranges.

ParameterTypeRequiredExample
latitudenumberno52.629729
longitudenumberno-1.131592
polygonarray of arrayno[[52.268,0.543],[52.794,0.238],[52.13,0.478]]
monthstringno"2026-03"
limitintegerno20
offsetintegerno0
response_format"concise" or "detailed"no"concise"

Returns { area, month, total, records_without_location, by_object_of_search[], by_outcome[], by_type[], by_legislation[], by_age_range[], by_gender[], by_officer_defined_ethnicity[], by_self_defined_ethnicity[], records[], pagination, attribution }. Upstream: data.police.uk. Cache: daily (1 day). Read-only.

uk_get_neighbourhood: Get the neighbourhood policing team of a location

Use this when you need the neighbourhood policing team that covers a point in England, Wales or Northern Ireland, or a known team: its name, description, published contact channels, police stations, force contact details and current local priorities. Do not use for crime figures (uk_get_street_crimes) or the list of police forces (uk_get_police_force). Parameters: latitude and longitude (e.g. 51.500617 and -0.124629), or force_id with neighbourhood_id (e.g. "leicestershire" and "NC04"), include_priorities (default true), response_format ("concise" keeps the 5 latest priorities trimmed to 400 and 600 characters, "detailed" the 10 latest trimmed to 1,000 and 2,500 characters, plus links). Names of individual officers are withheld, also inside free text.

ParameterTypeRequiredExample
latitudenumberno52.629729
longitudenumberno-1.131592
force_idstringno"leicestershire"
neighbourhood_idstringno"NC04"
include_prioritiesbooleannotrue
response_format"concise" or "detailed"no"concise"

Returns { located_from, force, neighbourhood, priorities[], priorities_total, attribution }. Upstream: data.police.uk. Cache: daily (1 day). Read-only.

uk_get_police_force: List police forces or get one force

Use this when you need the list of police forces that publish data on data.police.uk (id and name), or the public contact details of one force: website, telephone number, description and social media channels. Do not use for a local neighbourhood team (uk_get_neighbourhood) or for crime data (uk_get_street_crimes). Parameters: force_id (optional, force id or name, e.g. "leicestershire" or "Avon and Somerset", omit it to list every force), response_format ("detailed" keeps the full description).

ParameterTypeRequiredExample
force_idstringno"leicestershire"
response_format"concise" or "detailed"no"concise"

Returns { count, forces[], force, attribution }. Upstream: data.police.uk. Cache: reference (30 days). Read-only.

uk_get_police_data_availability: Get the months, categories and forces covered by police data

Use this when you need to know which months of police data exist, the latest published month, the crime category slugs accepted by uk_get_street_crimes, or which forces published stop and search data for a month. Do not use for the data itself (uk_get_street_crimes, uk_get_stop_and_search) or for force contact details (uk_get_police_force). Parameters: month (optional YYYY-MM, e.g. "2026-03", default the latest month), response_format ("detailed" adds the stop and search force list of every month).

ParameterTypeRequiredExample
monthstringno"2026-03"
response_format"concise" or "detailed"no"concise"

Returns { latest_month, first_month, last_updated, months_available, months[], selected, attribution }. Upstream: data.police.uk. Cache: daily (1 day). Read-only.

uk_search_members: Search MPs and members of the House of Lords

Use this when you need to find a UK MP or peer by name, by postcode or constituency (who is the MP for a postcode), or to list the members of one House, with party, constituency and member id. Do not use for the full profile and office contact details of one member (uk_get_member) or for how a member voted (uk_search_commons_divisions with member_id). Parameters: name (e.g. "Starmer"), location (full postcode, outward code or constituency name, e.g. "SW1A 1AA"), house ("commons" or "lords"), at least one of the three, current_only (default true, false drops the sitting-members filter), limit (1 to 20, default 10), offset, response_format ("detailed" adds full title, gender, end of membership and status).

ParameterTypeRequiredExample
namestringno"Starmer"
locationstringno"SW1A 1AA"
house"commons" or "lords"no"commons"
current_onlybooleannotrue
limitintegerno10
offsetintegerno0
response_format"concise" or "detailed"no"concise"

Returns { members[], result_context, pagination, attribution }. Upstream: UK Parliament Members API. Cache: daily (1 day). Read-only.

uk_get_member: Get one MP or peer

Use this when you need the profile of one UK MP or member of the House of Lords by member id: party, House, constituency or title, membership dates, the published parliamentary and constituency office contact details, and the official synopsis. Do not use for finding a member id (uk_search_members) or for voting records (uk_search_commons_divisions with member_id). Parameters: member_id (e.g. 172), include_contact (default true), include_synopsis (default true), response_format ("detailed" keeps up to 4,000 characters of synopsis and adds full title, gender and status).

ParameterTypeRequiredExample
member_idintegeryes172
include_contactbooleannotrue
include_synopsisbooleannotrue
response_format"concise" or "detailed"no"concise"

Returns { member, contact[], synopsis, attribution }. Upstream: UK Parliament Members API. Cache: daily (1 day). Read-only.

uk_search_bills: Search UK Parliament bills

Use this when you need to find bills before the UK Parliament (or past ones) by words of their title, House, session or sponsoring member, with their current stage and status. Do not use for the sponsors, summary and full stage history of one bill (uk_get_bill) or for votes (uk_search_commons_divisions). Parameters: search_term (e.g. "renters"), session_id (Bills API session number, e.g. 39), current_house and originating_house ("commons" or "lords"), sponsor_member_id (e.g. 4514), sort ("updated_desc" default, "updated_asc", "title_asc", "title_desc"), limit (1 to 20, default 10), offset, response_format ("detailed" adds former title, bill type and session ids).

ParameterTypeRequiredExample
search_termstringno"renters"
session_idintegerno39
current_house"commons" or "lords"no"commons"
originating_house"commons" or "lords"no"commons"
sponsor_member_idintegerno4514
sort"updated_desc" or "updated_asc" or "title_asc" or "title_desc"no"updated_desc"
limitintegerno10
offsetintegerno0
response_format"concise" or "detailed"no"concise"

Returns { bills[], pagination, attribution }. Upstream: UK Parliament Bills API. Cache: intraday (5 minutes). Read-only.

uk_get_bill: Get one UK Parliament bill

Use this when you need one bill by id: long title, summary, status (act, defeated, withdrawn), current stage, sponsors with party and constituency, and the stages it went through with their sitting dates. Do not use for finding a bill id (uk_search_bills) or for the votes held on it (uk_search_commons_divisions with a search_term). Parameters: bill_id (e.g. 3737), include_stages (default true), response_format ("detailed" keeps up to 4,000 characters of summary and adds promoters, petitioning period and every sitting date).

ParameterTypeRequiredExample
bill_idintegeryes3737
include_stagesbooleannotrue
response_format"concise" or "detailed"no"concise"

Returns { bill, stages[], stages_total, attribution }. Upstream: UK Parliament Bills API. Cache: intraday (5 minutes). Read-only.

uk_search_commons_divisions: Search House of Commons votes

Use this when you need House of Commons divisions (recorded votes) by words of their title, date range or division number, with the aye and no counts and the result, or how one MP voted in each of them. Do not use for the party breakdown and the full list of who voted aye or no in one division (uk_get_commons_division) or for House of Lords votes (not covered). Parameters: search_term (e.g. "Budget"), member_id (adds how this MP voted, uk_search_members gives the id, e.g. 172), start_date and end_date (YYYY-MM-DD, e.g. "2026-03-01"), division_number (the number printed in Hansard, unique within a session), limit (1 to 25, default 10), offset, response_format ("detailed" adds deferred flag, friendly title, EVEL and double-majority counts).

ParameterTypeRequiredExample
search_termstringno"Budget"
member_idintegerno172
start_datestringno"2026-03-01"
end_datestringno"2026-03-31"
division_numberintegerno123
limitintegerno10
offsetintegerno0
response_format"concise" or "detailed"no"concise"

Returns { member_id, divisions[], pagination, attribution }. Upstream: UK Parliament Commons Votes API. Cache: intraday (5 minutes). Read-only.

uk_get_commons_division: Get one House of Commons vote

Use this when you need the result of one House of Commons division by id: aye and no counts, tellers, how each party voted, and optionally the list of MPs who voted aye or no, filterable by party. Do not use for finding a division id (uk_search_commons_divisions) or for one MP voting record across divisions (uk_search_commons_divisions with member_id). Parameters: division_id (e.g. 1851), member_votes ("none" default, "ayes", "noes" or "all"), party (e.g. "Labour", filters the member list), limit (1 to 250, default 100), offset, response_format ("detailed" adds proxy votes, EVEL and double-majority fields).

ParameterTypeRequiredExample
division_idintegeryes1851
member_votes"none" or "ayes" or "noes" or "all"no"ayes"
partystringno"Labour"
limitintegerno100
offsetintegerno0
response_format"concise" or "detailed"no"concise"

Returns { division, party_breakdown[], tellers, no_vote_recorded_count, member_votes[], pagination, attribution }. Upstream: UK Parliament Commons Votes API. Cache: daily (1 day). Read-only.

Use this when ChatGPT needs to find UK Parliament records by keyword: sitting MPs and peers by name, bills by title words and House of Commons votes by title words. Do not use for police data (uk_get_street_crimes) or for paging through long result lists (uk_search_members, uk_search_bills, uk_search_commons_divisions). Parameter query (string), e.g. "renters" or "Starmer". Returns up to 5 members, 5 bills and 5 divisions.

ParameterTypeRequiredExample
querystringyes"renters"

Returns { results[], notices[] }. Upstream: UK Parliament Members API, UK Parliament Bills API, UK Parliament Commons Votes API. Cache: daily (1 day). Read-only.

fetch: Fetch

Use this when ChatGPT needs the full text of one record returned by search: a member profile with published office contacts, a bill with its status, sponsors and stages, or a Commons vote with its party breakdown. Do not use for ids that did not come from search. Parameter id (from search), e.g. "member-172", "bill-3737" or "division-1851".

ParameterTypeRequiredExample
idstringyes"member-172"

Returns { id, title, text, url, metadata, notices[] }. Upstream: UK Parliament Members API, UK Parliament Bills API, UK Parliament Commons Votes API. Cache: daily (1 day). Read-only.

Connect

Endpoint (Streamable HTTP): https://mrbridge--uk-open-data-mcp.apify.actor/mcp

Every client authenticates with your Apify API token, found in Apify Console > Settings > API & Integrations. Clients that support custom headers send it as Authorization: Bearer <token>. The others use the ?token= URL variant, which must be treated as a secret: keep it out of commits, screenshots and shared logs.

Claude Code

$claude mcp add --transport http uk-open-data "https://mrbridge--uk-open-data-mcp.apify.actor/mcp" --header "Authorization: Bearer ${APIFY_TOKEN}"

Cursor, VS Code and other JSON configurations

{
"mcpServers": {
"uk-open-data": {
"type": "http",
"url": "https://mrbridge--uk-open-data-mcp.apify.actor/mcp",
"headers": {
"Authorization": "Bearer ${APIFY_TOKEN}"
}
}
}
}

claude.ai and Claude Desktop

Add a custom connector with the URL https://mrbridge--uk-open-data-mcp.apify.actor/mcp?token=YOUR_APIFY_TOKEN and no authentication. Prefilled link (replace the token placeholder before saving): add UK Open Data MCP Server to Claude.

ChatGPT (developer mode)

Settings > Apps > Create, URL https://mrbridge--uk-open-data-mcp.apify.actor/mcp?token=YOUR_APIFY_TOKEN, authentication "No authentication". ChatGPT snapshots the tool list: after a server update, an admin has to click Refresh on the app.

OpenAI Responses API

{
"type": "mcp",
"server_label": "uk_open_data",
"server_url": "https://mrbridge--uk-open-data-mcp.apify.actor/mcp",
"headers": {
"Authorization": "Bearer YOUR_APIFY_TOKEN"
},
"require_approval": "never"
}

Add allowed_tools to restrict the tool list. Tool calls must finish within about 60 seconds on this API, and every tool of this server answers in under 50 seconds.

Anthropic Messages API

{
"mcp_servers": [
{
"type": "url",
"url": "https://mrbridge--uk-open-data-mcp.apify.actor/mcp",
"name": "uk-open-data",
"authorization_token": "YOUR_APIFY_TOKEN"
}
],
"tools": [
{
"type": "mcp_toolset",
"mcp_server_name": "uk-open-data"
}
]
}

Send the beta header anthropic-beta: mcp-client-2025-11-20.

One-click OAuth alternative

https://mcp.apify.com/?tools=mrbridge/uk-open-data-mcp connects through Apify OAuth without a token. It exposes the Actor as a single tool rather than the granular tools listed above.

Cost control

Each Standby run has a spending limit (maxTotalChargeUsd). When a call uses the last of it, the result is still returned, and later calls in that run answer CHARGE_LIMIT_REACHED until the limit is raised.

Why use UK Open Data MCP Server

  • Policing and Parliament in one server. Crime, outcomes, stop and search, neighbourhood teams, MPs, peers, bills and Commons votes, all under open licences.
  • From postcode to voting record. Who the MP is, their published office contacts and how they voted, in three calls.
  • Bills in full. Current stage, sponsors with party and constituency, and every stage with its sitting dates.
  • Votes with context. Each Commons division with aye and no counts, a party breakdown and the MPs on each side.
  • Totals you can read. Crime counts by category for a 1-mile radius or a custom area, and stop and search totals by outcome and legislation.
  • ChatGPT deep research ready. search and fetch over members, bills and Commons votes, each result linked to its parliament.uk page.

Pricing (Pay-per-Event)

UK Open Data MCP Server uses pay-per-event pricing. Each successful call is one tool-read event at $0.005, or one tool-action event at $0.01 for the two detailed tools (uk_get_neighbourhood and uk_get_member), so 1,000 reads cost $5 in events. These are the FREE plan prices, and Apify plan discounts lower them. Apify also bills its standard apify-actor-start event when a Standby run starts, and you pay the platform usage of your own Standby run on top of the events, as explained below. Calls that end in an error carry no event charge. See the Pricing tab for the price on your Apify plan.

EventCharged whenPrice
apify-actor-startrun start (platform default)see the Store page
tool-read (primary event)each successful read tool callsee the Store page
tool-actioneach successful call of a detailed or computed toolsee the Store page

Never charged: initialize, tools/list, pings, readiness probes, and any call that ends in an error (invalid input, not found, upstream failure, timeout, spending limit).

Platform usage comes on top of these events. This server runs in Apify Standby mode, and you also pay the platform usage of your own Standby run, billed to your Apify account like any other run: the memory set for the Standby run, for as long as the server is up, idle time included, until the run stops at its idle timeout. The Apify pay-per-event documentation says so: "For runs in Standby mode, users always pay the platform usage costs in addition to the event charges."

Limits, caveats and attribution

  • Attribution. Every answer carries an attribution block with the licence statement the source requires. Police data: "Contains public sector information licensed under the Open Government Licence v3.0." Parliament data: "Contains Parliamentary information licensed under the Open Parliament Licence v3.0." Keep the statement when you reuse the data. The server is not affiliated with or endorsed by data.police.uk, the Home Office, any police force or the UK Parliament.
  • Approximate locations. data.police.uk replaces the location of every crime and every stop and search with the nearest anonymous map point (the centre of a street, a park, a station), never the exact place. Every location in an answer is marked approximate: true. When the nearest map point is more than 20 km away the publisher removes the coordinates, and the record comes back with location: null.
  • Coverage. Police data covers England, Wales and Northern Ireland. Scotland only appears through British Transport Police records, so crime levels there look much lower than they are. Data is monthly, published about two months after the fact, and the API keeps roughly the last three years. Stop and search is published by some forces only, and uk_get_police_data_availability lists them month by month. The Police Service of Northern Ireland and the British Transport Police publish no outcomes.
  • Areas. A point query covers a 1 mile radius. A polygon is limited to 50 points and half a degree on each side, because data.police.uk refuses areas with more than 10,000 crimes.
  • What is left out on purpose. Names of individual police officers (the officer endpoints are not used, and a name that follows a police rank in published free text is replaced with "[name withheld]"), the identifier of a suspect in outcome records, portraits and thumbnails of members (Parliamentary photographs are outside the Open Parliament Licence) and the contact block of private bill agents. Member data is limited to what Parliament publishes about the public role, and gender is only shown in detailed mode.
  • Computed fields. The result of a Commons division and the party breakdown are computed by this server from the published counts and member votes. Lords votes are not covered.
  • Rate limits. data.police.uk allows 15 requests per second with bursts of 30, and this server keeps to half. The Parliament APIs document no limit, and the server keeps to 5 requests per second per host. Heavy use can still meet UPSTREAM_RATE_LIMITED.
  • Freshness. Police answers are cached for a day (the list of published months for an hour), the force list for 30 days, members for a day, bills and vote searches for 5 minutes, and a single division for a day.

Data terms

By using this server you agree to use the data it returns in line with the licence of each source, and to pass the same obligations on to anyone you share the data with.

  • Police data: Open Government Licence v3.0. Keep the attribution statement, do not suggest official status or endorsement, and remember that the licence does not cover personal data.
  • Parliament data: Open Parliament Licence v3.0. Keep the attribution statement, do not suggest endorsement, and do not use the Crowned Portcullis or the Royal Arms. The licence does not cover personal data either: names and contact details of members are published for their public role, and any further use has to respect UK data protection law.

The fee for this server pays for the service (hosting, caching, normalisation), not for a licence on the data.

Use cases

  • Constituent services and civic tech. "Who is my MP, and how do I contact their constituency office?"
  • Political journalism. "How did each party vote on the second reading of this bill, and who voted no in each party?"
  • Public affairs monitoring. Track bills by title words, House or session, with their current stage and status.
  • Local area research. "Which crime categories were recorded within a mile of this point last month, and what happened to the cases?"
  • Policing transparency studies. Stop and search totals by outcome and legislation, for an area and a month.
  • Teaching citizenship. Follow a real bill from first reading to Royal Assent, or explain how a division works.

Crime locations are approximate by design: the publisher moves each record to the nearest anonymous map point. Police data covers England, Wales and Northern Ireland and runs about two months behind.

More company and economic data tools

FAQ

Why is the first call slower?

The server runs in Apify Standby mode. When no request comes in for a while, the run stops at its idle timeout, and the next call starts a new one. That cold start took about 4 seconds in the last platform test. Calls made while the server is warm skip the delay.

How current is the police data?

It is published monthly, about two months after the fact, and the source keeps roughly the last three years. uk_get_police_data_availability tells you the latest month and which forces published stop and search data for it.

Does it cover Scotland and the House of Lords?

Police data covers England, Wales and Northern Ireland, and Scotland only through British Transport Police records. Members cover both Houses, but votes cover the House of Commons only.

Can I search crime by postcode?

The police tools take coordinates, so geocode the postcode first. The member search takes a postcode directly.

Why can a bill search take a while?

The bills source answers keyword searches slowly. A search took up to about 20 seconds in tests, and repeated searches come from the cache.

Is this an official government or Parliament service?

No. It is an independent server built on open data, not affiliated with or endorsed by data.police.uk, the Home Office, any police force or the UK Parliament.

Your feedback

Found a bug or a wrong answer? Open an issue on the Issues tab. UK Open Data MCP Server is built by MrBridge. More servers are listed in the MCP server catalogue, and more tools and data studies are at mr-bridge.com.

Changelog

  • 0.1.3: Output, dataset and key-value store schemas, as Apify asks for publication: the Output tab of a run started from the Console shows the connection details and one row per tool.
  • 0.1.2: the Input tab shows the endpoint and how to connect an AI client, and a run started from the Console outputs the connection details and the tool list
  • 0.1.1: pricing events tool-read and tool-action
  • 0.1.0: initial build (private, unpublished)