Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
PutRoots 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.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
SF move agent: rentals with sources, no-SSN banking routes, and your move plan and drafts.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http putroots-mcp https://www.putroots.com/mcp
# 2 — ask your agent for something these tools do
# search_listings, listing_requirements, newcomer_options and 8 more
PutRoots costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PUAll 1 server
putroots1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http putroots-mcp https://www.putroots.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 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.
Search PutRoots' San Francisco rental index. Every row carries its source, the date we last saw it, and whether the landlord stated any requirements at all. Use this when someone asks what's available in SF at a price / bedroom count / neighborhood. Without a signed-in PutRoots account this searches the free sample only (3 listings per bedroom tier) and says so, with the true total.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_price | number | no | Max monthly rent in USD. Listings with no stated price are excluded when you set this — we don't let unpriced posts through a price filter. |
| min_price | number | no | Min monthly rent in USD. |
| beds | string | no | Bedroom tier. "room" means a room in a shared place. |
| hood | string | no | Neighborhood name, matched loosely (e.g. "Mission", "Sunset"). |
| limit | integer | no | How many to return (default 10, max 25). Newest first. |
For one listing URL from search_listings: what the landlord requires, what the renter filled in, and the gap on each line — income, credit, SSN, deposit, pets, co-signer, documents. Each line carries the landlord's own sentence it was read from, plus where the rule came from and when we fetched it. Requires the renter's own PutRoots account (the comparison is against qualifications they filled in)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing_url | string | yes | The listing's url, exactly as returned by search_listings. |
The doors a newcomer has to walk through besides the apartment: opening a bank account, a credit card, a phone plan, or getting an SSN — specifically the routes that work without an SSN or US credit history. Returns real branches and stores (address, hours, phone) plus the no-branch options, each with its source and the date it was checked, and our firsthand account where we did it ourselves.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | bank = checking account, card = credit card, sim = phone plan, ssn = the SSN itself. |
When someone has just signed a lease, accepted an offer, or otherwise has a move coming: returns a PutRoots link that pre-fills their move date and new address and attributes them to you. Nothing is created on their behalf — they sign up themselves by opening the link. Use the returned id with GET /v1/handoffs/{id} to see which stage of the move they are in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trigger | string | yes | What set the move off: lease_signed, offer_accepted, relocation_approved, or your own short label. |
| stage | string | no | Which stage of the journey they are in right now, if you know it. |
| d0 | string | no | Move-in day, YYYY-MM-DD. |
| to | string | no | The new address, as one line. |
| profile_seed | object | no | Reserved. Accepted but not applied yet — the person fills their own profile after signing up. |
The whole move at a glance for the signed-in person: days to move day, how many tasks there are, how many are settled, how many can be done right now, how many are blocked and how many are overdue, plus the critical path. Two rulers share that answer and they are not interchangeable: total and done count every task in the move, while actionable, blocked and overdue count only tasks that have been
No parameter schema on file.
What the signed-in person should do next on their move: one task to press, a few short lines after it, and a count of everything folded away. This is deliberately one screen, not the task list — picking which one matters is our job, not the caller's, and a task whose prerequisites aren't done doesn't appear at all (its prerequisite does). Use move_plan for totals. This is also the only place a tas
No parameter schema on file.
One task on the signed-in person's move: what it is, when it is due, what state it is in, any draft already prepared, and which fields it is waiting on them to answer. Read-only — opening a task leaves no trace. It does not tell you whether the task is in flight: that needs evidence lookups this cheap read skips on purpose. move_tasks is the only place "in progress" appears.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | A task id exactly as move_tasks / move_plan returned it. |
Prepares one task for the signed-in person and stops. It writes the email or the call script and hands it back; it never sends, dials, submits or pays, and no MCP tool can. The person presses send themselves in PutRoots. It covers email and call tasks, plus a form-filling task that has already been tried and given up on (that falls back to a letter or a call). It cannot start the other two kinds:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | A task id exactly as move_tasks / move_plan returned it. |
| to | string | no | Recipient, when the person supplies one: an email address for an email task, a phone number for a call task. Leave it out to use the recipient we already have. |
Fills in one field the signed-in person's task is waiting on (the names come back in missing from move_task or move_task_draft). Only fields that task is actually asking for are accepted, and only values we can store — anything else is refused rather than silently dropped. Pass what the person actually said; never a guess or a plausible default.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | A task id exactly as move_tasks / move_plan returned it. |
| field | string | yes | A field name from the task's missing list. |
| value | string | yes | What the person said. Not inferred, not a placeholder. |
later = push it out; it comes back on its own in three days. not_applicable = it doesn't apply to this person; it leaves the list, stops counting against the move, and anything waiting on it can go ahead. undo = put a ruled-out task back. Only on the person's say-so: ruling a task out changes what the rest of the move waits on.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | A task id exactly as move_tasks / move_plan returned it. |
| mode | string | yes | — |
The signed-in person's move events after an epoch-millisecond timestamp, oldest first — drafted, sent, called, answered, done, skipped. Use it to answer "what changed since we last spoke" without re-reading the whole plan. Capped; more says how many were left out.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | integer | no | Epoch milliseconds; 0 for everything. |
| limit | integer | no | Most recent N of the matches (default 100, max 500). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 PutRoots or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish PutRoots can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.