UK Data: England listed buildings
REMOTE · UKDATA.RELINESS.CO.UK
Historic England: listed buildings and grades, scheduled monuments, parks, gardens, battlefields
Available components
Last scanned (22 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1102 tokens (~157/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Nov 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://ukdata.reliness.co.uk/mcp/uk-heritage
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=reliness.co.uk | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | f1d4f4e9f24c919b0e13c306162294a4 |
| SANs: reliness.co.uk, ukdata.reliness.co.uk, *.ukdata.reliness.co.uk | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ukdata.reliness.co.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | DS published | 43876 | 8 | Verified |
| co.uk. | DS published | 11810 | 8 | Verified |
| reliness.co.uk. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ukdata.reliness.co.uk/mcp/uk-heritage | Verified | 200 | |
| http (plaintext) | http://ukdata.reliness.co.uk/mcp/uk-heritage | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
battlefield_search ~139
List or search England's registered historic battlefields (from Hastings-era sites to the Civil War): name with battle year, date registered, area in hectares, grid reference and official link. For history fans, schools and walkers asking where a battle was fought. Source: Historic England Register of Historic Battlefields. Covers only the registered sites in England, not every recorded battle. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | integer, optional, max results 1-100, default 25 |
| name | string | – | string, optional, part of the battlefield name, e.g. 'Barnet' (omit to list all) |
No output schema declared.
No examples provided.
historic_park_garden_search ~141
Search England's Register of Parks and Gardens of Special Historic Interest by name: grade, date registered, area in hectares and official link. For garden visitors, estate owners and planners (registration is a planning consideration). Source: Historic England National Heritage List for England. Name match only; covers registered landscapes, not every public park. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | integer, optional, max results 1-100, default 10 |
| name | string | – | string, required, part of the park or garden name, e.g. 'Kew' (case-insensitive, 2-100 chars) |
No output schema declared.
No examples provided.
listed_building_lookup ~118
Look up one listed building by its NHLE list entry number (the 7-digit reference used in conveyancing and planning papers): name, grade, listing and last-amended dates, grid reference and official link. Source: Historic England National Heritage List for England. Covers listed buildings only; a number belonging to a scheduled monument, park, battlefield or wreck returns found: false. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| list_entry | string | – | integer, required, NHLE list entry number, e.g. 1065833 |
No output schema declared.
No examples provided.
listed_building_search ~176
Search England's listed buildings by name and get list entry number, grade (I, II*, II), listing date, grid reference and the link to the official Historic England record. Useful for homebuyers, conveyancers, builders and planners asking 'is this building listed'. Source: Historic England National Heritage List for England. Matches the list entry name only (often the address or building name as written when listed), not street addresses generally; England only, and it does not cover conservation areas or local lists. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | integer, optional, max results 1-100, default 10 |
| name | string | – | string, required, part of the list entry name, e.g. 'TOWER BRIDGE' (case-insensitive, 2-100 chars) |
No output schema declared.
No examples provided.
protected_wreck_search ~177
List or search wrecks designated under the Protection of Wrecks Act 1973 in English waters: name, designation date, restricted area in hectares, position (lat/lon and grid reference) and official link. Diving on or interfering with a designated wreck inside its restricted area without a Historic England licence is an offence, so divers and boat users check here. Source: Historic England National Heritage List for England. Covers designated wrecks only (not all wrecks or military remains); the position is a reference point, not the restricted-area boundary. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | integer, optional, max results 1-100, default 25 |
| name | string | – | string, optional, part of the wreck name, e.g. 'Mary Rose' (omit to list all) |
No output schema declared.
No examples provided.
scheduled_monument_search ~164
Search England's scheduled monuments by name and get list entry number, date scheduled, area in hectares, grid reference and official link. Scheduling gives legal protection: works, and metal detecting, on a scheduled monument need consent. For landowners, detectorists, developers and walkers. Source: Historic England National Heritage List for England. Name match only; most archaeology is not scheduled, so no match does not mean a site is unprotected or unrecorded. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | integer, optional, max results 1-100, default 10 |
| name | string | – | string, required, part of the monument name, e.g. 'Stonehenge' (case-insensitive, 2-100 chars) |
No output schema declared.
No examples provided.
scheduled_monuments_near ~187
List scheduled monuments around a point in England, nearest first, with date scheduled, area and the official link. Answers 'are there any scheduled monuments on or near this land' for development checks and metal-detecting permission. Source: Historic England National Heritage List for England. Takes lat/lon; includes any monument whose mapped area overlaps the search square, with distance to its reference point rather than its edge. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number|string | – | number, required, latitude in decimal degrees (WGS84) |
| limit | string | – | integer, optional, max results 1-100, default 25 |
| lon | number|string | – | number, required, longitude in decimal degrees (WGS84) |
| radius_m | string | – | integer, optional, search radius in metres 10-5000, default 1000 |
No output schema declared.
No examples provided.
How do I install the UK Data: England listed buildings MCP server?
UK Data: England listed buildings is a hosted endpoint at https://ukdata.reliness.co.uk/mcp/uk-heritage, 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.
remote · ukdata.reliness.co.uk
claude mcp add --transport http uk-co-reliness-uk-heritage 'https://ukdata.reliness.co.uk/mcp/uk-heritage'
What is the UK Data: England listed buildings MCP server?
UK Data: England listed buildings is an MCP server listed in the public MCP registry as uk.co.reliness/uk-heritage. Historic England: listed buildings and grades, scheduled monuments, parks, gardens, battlefields. This page covers its hosted endpoint (https://ukdata.reliness.co.uk/mcp/uk-heritage).
Is the UK Data: England listed buildings MCP server safe to use?
UK Data: England listed buildings scores 76 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: England listed buildings MCP server expose?
UK Data: England listed buildings exposes 7 tools: listed_building_search, listed_building_lookup, scheduled_monument_search, scheduled_monuments_near, historic_park_garden_search, and 2 more. Their descriptions and schemas cost roughly 1,102 tokens of context every time the server is loaded.
Does the UK Data: England listed buildings MCP server require authentication?
No. We connected to UK Data: England listed buildings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the UK Data: England listed buildings MCP server still maintained?
UK Data: England listed buildings 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: England listed buildings MCP server?
VerifyMCP ran 13 checks on UK Data: England listed buildings, 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.