# PutRoots (remote · www.putroots.com)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `www.putroots.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-putroots-putroots/www.md), [page](https://verifymcp.io/servers/com-putroots-putroots/www)

## Channel facts

- Endpoint: `https://www.putroots.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1863 tokens (~169/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the PutRoots MCP server?

PutRoots is a hosted endpoint at https://www.putroots.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-putroots-putroots 'https://www.putroots.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-putroots-putroots": {
      "url": "https://www.putroots.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-putroots-putroots": {
      "type": "http",
      "url": "https://www.putroots.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-putroots-putroots]
url = "https://www.putroots.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-putroots-putroots": {
      "type": "remote",
      "url": "https://www.putroots.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-putroots-putroots --url 'https://www.putroots.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-putroots-putroots:
    url: "https://www.putroots.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-putroots-putroots": {
      "Transport": "http",
      "Url": "https://www.putroots.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-putroots-putroots -t streamable-http -u 'https://www.putroots.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-putroots-putroots": {
      "type": "http",
      "url": "https://www.putroots.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 72, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-26 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-25 (score 71)

First indexed and scored.

## MCP tools (11)

### `search_listings` (~202 tokens)

Search SF rentals, with provenance

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.

Input 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.

Output parameters:

- `gated` (boolean): true = free sample only (anonymous or partner key); total still tells the true index size.
- `listings` (array)
- `listings_with_no_stated_requirements` (integer)
- `matched` (integer)
- `not_checked_vs_budget` (integer)
- `searched` (integer)
- `total` (integer)

### `listing_requirements` (~125 tokens)

This listing's requirements vs. the renter, line by line

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.

Input parameters:

- `listing_url` (string, required): The listing's url, exactly as returned by search_listings.

Output parameters:

- `items` (array)
- `listing` (string)
- `price` (number|null)
- `source` (object)
- `summary`
- `triage_tier` (string|null)

### `newcomer_options` (~122 tokens)

Bank account / phone plan / SSN, for someone with no SSN yet

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.

Input parameters:

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

Output parameters:

- `options` (array)
- `places` (array)
- `places_total` (integer)
- `prefNote` (string|null)
- `prefScope` (string|null)
- `topic` (string)

### `start_move` (~195 tokens)

Hand a mover over to PutRoots (a link, nothing created)

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.

Input parameters:

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

Output parameters:

- `d0` (string|null)
- `dry_run` (boolean): true when called with a pr_test_ key.
- `id` (string)
- `partner` (string)
- `stage` (string|null)
- `to` (string|null)
- `trigger` (string)
- `url` (string)

### `move_plan` (~136 tokens)

Where this move stands, in five numbers

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.

Output parameters:

- `actionable` (integer): Unlocked and not waiting on an answer (unlocked ruler).
- `blocked` (integer): total - done - actionable: tasks missing an answer AND tasks not yet unlocked, together.
- `critical_path` (object)
- `d0` (string)
- `days_to_d0` (integer)
- `done` (integer): Settled: done, sent, called, replied or marked not applicable (full ruler).
- `health` (object)
- `ok` (boolean)
- `overdue` (integer): Past due, not in flight, not blocked (unlocked ruler).
- `total` (integer): Every task in this move (full ruler).

### `move_tasks` (~115 tokens)

The one thing to do next, and the few after it

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.

Output parameters:

- `blockedReason` (string|null): no_move / nothing_open / all_in_flight — why there is no next thing.
- `hero`: The single next thing, or null with blockedReason set.
- `moreCount` (integer)
- `rows` (array)

### `move_task` (~114 tokens)

One task's current state

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.

Input parameters:

- `task_id` (string, required): A task id exactly as move_tasks / move_plan returned it.

Output parameters:

- `actor` (string)
- `dlabel` (string)
- `draft` (object): Prepared, never sent.
- `due` (integer)
- `due_day` (string)
- `id` (string)
- `kind` (string)
- `missing` (array)
- `missing_text` (array)
- `ok` (boolean)
- `state` (string)
- `title` (string)

### `move_task_draft` (~260 tokens)

Prepare a task (draft only — never sends)

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.

Input parameters:

- `task_id` (string, required): 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.

Output parameters:

- `draft` (object): to / subject / body, or the call script. Prepared, not sent.
- `missing` (array)
- `missing_text` (array)
- `ok` (boolean)
- `state` (string): drafted = ready for them to press send; blocked = waiting on an answer.

### `move_task_answer` (~134 tokens)

Answer one field a task is waiting on

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.

Input parameters:

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

Output parameters:

- `closeout` (object)
- `field` (string)
- `id` (string)
- `ok` (boolean)
- `state` (string|null)

### `move_task_defer` (~114 tokens)

Put a task off, or rule it out

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.

Input parameters:

- `mode` (string, required)
- `task_id` (string, required): A task id exactly as move_tasks / move_plan returned it.

Output parameters:

- `later_until` (integer)
- `ok` (boolean)
- `state` (string)

### `move_events` (~101 tokens)

What has happened on this move since a given moment

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.

Input parameters:

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

Output parameters:

- `events` (array)
- `more` (integer)
- `ok` (boolean)
- `since` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-putroots-putroots/www#diagnostics

## Score history

- 2026-09-28: 72
- 2026-09-27: 72
- 2026-09-26: 71
- 2026-09-25: 71

## Common questions

### What is the PutRoots MCP server?

PutRoots is an MCP server listed in the public MCP registry as com.putroots/putroots. SF move agent: rentals with sources, no-SSN banking routes, and your move plan and drafts. This page covers its hosted endpoint (https://www.putroots.com/mcp).

### Is the PutRoots MCP server safe to use?

PutRoots scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the PutRoots MCP server expose?

PutRoots exposes 11 tools: search_listings, listing_requirements, newcomer_options, start_move, move_plan, and 6 more. Their descriptions and schemas cost roughly 1,618 tokens of context every time the server is loaded.

### Does the PutRoots MCP server require authentication?

No. We connected to PutRoots without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PutRoots MCP server still maintained?

PutRoots is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.putroots.com/mcp
- Website: https://www.putroots.com/connect
- Changelog RSS feed: https://verifymcp.io/servers/com-putroots-putroots/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-putroots-putroots/www.json
- HTML version of this page: https://verifymcp.io/servers/com-putroots-putroots/www