Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
rentready 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
Is an English rental ready for the landlord database? Deadline, gas/EICR/EPC, fee, checklist.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user rentready-mcp '--' uvx rentready mcp
# 2 — ask your agent for something these tools do
# check_property, check_portfolio, make_calendar and 1 more
rentready 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 rentready 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 uv (docs.astral.sh/uv): uvx 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 rentready-mcp '--' uvx rentready 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.
4 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.
Is an English rental property ready for the landlord database (Register your rental property, Renters' Rights Act)?
| Parameter | Type | Required | Notes |
|---|---|---|---|
| postcode | string | no | Property postcode (England) |
| region | string | no | Override region, e.g. 'London', if no postcode |
| gas | string | no | Gas safety record issue date YYYY-MM-DD |
| no_gas | boolean | no | True if the property has no gas supply |
| eicr | string | no | EICR issue date YYYY-MM-DD |
| eicr_due | string | no | Date the EICR gives for the next inspection YYYY-MM-DD (used instead of issue + 5 years; give it whenever the report has one) |
| epc | string | no | EPC issue date YYYY-MM-DD |
| epc_rating | string | no | EPC rating letter A-G |
| tenancy_start | string | no | Current tenancy start date YYYY-MM-DD |
| properties | integer | no | Number of properties, for the fee |
Check many English rental properties at once for the landlord database. Input is CSV text (header row: name, postcode, gas, no_gas, eicr, eicr_due, epc, epc_rating, tenancy_start, region)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| portfolio | string | yes | CSV text or JSON list of properties |
| today | string | no | Override today's date YYYY-MM-DD |
Build an iCalendar (.ics) file for one property or a portfolio: registration window opens, registration deadline, and each gas/EICR/EPC expiry as all-day events with reminders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| portfolio | string | no | CSV text or JSON list of properties (omit for a single property) |
| postcode | string | no | — |
| region | string | no | — |
| name | string | no | Label for the property |
| gas | string | no | — |
| no_gas | boolean | no | — |
| eicr | string | no | — |
| eicr_due | string | no | — |
| epc | string | no | — |
| reminder_days | array | no | Days before each event to alarm, default [60, 14] |
Prepare the registration pack for England's 'Register your rental property' service: every question the service asks
| Parameter | Type | Required | Notes |
|---|---|---|---|
| portfolio | string | yes | CSV text or JSON list of properties |
| organisation | boolean | no | True if the landlord is a company, trust or other organisation |
| today | string | no | Override today's date YYYY-MM-DD |
- 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 rentready 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 | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| 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. moderate 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.8.1. 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 rentready 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.