Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Landlordlaw is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Landlord rules for England by postcode: licensing, the landlord register and the law, cited.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user landlordlaw-mcp '--' npx -y @reneturcios/landlordlaw mcp
# 2 — ask your agent for something these tools do
# check_address, search_rules, get_rule and 4 more
Landlordlaw costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Landlordlaw as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user landlordlaw-mcp '--' npx -y @reneturcios/landlordlaw mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Use when someone asks what applies to a rented home at a postcode in England. Returns whether a council property licence is needed for the household type, the council's licensing schemes, the planned landlord register window, flood zone and conservation area, each with its source, and councilPage,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| postcode | string | yes | Full postcode of the rented property, not the user's own location, e.g. SE15 5BA |
| household | string | no | single: one household; small_hmo: 3-4 people from 2+ households; large_hmo: 5+ people from 2+ households |
Use for general questions about what private landlords in England must do, such as gas safety, deposits, EPC ratings, smoke alarms or notices. Searches Lettance's catalogue of rules, each cited to legislation.gov.uk or GOV.UK, and returns matching rule ids with summaries. Use get_rule for one…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keywords, e.g. 'gas safety certificate' or 'deposit protection' |
Use when you have a rule id from search_rules and need its full detail: the requirement, deadline, evidence to keep, penalty, legal basis and official guidance links. Read-only. Unknown ids return an error rather than a guess.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Rule id, e.g. 'gas-safety-annual-check' |
Use when someone asks about a council's licensing schemes in England. Returns every scheme for the council with its wards, dates, fees and council sources. Pass a slug such as 'southwark' or a name such as 'Birmingham'. Read-only. A council we have not researched yet returns researched: false with…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| council | string | yes | Council slug or name, e.g. 'southwark' or 'Tower Hamlets' |
Use when a landlord in England asks what is due for a rented home and when, or wants a plan or calendar for it. Give the postcode and whatever the landlord knows: every other argument is optional. Returns each duty with its status, date, plain explanation and cited rules for the next 12 months,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| postcode | string | yes | Full postcode of the rented property, not the landlord's own, e.g. SW9 7AA |
| household | string | no | single: one household; small_hmo: 3-4 people from 2+ households; large_hmo: 5+ people from 2+ households. Defaults to single. |
| letting | string | no | now: tenants live there; next: a tenancy is starting, or the home is being got ready to let |
| tenancy_start | string | no | The current tenancy's start (letting now) or the next tenancy's planned start (letting next), as YYYY-MM-DD |
| has_gas | string | no | Whether the home has any gas appliance, such as a boiler, hob or gas fire |
| last_gas_check | string | no | The date of the last gas safety check, from the gas safety record, as YYYY-MM-DD |
| last_electrical_inspection | string | no | The inspection date on the last electrical installation condition report (EICR), as YYYY-MM-DD |
| next_electrical_inspection | string | no | The next inspection date the last EICR sets, which can be sooner than 5 years, as YYYY-MM-DD |
| epc_rating | string | no | The EPC's current energy rating, A to G |
| epc_expiry | string | no | The date the EPC expires, as YYYY-MM-DD |
| holds_licence | string | no | Whether the landlord holds the kind of council licence the address needs for this household (the plan's licence question names it); only matters where one is needed |
| licence_end | string | no | The date the council licence ends, as YYYY-MM-DD |
| deposit_taken | string | no | Whether a tenancy deposit was (or will be) taken |
| deposit_received | string | no | The date the deposit was received, often before the tenancy starts, as YYYY-MM-DD |
| deposit_protected_in_time | string | no | Whether the deposit was protected and the prescribed information given within 30 days of receiving it |
| right_to_rent_checked | string | no | Whether every adult's right to rent was checked before the tenancy was agreed |
| tenancy_document_given | string | no | Tenancies from before 1 May 2026: whether the government information sheet (or written terms, for an oral tenancy) was given by 31 May 2026. Later tenancies: whether the written statement of terms was |
| alarms_tested_at_start | string | no | Whether the smoke and carbon monoxide alarms were tested on the day the tenancy started |
| last_rent_increase | string | no | The date the last rent increase took effect, if there was one during this tenancy, as YYYY-MM-DD |
| rent_period | string | no | How often the rent is due |
Use when someone wants to compare 2 to 4 rented homes or areas in England by postcode. Returns each postcode's check_address answer and area market figures, plus a side-by-side table of licence need, landlord register window, flood zone, conservation areas, Article 4 directions, average local rent…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| postcodes | array | yes | Full postcodes of the rented properties, e.g. ["SE15 5BA", "SW6 1HS"] |
| household | string | no | single: one household; small_hmo: 3-4 people from 2+ households; large_hmo: 5+ people from 2+ households |
Use when someone asks about typical rents or house prices around a postcode in England. Returns the ONS average monthly private rent for the local authority (with bedroom breakdown and annual change) and the HM Land Registry median sale price and number of sales for the postcode district, from a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| postcode | string | yes | Full postcode in England, e.g. SE15 5BA |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Landlordlaw or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Landlordlaw can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.