PutRoots

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

SF move agent: rentals with sources, no-SSN banking routes, and your move plan and drafts.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "PutRoots": {
      "url": "https://www.putroots.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (11)

• search_listings read-only

  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.

  Parameters:

  • beds — string — Bedroom tier. "room" means a room in a shared place.
  • hood — string — Neighborhood name, matched loosely (e.g. "Mission", "Sunset").
  • limit — integer — How many to return (default 10, max 25). Newest first.
  • max_price — number — 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 — Min monthly rent in USD.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• listing_requirements read-only

  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). It returns no overall verdict, by design.

  Parameters:

  • listing_url (required) — string — The listing's url, exactly as returned by search_listings.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• newcomer_options read-only

  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.

  Parameters:

  • topic (required) — string — bank = checking account, card = credit card, sim = phone plan, ssn = the SSN itself.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• start_move

  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.

  Parameters:

  • trigger (required) — string — What set the move off: lease_signed, offer_accepted, relocation_approved, or your own short label.
  • d0 — string — Move-in day, YYYY-MM-DD.
  • to — string — The new address, as one line.
  • stage — string — Which stage of the journey they are in right now, if you know it.
  • profile_seed — object — Reserved. Accepted but not applied yet — the person fills their own profile after signing up.

  Hints: read-only no · destructive no · idempotent not declared · open-world no

• move_plan read-only

  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 unlocked so far. Blocked therefore mixes two things — tasks missing an answer from the person, and tasks whose prerequisites aren't finished so they haven't been generated yet. Report the numbers as given; don't subtract one from another.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• move_tasks read-only

  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 task is marked in flight (we have evidence they already started it); move_task does not carry that flag.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• move_task read-only

  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.

  Parameters:

  • task_id (required) — string — A task id exactly as move_tasks / move_plan returned it.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• move_task_draft

  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: walk tasks (filling a form on a provider's own site) and research tasks (finding candidates, booking a viewing, filling a rental application) have no execution path here yet and will come back saying the task is neither an email nor a call. Those are done in the PutRoots web app; say so rather than retrying. If it comes back blocked, the task is waiting on a field only the person can answer — use move_task_answer, then call this again.

  Parameters:

  • task_id (required) — string — A task id exactly as move_tasks / move_plan returned it.
  • to — string — 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.

  Hints: read-only no · destructive no · idempotent not declared · open-world no

• move_task_answer

  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.

  Parameters:

  • task_id (required) — string — A task id exactly as move_tasks / move_plan returned it.
  • field (required) — string — A field name from the task's missing list.
  • value (required) — string — What the person said. Not inferred, not a placeholder.

  Hints: read-only no · destructive no · idempotent not declared · open-world no

• move_task_defer

  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.

  Parameters:

  • task_id (required) — string — A task id exactly as move_tasks / move_plan returned it.
  • mode (required) — string

  Hints: read-only no · destructive no · idempotent not declared · open-world no

• move_events read-only

  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.

  Parameters:

  • limit — integer — Most recent N of the matches (default 100, max 500).
  • since — integer — Epoch milliseconds; 0 for everything.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.