Skip to content

HouseFile UK property licensing checker MCP server

app.housefile/licensinghousefile.appstreamable-httpv1.1.0Scanned

Checks whether a property in England is in a council's selective or HMO licensing scheme

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the HouseFile UK property licensing checker MCP server can do

The HouseFile UK property licensing checker MCP server is published by housefile.app, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: check_property_licensing, upcoming_licensing_changes and licensing_coverage), but cannot delete data. 1 tool only reads.

1 tool reads private data (list_council_schemes).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • check_property_licensingLooks 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a property’s licensing
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • licensing_coverageWhich 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 f…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Which councils are covered
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • upcoming_licensing_changesWhat’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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Upcoming licensing changes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • list_council_schemesLists 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 la…Reads private dataNo findings

    Why it is in this group

    • The name "list_council_schemes" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List a council’s licensing schemes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.housefile.app/mcp: tools/list returned 4 tools to an anonymous client, including check_property_licensing (write), upcoming_licensing_changes (write), licensing_coverage (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__licensing__list_council_schemes"
    ],
    "ask": [
      "mcp__licensing__check_property_licensing",
      "mcp__licensing__upcoming_licensing_changes",
      "mcp__licensing__licensing_coverage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as licensing. Review it before you use it.

Capability tags behind 1 rule
  • mcp__licensing__list_council_schemes private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.housefile/licensing/verify?hash=9faa097118d3c6642956fa2bf385437234a9e8b54d7cd416d781f2a5c4329bb5" | jq -e '.changed == false'

Pinned hash 9faa097118d3, from Nov 9, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.housefile/licensing/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.housefile/licensing
[![Anlyon Radar](https://radar.anlyon.com/badge/app.housefile/licensing.svg)](https://radar.anlyon.com/servers/app.housefile/licensing)

Source: MCP Registry. Synced Oct 24, 2026, 09:17 UTC.

HouseFile UK property licensing checker MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the HouseFile UK property licensing checker MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the HouseFile UK property licensing checker MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the HouseFile UK property licensing checker MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the HouseFile UK property licensing checker MCP server have?

4 tools: 3 write, 1 read. check_property_licensing, upcoming_licensing_changes, licensing_coverage and list_council_schemes.

Does the HouseFile UK property licensing checker MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the HouseFile UK property licensing checker MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the HouseFile UK property licensing checker MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.