# 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

- Trust score: 83/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.housefile.app`: 83/100 (this document), [markdown](https://verifymcp.io/servers/app-housefile-licensing/www.md), [page](https://verifymcp.io/servers/app-housefile-licensing/www)

## Channel facts

- Endpoint: `https://www.housefile.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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**: 80/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 is enforced; there's no plaintext access path.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 50/100
  - 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.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 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.

### Claude

```bash
claude mcp add --transport http app-housefile-licensing 'https://www.housefile.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-housefile-licensing": {
      "url": "https://www.housefile.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-housefile-licensing": {
      "type": "http",
      "url": "https://www.housefile.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-housefile-licensing]
url = "https://www.housefile.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-housefile-licensing": {
      "type": "remote",
      "url": "https://www.housefile.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-housefile-licensing --url 'https://www.housefile.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-housefile-licensing:
    url: "https://www.housefile.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-housefile-licensing": {
      "Transport": "http",
      "Url": "https://www.housefile.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-housefile-licensing -t streamable-http -u 'https://www.housefile.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-housefile-licensing": {
      "type": "http",
      "url": "https://www.housefile.app/mcp"
    }
  }
}
```

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-16 (score 83, 0)

- [security] Stability: 0.97 → pass

### 2026-11-15 (score 83, +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.

### 2026-11-12 (score 82, +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.

### 2026-11-10 (score 81, +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.

### 2026-11-08 (score 80, +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.

### 2026-11-06 (score 79, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 78, +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.

### 2026-11-02 (score 77, +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.

## MCP tools (4)

### `check_property_licensing` (~187 tokens)

Check a property’s licensing

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.

Input parameters:

- `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, required): The full UK postcode of the property being checked, in any spacing or case, such as "e8 1dy". Only its first half is kept

Output parameters:

- `as_of_date` (string)
- `council` (string|null)
- `council_address_checker` (string|null): The council’s own address-level lookup, where it has one
- `council_gss_code` (string|null)
- `country` (string)
- `covered` (boolean)
- `disclaimer` (string)
- `housefile_url` (string)
- `postcode` (string)
- `schemes` (array)
- `upcoming` (array)

### `list_council_schemes` (~119 tokens)

List a council’s licensing schemes

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.

Input parameters:

- `council` (string, required): A council name, part of one, or its GSS code, such as "Croydon" or "E09000008"

Output parameters:

- `candidates` (array)
- `council`
- `disclaimer` (string)
- `query` (string)
- `result` (string)
- `schemes` (array)

### `upcoming_licensing_changes` (~146 tokens)

Upcoming licensing changes

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.

Input parameters:

- `council` (string): A council name, part of one, or its GSS code
- `within_months` (integer): Months ahead and back to look, 6 by default

Output parameters:

- `candidates` (array)
- `council` (string|null)
- `disclaimer` (string)
- `note` (string): What the stages mean, and how to see more when a list was cut short
- `recent_changes` (array): Newest first, at most 10 when no council is given
- `recent_changes_total` (number): How many changes there were in the window; more than listed when the list was cut short
- `result` (string)
- `upcoming` (array): Soonest first, then proposals with no start date by council; at most 15 when no council is given
- `upcoming_total` (number): How many schemes are proposed or starting soon; more than listed when the list was cut short
- `within_months` (number)

### `licensing_coverage` (~76 tokens)

Which councils are covered

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.

Output parameters:

- `checked_no_scheme_councils` (array): 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)
- `council_count` (number): Every council the records cover, with schemes or checked and found to run none
- `councils` (array): Councils with published schemes. Councils checked and found to run none are in checked_no_scheme_councils
- `councils_with_schemes` (number)
- `housefile_url` (string)
- `most_recent_verification` (string|null)
- `note` (string)
- `published_scheme_count` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-housefile-licensing/www#diagnostics

## Score history

- 2026-11-21: 83
- 2026-11-20: 83
- 2026-11-19: 83
- 2026-11-18: 83
- 2026-11-17: 83
- 2026-11-16: 83
- 2026-11-15: 83
- 2026-11-14: 82
- 2026-11-13: 82
- 2026-11-12: 82
- 2026-11-11: 81
- 2026-11-10: 81
- 2026-11-09: 80
- 2026-11-08: 80
- 2026-11-07: 79
- 2026-11-06: 79
- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 72
- 2026-10-23: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://www.housefile.app/mcp
- Website: https://www.housefile.app/mcp/about
- Changelog RSS feed: https://verifymcp.io/servers/app-housefile-licensing/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-housefile-licensing/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-housefile-licensing/www.json
- HTML version of this page: https://verifymcp.io/servers/app-housefile-licensing/www
