uk.postcodecontext/mcp
REMOTE · API.POSTCODECONTEXT.UK
UK location intelligence: Census, HMLR/RoS prices, EPC, IMD, schools & transit via x402
Available components
Last scanned (14 hours ago)
Scores higher than 59% 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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2060 tokens (~171/item across 12 items; 10 tools + 2 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 Management40
- Stability observed for 12 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
- Structured output schemas are declared (80% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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 (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 20 Nov 26 +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.
- 17 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.
- 15 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.
- 13 Nov 26 +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.
- 11 Nov 26 +1
- HTTPS: fail → unverified ▼ security
- 10 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 68
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://api.postcodecontext.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=postcodecontext.uk | CN=WE1,O=Google Trust Services,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 13b69682b0e2773813f3b452dc9f112a |
| SANs: postcodecontext.uk, api.postcodecontext.uk, *.api.postcodecontext.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 api.postcodecontext.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | DS published | 43876 | 8 | Verified |
| postcodecontext.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.postcodecontext.uk/mcp | Verified | 200 | |
| http (plaintext) | http://api.postcodecontext.uk/mcp | Inconclusive | 405 |
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 →
compare_postcodes Compare Great Britain Postcodes Side-by-Side ~229
Use when you need to directly contrast 2 to 5 Great Britain postcodes across affluence, safety, housing cost per m², broadband, and family suitability. Returns full profiles by default; use view="brief" (~80 tokens per postcode) to keep context compact alongside the comparison ranking. Do not use for single postcode inspection (use lookup_postcode) or bulk batches of >5 postcodes (use enrich_postcodes).
| Name | Type | Req | Description |
|---|---|---|---|
| postcodes | array | yes | List of 2 to 5 distinct Great Britain postcodes to compare side-by-side (e.g. ["SW1A 1AA", "BB7 3BB"]). Must contain at least 2 distinct postcodes in England, Scotland, or Wales. |
| view | string | – | View slice for returned postcode profiles: "full" (complete profile per postcode, default), "brief" (or "summary"/"ai", ~80 tokens per postcode, recommended to minimize context usage alongside compar… |
| Name | Type | Req | Description |
|---|---|---|---|
| _attribution | string | yes | – |
| _billing | object | – | – |
| comparison_synthesis | object | yes | – |
| postcodes | array | yes | – |
No examples provided.
enrich_postcodes Enrich Bulk Great Britain Postcodes Cohort ~276
Bulk demographic, economic, and spatial lookup for 1 to 50 Great Britain postcodes. Returns brief profile by default (~80 tokens per postcode) to prevent context blow-up; use view="full" when all 113 metrics are needed. Cost-effective for 6 to 50 postcodes ($0.050 flat fee). For 1 postcode use lookup_postcode ($0.005); for 2 to 5 postcodes use compare_postcodes ($0.010). Do not use when detailed side-by-side comparative rankings are required (use compare_postcodes).
| Name | Type | Req | Description |
|---|---|---|---|
| postcodes | array | yes | Array of 1 to 50 Great Britain postcodes to enrich. Cost-effective for 6 to 50 postcodes ($0.050 flat fee). For 1 postcode use lookup_postcode ($0.005); for 2 to 5 postcodes use compare_postcodes ($0… |
| view | string | – | View slice for each postcode in the batch results: "brief" (or "summary"/"ai", ~80 tokens per postcode, default for batch calls to prevent context blow-up), "full" (complete 113-metric dataset per po… |
| Name | Type | Req | Description |
|---|---|---|---|
| _attribution | string | yes | – |
| _billing | object | – | – |
| cohort_summary | object | yes | – |
| results | array | yes | – |
No examples provided.
get_data_attribution Get Data Provenance & Statutory Attribution Register ~115
$0.00 USDC reference tool (no payment or authentication required; subject to Terms of Service): Retrieve official statutory attribution statements, Crown copyright notices, Royal Mail Gridlink sublicence details, and Open Government Licence v3.0 metadata across all 19 contributing data providers (ONS, OS, Royal Mail, HM Land Registry, Registers of Scotland, MHCLG, Ofcom, Scottish Government, Welsh Government, DfE, CQC, PHS, NWSSP, DfT, ORR).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_data_dictionary Get Data Dictionary & Field Methodology ~142
$0.00 USDC reference tool (no payment or authentication required; subject to Terms of Service): Retrieve exact field specifications, mathematical calculation formulas, statistical scales, and data sources for any metric across Great Britain in the Postcode Context database.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Statistical domain category filter. Use "summary_for_ai" (default) for a compact token-efficient overview (~8 fields) for AI agents, or "all" for the complete 113-metric specification. |
| field | string | – | Optional specific field name to inspect (e.g. affluence_score_100, median_house_price_gbp, family_suitability_score_100). |
No output schema declared.
No examples provided.
get_demographics_and_deprivation Get Great Britain Demographics & Deprivation Profile ~147
Retrieve Census demographic breakdown (ONS Census 2021 / NRS Scotland Census 2022 income estimate, qualifications, tenure, employment, age) and statutory IMD deprivation deciles (IoD 2025, WIMD 2025, SIMD 2020 crime safety, education, living environment) for any Great Britain postcode. Covers England, Scotland, and Wales.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | Great Britain unit postcode to inspect for Census demographics and statutory IMD deprivation deciles (e.g. SW1A 1AA, BB7 3BB, EH1 1YZ, CF10 1EP). Space-optional, case-insensitive. |
| Name | Type | Req | Description |
|---|---|---|---|
| _attribution | string | yes | – |
| _billing | object | – | – |
| census_demographics | object | yes | – |
| confidence | string | – | – |
| deprivation_deciles | object | yes | – |
| landmark_context | object | – | – |
| location | object | yes | – |
| match_type | string | – | – |
| note | string | – | – |
| requested_postcode | string | – | – |
| resolved_district | string | – | – |
No examples provided.
get_postcode_ai_brief Get Great Britain Postcode AI Briefing (Low-Token) ~125
Retrieve an ultra-lightweight, token-efficient natural language briefing, affluence tier, and persona profile (~80 tokens) for fast autonomous agent decision-making across Great Britain. Covers England, Scotland, and Wales (excludes Northern Ireland BT postcodes).
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | Great Britain unit postcode to summarize (e.g. SW1A 1AA, BB7 3BB, EH1 1YZ, CF10 1EP). Space-optional, case-insensitive. Returns ~80 tokens of concise natural language context for LLM agents. |
| Name | Type | Req | Description |
|---|---|---|---|
| _attribution | string | yes | – |
| _billing | object | – | – |
| confidence | string | – | – |
| landmark_context | object | – | – |
| location | object | yes | – |
| match_type | string | – | – |
| note | string | – | – |
| requested_postcode | string | – | – |
| resolved_district | string | – | – |
| summary_for_ai | object | yes | – |
No examples provided.
get_property_and_energy_profile Get Great Britain Property & Energy Efficiency Profile ~139
Retrieve real estate valuation (HM Land Registry / Registers of Scotland median house price, price per sqm, 3yr sales volume), EPC energy efficiency (current/potential band, retrofit upside), and Ofcom gigabit broadband connectivity for any Great Britain postcode. Covers England, Scotland, and Wales (excludes Northern Ireland BT postcodes).
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | Great Britain unit postcode to inspect for real estate transactions, £/sqm, and EPC ratings (e.g. SW1A 1AA, BB7 3BB, EH1 1YZ, CF10 1EP). Space-optional, case-insensitive. |
| Name | Type | Req | Description |
|---|---|---|---|
| _attribution | string | yes | – |
| _billing | object | – | – |
| confidence | string | – | – |
| digital_infrastructure | object | yes | – |
| landmark_context | object | – | – |
| location | object | yes | – |
| match_type | string | – | – |
| note | string | – | – |
| property_and_energy | object | yes | – |
| requested_postcode | string | – | – |
| resolved_district | string | – | – |
No examples provided.
lookup_postcode Lookup Great Britain Postcode Intelligence Profile ~342
Use when you need demographic, property, EPC energy efficiency, broadband, or socio-economic context for a Great Britain unit postcode (England, Scotland, Wales). Returns full profile by default; use view="brief" (~80 tokens) for low-token, concise briefings when managing context budget. Do not use for non-GB postcodes (e.g. Northern Ireland BT) or when comparing multiple postcodes simultaneously (use compare_postcodes instead).
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | – | – | Optional domain(s) to exclude: "schools", "healthcare", "transit" as a comma-separated string (e.g. "schools, healthcare") or an array of strings (e.g. ["schools", "healthcare"]). Note: exclude only… |
| postcode | string | yes | Great Britain unit postcode to analyze (e.g. SW1A 1AA, BB7 3BB, M1 1AE, EH1 1YZ, CF10 1EP). Space-optional, case-insensitive. Covers England, Scotland, and Wales. |
| view | string | – | View slice to return: "full" (complete 113-metric profile, default), "brief" (or "summary"/"ai", ~80 tokens summary with AI affluence tier & persona, recommended for token efficiency), "property" (pr… |
| Name | Type | Req | Description |
|---|---|---|---|
| _attribution | string | – | – |
| _billing | object | – | – |
| census_demographics | object | – | – |
| confidence | string | – | – |
| deprivation_deciles | object | – | – |
| digital_infrastructure | object | – | – |
| healthcare_and_services | object | – | – |
| landmark_context | object | – | – |
| location | object | yes | – |
| match_type | string | – | – |
| note | string | – | – |
| property_and_energy | object | – | – |
| requested_postcode | string | – | – |
| resolved_district | string | – | – |
| schools_and_education | object | – | – |
| summary_for_ai | object | – | – |
| transit | object | – | – |
No examples provided.
screen_postcodes Screen & Rank Great Britain Postcodes ~242
Rank and screen 2 to 10 Great Britain postcodes by a specific target metric (affluence, house price, crime safety, broadband speed, family suitability, or connectivity). Returns a sorted leaderboard. For 11 to 50 postcodes use enrich_postcodes; for full cross-metric comparison of 2 to 5 postcodes use compare_postcodes.
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | yes | Target metric to rank postcodes by: "affluence" (1-100 score), "house_price" (median GBP), "crime_safety" (IMD crime decile), "broadband_speed" (gigabit availability), "family_suitability" (1-100 sco… |
| order | string | – | Sort order: "desc" (highest first, default) or "asc" (lowest first). |
| postcodes | array | yes | List of 2 to 10 Great Britain postcodes to screen and rank (e.g. ["SW1A 1AA", "BB7 3BB", "M1 1AE"]). Maximum 10 postcodes. |
| Name | Type | Req | Description |
|---|---|---|---|
| _attribution | string | yes | – |
| _billing | object | – | – |
| leaderboard | array | yes | – |
| metric_ranked_by | string | yes | – |
| order | string | yes | – |
| total_screened | number | yes | – |
No examples provided.
summarise_outcode Summarise Outward Postal District ~242
Use when you only have an outward code / district (e.g. SW1A, BB7, EH1, CF10) and need high-level district demographic and property statistics (~150 tokens). Do not use when an exact full unit postcode is available (use lookup_postcode).
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | – | – | Optional domain(s) to exclude: "schools", "healthcare", "transit" as a comma-separated string (e.g. "schools, healthcare") or an array of strings (e.g. ["schools", "healthcare"]). Note: exclude only… |
| outcode | string | yes | Great Britain outward postal district code to summarize (e.g. SW1A, BB7, M1, EH1, CF10). Covers England, Scotland, and Wales. |
| view | string | – | Optional view slice to return: "full" (complete district summary, default), "brief" (or "summary"/"ai", ~80 tokens context summary), "property", "demographics", "education", "healthcare", "transit",… |
| Name | Type | Req | Description |
|---|---|---|---|
| _attribution | string | yes | – |
| _billing | object | – | – |
| average_affluence_score_100 | number | yes | – |
| district_avg_price_per_sqm_gbp | number | yes | – |
| district_context_briefing | string | yes | – |
| district_median_house_price_gbp | number | yes | – |
| dominant_affluence_tier | string | yes | – |
| imd_overall_decile_range | object | yes | – |
| outcode | string | yes | – |
| sample_postcodes | array | yes | – |
| top_personas | array | yes | – |
| total_postcodes | number | yes | – |
No examples provided.
How do I install the uk.postcodecontext/mcp server?
uk.postcodecontext/mcp is a hosted endpoint at https://api.postcodecontext.uk/mcp, 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 · api.postcodecontext.uk
claude mcp add --transport http uk-postcodecontext-mcp 'https://api.postcodecontext.uk/mcp'
What is the uk.postcodecontext/mcp server?
uk.postcodecontext/mcp is listed in the public MCP registry as uk.postcodecontext/mcp. UK location intelligence: Census, HMLR/RoS prices, EPC, IMD, schools & transit via x402. This page covers its hosted endpoint (https://api.postcodecontext.uk/mcp).
Is the uk.postcodecontext/mcp server safe to use?
uk.postcodecontext/mcp scores 73 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.postcodecontext/mcp server expose?
uk.postcodecontext/mcp exposes 10 tools: lookup_postcode, compare_postcodes, enrich_postcodes, summarise_outcode, get_postcode_ai_brief, and 5 more. Their descriptions and schemas cost roughly 1,999 tokens of context every time the server is loaded.
Does the uk.postcodecontext/mcp server require authentication?
No. We connected to uk.postcodecontext/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the uk.postcodecontext/mcp server still maintained?
uk.postcodecontext/mcp 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.postcodecontext/mcp server?
VerifyMCP ran 12 checks on uk.postcodecontext/mcp, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about uk.postcodecontext/mcp: HTTPS. 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.