Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Rentfeed 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
US rental listings as JSON: free sample search and rent statistics, plus your licensed feed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user rentfeed-mcp '--' npx -y @reneturcios/rentfeed mcp
# 2 — ask your agent for something these tools do
# search_rentals_sample, rent_summary, feed_status and 2 more
Rentfeed 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 Rentfeed 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 rentfeed-mcp '--' npx -y @reneturcios/rentfeed 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.
5 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.
Live US rental listings for an area and budget, no key needed. Returns at most 10 listings per call (rent, beds, baths, size, address, coordinates, photo, source link, days listed). Use a state code and a city for one market; add rent and bedroom limits to narrow it. For complete results a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Two-letter US state code, e.g. NY. |
| city | string | no | City name, partial match, e.g. Brooklyn. |
| min_rent | number | no | Minimum monthly rent in USD. |
| max_rent | number | no | Maximum monthly rent in USD. |
| min_beds | number | no | Minimum bedrooms; 0 = studio. |
| max_beds | number | no | Maximum bedrooms. Same as min_beds for exactly N. |
| min_lat | number | no | South edge of a map box. |
| max_lat | number | no | North edge of a map box. |
| min_lng | number | no | West edge of a map box. |
| max_lng | number | no | East edge of a map box. |
| new_since_days | number | no | Only listings first seen in the last N days (new listings land weekly, Sunday to Tuesday UTC). |
| sort | string | no | best (default): photo and coordinates first, freshest, mixed sources. |
What rent costs right now in one US city or ZIP, no key needed: number of listings and the median, 25th and 75th percentile monthly asking rent, overall and by bedroom count (studio, 1, 2, 3, 4+). Based on listings verified at the source in the last 30 days. Give a state and a city or a ZIP.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter US state code, e.g. TX. |
| city | string | no | Full city name, e.g. Austin or New York (New York includes its five boroughs). Not a partial match. |
| zip | string | no | Exact 5-digit ZIP code; use instead of or with city. |
| beds | integer | no | Only this bedroom count: 0 = studio, 4 = four or more. |
| include_rooms | boolean | no | true = include rooms in shared homes (excluded by default). |
Requires a HousingFeed key. The current version of your licensed feed: listing count, when it was published, when the next weekly update is due, and how many listings were added, changed and removed.
No parameter schema on file.
Requires a HousingFeed key. Search the listings in your licensed feed by city, ZIP, rent, bedrooms or map box. Returns up to 50 per call with a total; page with offset.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Two-letter US state code. |
| city | string | no | City name, partial match. |
| zip | string | no | Exact ZIP code. |
| min_rent | number | no | Minimum monthly rent in USD. |
| max_rent | number | no | Maximum monthly rent in USD. |
| min_beds | number | no | Minimum bedrooms; 0 = studio. |
| max_beds | number | no | Maximum bedrooms. Same as min_beds for exactly N. |
| min_lat | number | no | South edge of a map box. |
| max_lat | number | no | North edge of a map box. |
| min_lng | number | no | West edge of a map box. |
| max_lng | number | no | East edge of a map box. |
| limit | integer | no | Listings to return (default 10). |
| offset | integer | no | Skip this many matches (for paging). |
| full | boolean | no | true = every field of each listing, including description and photos. |
Requires a HousingFeed key. Listings added, changed or removed in the latest weekly update of your feed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| change | string | no | Only this kind of change. |
| since | string | no | Changes since this earlier version (one of feed_status's changes_from) instead of since the previous week; for a client that missed a week. |
| limit | integer | no | Changes to return (default 20). |
| offset | integer | no | Skip this many changes (for paging). |
- 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 Rentfeed 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 Rentfeed 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.