putroots

endpoint

https://www.putroots.com/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is putroots live?

No — it has stopped answering the hub's checks (checked 26h ago). It answered 84% of checks over the last 30 days.

Is putroots free to use?

Yes — the hub reached it with no key and no payment.

What tools does putroots have?

11 tools: start_move, move_tasks, move_task, move_task_draft, move_task_answer, move_task_defer, listing_requirements, newcomer_options, ….

Is putroots safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• search_listings reads open 10d ago

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435

  {
    "type": "object",
    "properties": {
      "beds": {
        "enum": [
          "room",
          "studio",
          "1",
          "2",
          "3+"
        ],
        "type": "string",
        "description": "Bedroom tier. \"room\" means a room in a shared place."
      },
      "hood": {
        "type": "string",
        "description": "Neighborhood name, matched loosely (e.g. \"Mission\", \"Sunset\")."
      },
      "limit": {
        "type": "integer",
        "maximum": 25,
        "minimum": 1,
        "description": "How many to return (default 10, max 25). Newest first."
      },
      "max_price": {
        "type": "number",
        "description": "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": {
        "type": "number",
        "description": "Min monthly rent in USD."
      }
    },
    "additionalProperties": false
  }

  arguments 35 lines copy
• start_move changes data unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041

  {
    "type": "object",
    "required": [
      "trigger"
    ],
    "properties": {
      "d0": {
        "type": "string",
        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
        "description": "Move-in day, YYYY-MM-DD."
      },
      "to": {
        "type": "string",
        "maxLength": 200,
        "description": "The new address, as one line."
      },
      "stage": {
        "enum": [
          "pre_arrival",
          "housing",
          "move_planning",
          "move_logistics",
          "activate",
          "settle",
          "stabilize"
        ],
        "type": "string",
        "description": "Which stage of the journey they are in right now, if you know it."
      },
      "trigger": {
        "type": "string",
        "maxLength": 60,
        "description": "What set the move off: lease_signed, offer_accepted, relocation_approved, or your own short label."
      },
      "profile_seed": {
        "type": "object",
        "description": "Reserved. Accepted but not applied yet — the person fills their own profile after signing up."
      }
    },
    "additionalProperties": false
  }

  arguments 41 lines copy
• move_tasks reads unknown never probed

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• move_task reads unknown never probed

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "task_id"
    ],
    "properties": {
      "task_id": {
        "type": "string",
        "description": "A task id exactly as move_tasks / move_plan returned it."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• move_task_draft reads unknown never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "task_id"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "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."
      },
      "task_id": {
        "type": "string",
        "description": "A task id exactly as move_tasks / move_plan returned it."
      }
    },
    "additionalProperties": false
  }

  arguments 17 lines copy
• move_task_answer changes data unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223

  {
    "type": "object",
    "required": [
      "task_id",
      "field",
      "value"
    ],
    "properties": {
      "field": {
        "type": "string",
        "description": "A field name from the task's missing list."
      },
      "value": {
        "type": "string",
        "description": "What the person said. Not inferred, not a placeholder."
      },
      "task_id": {
        "type": "string",
        "description": "A task id exactly as move_tasks / move_plan returned it."
      }
    },
    "additionalProperties": false
  }

  arguments 23 lines copy
• move_task_defer changes data unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "required": [
      "task_id",
      "mode"
    ],
    "properties": {
      "mode": {
        "enum": [
          "later",
          "not_applicable",
          "undo"
        ],
        "type": "string"
      },
      "task_id": {
        "type": "string",
        "description": "A task id exactly as move_tasks / move_plan returned it."
      }
    },
    "additionalProperties": false
  }

  arguments 22 lines copy
• listing_requirements reads unknown 10d ago

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "listing_url"
    ],
    "properties": {
      "listing_url": {
        "type": "string",
        "description": "The listing's url, exactly as returned by search_listings."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• newcomer_options reads unknown 10d ago

  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.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "required": [
      "topic"
    ],
    "properties": {
      "topic": {
        "enum": [
          "bank",
          "card",
          "sim",
          "ssn"
        ],
        "type": "string",
        "description": "bank = checking account, card = credit card, sim = phone plan, ssn = the SSN itself."
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• move_plan reads unknown never probed

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• move_events reads unknown never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 500,
        "minimum": 1,
        "description": "Most recent N of the matches (default 100, max 500)."
      },
      "since": {
        "type": "integer",
        "minimum": 0,
        "description": "Epoch milliseconds; 0 for everything."
      }
    },
    "additionalProperties": false
  }

  arguments 17 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.