Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@rentready is B3 2TA ready? gas expires 2026-02-01, EICR 2023-06-01, EPC 2017-05-01"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Is your rental ready for England's landlord database?
From 15 December 2026 every private landlord in England must register each property on the government's
"Register your rental property" service (Renters' Rights Act 2025), region by region, at £65 per property per year,
uploading the gas safety record, EICR and EPC. Without an active entry there is no possession order from the court,
and penalties run to £7,000 (£40,000 for a repeat). rentready tells you your region's window and deadline, whether
your certificates will still be in date, what to book, what to upload and what it costs. Zero dependencies, one file,
also an MCP server and a Claude Code plugin, so your own agent can run it.
curl -sL https://raw.githubusercontent.com/genzagents/rentready/main/rentready/__init__.py | python3 - check "B3 2TA" --gas=2026-02-01 --eicr=2023-06-01 --epc=2017-05-01 --epc-rating=Drentready 0.1.0 B3 2TA region: West Midlands
Window: requirement starts 2026-12-15, deadline 2027-03-14 (139 days from 2026-10-26); the service opens for everyone on 2026-12-15
PASS registration deadline: West Midlands requirement starts 2026-12-15, deadline 2027-03-14; you can register from 2026-12-15
WARN gas safety record: expires 2027-02-01, before the 2027-03-14 deadline (98 days)
PASS EICR: valid to 2028-06-01
PASS EPC: valid to 2027-05-01
INFO EPC rating: rating D meets today's E minimum; the proposed C minimum for new tenancies from 2028 and all tenancies from 2030 would not be met
Do next:
- Book before 2027-02-01: annual gas safety check by a Gas Safe engineer; upload the record and issue date
Fee: £65 a year (65 per property); renewal annual, on the anniversary of the first property registered (one date for the whole portfolio); later properties pay pro rata
Upload at registration (within 28 days of the entry):
- Latest gas safety record (CP12) and its issue date, if the property has gas
- EICR (or EIC if no EICR yet) and its expiry date
- Latest EPC, and any MEES exemption; if the EPC has lapsed, the start date of the current tenancy
READY: nothing expires before your deadline. Gather the details above and register when your window opens.Region | Requirement starts | Deadline (midnight) |
West Midlands | 15 Dec 2026 | 14 Mar 2027 |
East of England | 15 Jan 2027 | 14 Apr 2027 |
East Midlands | 15 Feb 2027 | 14 May 2027 |
South East | 15 Mar 2027 | 14 Jun 2027 |
Yorkshire and The Humber | 15 Apr 2027 | 14 Jul 2027 |
North West | 15 May 2027 | 14 Aug 2027 |
North East | 15 Jun 2027 | 14 Sep 2027 |
London | 15 Jul 2027 | 14 Oct 2027 |
South West | 15 Aug 2027 | 14 Nov 2027 |
Registration opens for all of England on 15 December 2026. Source: the Private Rented Sector Database Regulations 2026 as summarised by the NRLA and HCR Law; official guidance at housinghub.campaign.gov.uk. Check gov.uk before relying on a date.
Related MCP server: UK Property Data
pip install git+https://github.com/genzagents/rentready # or copy rentready/__init__.py anywhere
rentready regions
rentready check "SW1A 1AA" --no-gas --eicr=2024-01-01 --epc=2020-01-01 --properties=3 --jsonExit code 0 when nothing fails, 1 otherwise, so it works in a cron or a CI step.
claude plugin marketplace add genzagents/marketplace
claude plugin install rentready@genzagentsOr add to any MCP client: python3 /path/to/rentready/__init__.py mcp (stdio). One tool, check_property.
Region from the postcode (postcodes.io, no key; --region= to skip the lookup). Wales and Scotland are flagged out of scope.
Registration window and deadline for that region; whether it is open, upcoming or missed.
Gas safety record (annual), EICR (five-yearly), EPC (ten-yearly): valid at the deadline, expiring before it, expired, or missing.
EPC rating against the current E minimum and the proposed C minimum.
The fee for N properties, the renewal rule, the full list of details the service asks for, and the penalties.
It does not register for you, fetch certificates, or hold any data. It never sends your dates anywhere; the only network call is the postcode lookup. Not legal advice.
A monthly watch per property (alerts before gas, EICR, EPC or the registration lapse; one email a month otherwise) is the paid step, a few pounds a year. Press the button on the project page if you want it.
MIT. Built by genzagents; sibling of citable.
Is an English rental property ready for the landlord database (Register your rental property, Renters' Rights Act)? Returns the region's registration window and deadline, whether the gas safety record, EICR and EPC will still be valid, the £65/property fee, the upload checklist and the penalties.
| Name | Required | Description | Default |
|---|---|---|---|
| epc | No | EPC issue date YYYY-MM-DD | |
| gas | No | Gas safety record issue date YYYY-MM-DD | |
| eicr | No | EICR issue date YYYY-MM-DD | |
| no_gas | No | True if the property has no gas supply | |
| region | No | Override region, e.g. 'London', if no postcode | |
| postcode | No | Property postcode (England) | |
| epc_rating | No | EPC rating letter A-G | |
| properties | No | Number of properties, for the fee | |
| tenancy_start | No | Current tenancy start date YYYY-MM-DD |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the full behavioral burden. It usefully discloses the kinds of results returned and implies a read-only check via 'Is ... ready' and 'Returns', but it does not explicitly state that the tool is side-effect free, what permissions are required, or how missing inputs affect the result.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loads the core question before listing the returned information. The return list is dense and could be more structured, but every phrase contributes relevant domain context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a nine-parameter compliance-check tool with no annotations and no output schema, the description gives useful context about what is returned and why. It still leaves gaps around how optional inputs are handled, whether any parameters are practically required, and the exact shape or conditions of the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all nine parameters. The description adds some domain meaning by linking EPC, gas, EICR, region, and properties to the returned compliance checks and fee, but it does not clarify the roles of parameters like tenancy_start or no_gas beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies a compliance-readiness check for English rental properties in the landlord database, and it lists the specific outputs (registration window, certificate validity, fee, checklist, penalties). It is specific about the regulatory context but does not sharply distinguish a verb/resource pair beyond the implied 'check property readiness'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The usage scenario is implied: use this for English rental properties before landlord registration. However, there are no explicit when-to-use, when-not-to-use, prerequisite, or alternative-tool statements, and no guidance on whether all inputs are optional or what happens when key dates are omitted.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0check_propertyScored across 1 tool
There is only one tool, so there is no possibility of overlap or misselection. Its name and description make its single purpose unmistakable.
check_property follows a clear snake_case verb_noun convention, which would scale predictably if more tools were added. With only one tool there is no pattern to verify, so it cannot be a full 5.
The server is scoped to a single narrow question (is a rental property ready to register), which one tool can answer. However, a one-tool surface is thin and leaves no room for related checks such as cost breakdowns or remediation steps.
The description promises the region's registration window and deadline, certificate validity (gas safety, EICR, EPC), fee, upload checklist, and penalties, which is a thorough answer for the readiness question. Minor gaps: no guidance on fixing non-compliant items and no coverage beyond England.
Checks whether a property in England is in a council's selective or HMO licensing scheme
UK property data: EPC, flood risk, planning, sale prices, MEES 2030 checks and grants.
UK tenancy and employment rule checks: deposits, notice, rent increases, holiday and minimum wage.
Landlord rules for England by postcode: council licensing, the landlord register and the law, cited.