Supabase
MCP server for interacting with the Supabase platform
Beschreibung vom Entwickler (englisches Original)
Is an English rental ready for the landlord database? Deadline, gas/EICR/EPC, fee, checklist.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"rentready": {
"command": "uvx",
"args": [
"rentready",
"mcp"
]
}
}
}Führe das in deinem Terminal aus
claude mcp add rentready -- uvx rentready mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"rentready": {
"command": "uvx",
"args": [
"rentready",
"mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"rentready": {
"type": "stdio",
"command": "uvx",
"args": [
"rentready",
"mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto genzagents bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.8.1) kam vor 10 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Python (uv) auf deinem Computer.
In derselben Kategorie: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP server for interacting with the Supabase platform
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Is your rental ready for England's landlord database?
From 15 December 2026 every private landlord in England must register each let 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. Unoccupied properties need not be registered yet, and landlords of supported exempt accommodation are excluded (official guidance). Without an active entry the court cannot make a possession order, except on Ground 7A or Ground 14 (section 90). Penalties are up to £7,000 for a breach (section 91) and up to £40,000 for the offences in section 92: false information, continuing a breach after a penalty, or a repeat within five years. 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.
No install: check in your browser at https://genzagents.github.io/rentready/ (0.7.0: now with the registration pack). Add your properties or paste a CSV, see every property's window, deadline and certificate state, then download one .ics with every date and reminder. It runs docs/rentready.js, a line-for-line port of the Python that tests/test_web.py holds to identical answers and an identical calendar on five dates; the only network call is the postcode lookup at postcodes.io, and your list stays in your browser.
curl -sL https://raw.githubusercontent.com/genzagents/rentready/main/rentready/__init__.py | python3 - check "B3 2TA" --gas=2026-02-01 --eicr=2023-06-01 --eicr-due=2028-06-01 --epc=2017-05-01 --epc-rating=D
rentready 0.8.1 B3 2TA region: West Midlands
Window: requirement starts 2026-12-15, deadline 2027-03-14 (137 days from 2026-10-28); 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 (96 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; it would not meet the C minimum set for all tenancies from 1 October 2030 (government response, 21 Jan 2026; not yet law) Do next:
Fee: £65 a year (65 per property); renewal every 12 months: the renewal date is the last day of the 12 months from your first entry, one date for the whole portfolio (draft regulation 10); later properties pay pro rata Upload at registration (within 28 days of the entry, or it becomes inactive):
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 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 draft Private Rented Sector Database Regulations 2026, laid before Parliament on 9 September 2026 and not yet approved: the Lords Secondary Legislation Scrutiny Committee drew them to the special attention of the House (13th report, 22 October 2026) and committees of both Houses debated them on 28 October 2026 (Parliament record), as summarised by the NRLA and HCR Law; the same dates are in the official guidance at housinghub.campaign.gov.uk, which names the region "Yorkshire and Humber". Upload within 28 days of the entry and one renewal date for every property are in the draft regulations (regulation 6(2), regulation 10) and in the official guidance (29 October 2026), which also gives the fee formula: no charge for days before 15 November 2027, so the first payment is £5.34 to £64.82. The £65 fee is from the official guidance; the draft leaves the amount to the database operator (regulation 14). Miss the 28-day upload and the entry becomes inactive (regulation 11(2)(a)); any later change must be updated within 28 days (regulation 9(4)). The official guidance confirms the two 28-day rules and the single renewal date. Check gov.uk before relying on a date.
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 --json
Exit code 0 when nothing fails, 1 otherwise, so it works in a cron or a CI step.
rentready portfolio properties.csv # one line per property, every FAIL/WARN, total fee, earliest deadline
rentready portfolio properties.csv --json
properties.csv has a header row with any of name, postcode, gas, no_gas, eicr, eicr_due, epc, epc_rating, tenancy_start, region (eicr is the report's issue date, eicr_due the date it gives for the next inspection) (common spellings like Address, Post Code, Gas safety, Rating are accepted; a JSON list of objects works too):
name,postcode,gas,no_gas,eicr,epc,epc_rating
12 Example St,B3 2TA,2026-02-01,,2023-06-01,2017-05-01,D Flat 4,SW1A 1AA,,yes,2024-01-01,2020-01-01,C
rentready calendar properties.csv --out=rentready.ics # whole portfolio
rentready calendar "B3 2TA" --gas=2026-02-01 --eicr=2023-06-01 --epc=2017-05-01 --out=rentready.ics rentready calendar properties.csv --reminders=90,30,7 > rentready.ics
One all-day event per dated thing: the day your region's window opens, the registration deadline, and each gas safety, EICR and EPC expiry, each with reminders 60 and 14 days before (change with --reminders). Import the file into Google, Apple or Outlook calendar; UIDs are deterministic, so re-importing after a renewal updates the events instead of duplicating them. This is the free, serverless version of the monthly watch: nothing is stored anywhere but your own calendar.
rentready pack properties.csv --out=pack.md # add --organisation for a company or trust
No terminal? On https://genzagents.github.io/rentready/ press Show my registration pack after a check: the same pack (docs/rentready.js, parity-tested against pack.py), printable or saved as registration-pack.md for your agent. Extra columns pasted in the CSV are kept with your list in the browser.
Every question *Register your rental property* asks, in the service's own words (gov.uk "Get ready to register", Oct 2026): you as the landlord once, then per property the dwelling, tenancy, rent and health-and-safety sections. Answers come pre-filled from the CSV, a GATHER line marks each gap, and the pack tells you which columns to add to fill them (ownership, dwelling_type, bedrooms, let, occupants, households, licence, furnished, rent, rent_frequency, bills, optional freeholder, manager). Each certificate gets a file name to scan it as (12-example-st_eicr_2023-06-01.pdf) and a state: READY, RENEW SOON (expires before your deadline), RENEW (lapsed: renew before you upload) or GATHER. A lapsed EPC is accepted with the current tenancy's start date, and an F or G rating adds the MEES exemption question. A property is ready to register only when every answer and file is in hand. Nothing registers for you: you start the entry with GOV.UK One Login.
A certificate that lapses in month four is the thing nobody notices until the deadline. The watch is the alarm, and it runs for free as a GitHub Action in a private repo of yours that holds properties.csv: on the first of every month it re-checks every property, keeps one issue up to date with the full table, and comments on that issue only when something needs action: a gas safety record, EICR or EPC within 60 days of expiring, your region's window opening, a deadline nearing or passing, or a property no longer ready. GitHub emails the comment to you. No server, no account beyond GitHub, no dependencies; your dates never leave your repo except for the postcode lookup. Example: issue #1 watches docs/example.csv.
Copy docs/watch.yml to .github/workflows/rentready-watch.yml:
on:
schedule: [{ cron: "23 7 1 * *" }] # the 1st of each month workflow_dispatch: push: { paths: [properties.csv] } permissions: { issues: write, contents: read } jobs: watch: runs-on: ubuntu-latest steps:
The same command runs from cron on your own machine with a local state file instead of an issue:
rentready watch properties.csv --state=rentready-state.json # exit 1 when something needs action
claude plugin marketplace add genzagents/marketplace
claude plugin install rentready@genzagents
Or add to any MCP client: uvx rentready mcp (from PyPI) or python3 /path/to/rentready/__init__.py mcp (stdio). Four tools: check_property, check_portfolio (CSV or JSON text in, one table out), make_calendar (returns the .ics text for one property or a portfolio) and registration_pack (the markdown checklist above).
Listed in the official MCP registry as io.github.genzagents/rentready.
mcp-name: io.github.genzagents/rentready
--region= to skip the lookup). Wales and Scotland are flagged out of scope.Nur der Anfang wird gezeigt; den Rest findest du im Repo