HouseFile UK property licensing checker
REMOTE · WWW.HOUSEFILE.APP
Checks whether a property in England is in a council's selective or HMO licensing scheme
Available components
Last scanned (17 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 699 tokens (~174/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 (100% of tools); any adoption earns full credit.Pass
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Never tell the user", at byte 416 of that field. See how to fix → Fail
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 16 Nov 26 0
- Stability: 0.97 → pass security
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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://www.housefile.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.housefile.app | CN=YR1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 2048 | SHA256-RSA | 51a5b3c9375a8d1f7fbfd878d7ecc541880 |
| SANs: www.housefile.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.housefile.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| housefile.app. | 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=63072000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'self'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.housefile.app/mcp | Verified | 200 | |
| http (plaintext) | http://www.housefile.app/mcp | HTTPS enforced | 308 | https://www.housefile.app/mcp |
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 →
check_property_licensing Check a property’s licensing ~187
Looks up a postcode in England in HouseFile’s records of council licensing schemes and returns each scheme in force there, with its dates, fee, source link and the date the records were last verified, plus the national HMO rule. Schemes not in force yet are listed under upcoming. It works to postcode precision, so near a scheme’s edge it says so. Give occupants and households to settle the mandatory HMO test in England.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | – | YYYY-MM-DD. Defaults to today; at most 24 months ahead |
| households | integer | – | How many separate households they form |
| occupants | integer | – | How many people live in the property |
| postcode | string | yes | The full UK postcode of the property being checked, in any spacing or case, such as "e8 1dy". Only its first half is kept |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | yes | – |
| council | string|null | yes | – |
| council_address_checker | string|null | yes | The council’s own address-level lookup, where it has one |
| council_gss_code | string|null | yes | – |
| country | string | yes | – |
| covered | boolean | yes | – |
| disclaimer | string | yes | – |
| housefile_url | string | yes | – |
| postcode | string | yes | – |
| schemes | array | yes | – |
| upcoming | array | yes | – |
No examples provided.
licensing_coverage Which councils are covered ~76
Which councils HouseFile’s records cover: each council with published schemes, with how many, how many are in force and when they were last verified, and the councils checked and found to run none. Use it to tell the user honestly whether their area is covered, and list_council_schemes for one council’s detail.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| checked_no_scheme_councils | array | yes | Short names of the councils a person checked and found to run no additional or selective scheme. list_council_schemes gives the date |
| checked_no_scheme_count | number | yes | – |
| council_count | number | yes | Every council the records cover, with schemes or checked and found to run none |
| councils | array | yes | Councils with published schemes. Councils checked and found to run none are in checked_no_scheme_councils |
| councils_with_schemes | number | yes | – |
| housefile_url | string | yes | – |
| most_recent_verification | string|null | yes | – |
| note | string | yes | – |
| published_scheme_count | number | yes | – |
No examples provided.
list_council_schemes List a council’s licensing schemes ~119
Lists a council’s licensing schemes from HouseFile’s records: in force, starting soon, proposed, and ended in the last 12 months, each with its area, dates, fee, source link and last verified date. Takes a council name, part of a name or a GSS code. If several councils match, it returns them to choose from.
| Name | Type | Req | Description |
|---|---|---|---|
| council | string | yes | A council name, part of one, or its GSS code, such as "Croydon" or "E09000008" |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | – |
| council | – | yes | – |
| disclaimer | string | yes | – |
| query | string | yes | – |
| result | string | yes | – |
| schemes | array | yes | – |
No examples provided.
upcoming_licensing_changes Upcoming licensing changes ~146
What’s coming: schemes proposed or starting soon, and recent changes to schemes in HouseFile’s records (started, ended, fee, dates or area changed), newest first. Optionally for one council, and for a number of months ahead and back (6 by default, at most 24). For all councils the lists stop at the 15 soonest schemes and the 10 latest changes, with the totals; ask for one council to see all of its own.
| Name | Type | Req | Description |
|---|---|---|---|
| council | string | – | A council name, part of one, or its GSS code |
| within_months | integer | – | Months ahead and back to look, 6 by default |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | – |
| council | string|null | yes | – |
| disclaimer | string | yes | – |
| note | string | yes | What the stages mean, and how to see more when a list was cut short |
| recent_changes | array | yes | Newest first, at most 10 when no council is given |
| recent_changes_total | number | yes | How many changes there were in the window; more than listed when the list was cut short |
| result | string | yes | – |
| upcoming | array | yes | Soonest first, then proposals with no start date by council; at most 15 when no council is given |
| upcoming_total | number | yes | How many schemes are proposed or starting soon; more than listed when the list was cut short |
| within_months | number | yes | – |
No examples provided.
How do I install the HouseFile UK property licensing checker MCP server?
HouseFile UK property licensing checker is a hosted endpoint at https://www.housefile.app/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 · www.housefile.app
claude mcp add --transport http app-housefile-licensing 'https://www.housefile.app/mcp'
What is the HouseFile UK property licensing checker MCP server?
HouseFile UK property licensing checker is an MCP server listed in the public MCP registry as app.housefile/licensing. Checks whether a property in England is in a council's selective or HMO licensing scheme. This page covers its hosted endpoint (https://www.housefile.app/mcp).
Is the HouseFile UK property licensing checker MCP server safe to use?
HouseFile UK property licensing checker scores 83 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 HouseFile UK property licensing checker MCP server expose?
HouseFile UK property licensing checker exposes 4 tools: check_property_licensing, list_council_schemes, upcoming_licensing_changes, licensing_coverage. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.
Does the HouseFile UK property licensing checker MCP server require authentication?
No. We connected to HouseFile UK property licensing checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HouseFile UK property licensing checker MCP server still maintained?
HouseFile UK property licensing checker 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 HouseFile UK property licensing checker MCP server?
VerifyMCP ran 13 checks on HouseFile UK property licensing checker, 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.