Skip to content

PutRoots MCP server

com.putroots/putrootsputroots.comstreamable-httpv1.0.1Scanned

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

11 tools: 2 do something that can't be undone, 8 change things and 1 only read.

Tools: 0 delete, 2 irreversible, 8 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • 4 findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

10 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the PutRoots MCP server can do

The PutRoots MCP server is published by putroots.com, a domain the MCP Registry verified. It has 11 tools. It can do things that cannot be undone, such as sending, paying or publishing (start_move and move_task_draft) and create or change data (8 tools: listing_requirements, newcomer_options, move_plan, move_tasks and 4 more), but cannot delete data. 1 tool only reads.

2 tools can send data out of your system (start_move and move_task_draft).

The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.

Last scanned Nov 1, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Can't be undone 2Claude Code: ask
  • move_task_draftPrepares one task for the signed-in person and stops.Can send data outNo findings

    Why it is in this group

    • The name "move_task_draft" says "move": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote 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: 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.

    Annotations the server declares

    • title: Prepare a task (draft only — never sends)
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • start_moveWhen 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 …Can send data outNo findings

    Why it is in this group

    • The name "start_move" says "start": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Hand a mover over to PutRoots (a link, nothing created)
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Changes things 8Claude Code: ask
  • listing_requirementsFor 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: This listing's requirements vs. the renter, line by line
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • move_eventsThe signed-in person's move events after an epoch-millisecond timestamp, oldest first — drafted, sent, called, answered, done, skipped.1 finding

    Why it is in this group

    • The name "move_events" says "move": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "move_events" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "move_events" says "move": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: What has happened on this move since a given moment
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • move_planThe 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 …1 finding

    Why it is in this group

    • The name "move_plan" says "move": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "move_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "move_plan" says "move": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Where this move stands, in five numbers
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • move_taskOne 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.1 finding

    Why it is in this group

    • The name "move_task" says "move": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "move_task" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "move_task" says "move": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: One task's current state
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • move_task_answerFills 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).No findings

    Why it is in this group

    • The name "move_task_answer" says "move": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Answer one field a task is waiting on
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • move_task_deferlater = push it out; it comes back on its own in three days.No findings

    Why it is in this group

    • The name "move_task_defer" says "move": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Put a task off, or rule it out
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • move_tasksWhat 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.1 finding

    Why it is in this group

    • The name "move_tasks" says "move": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "move_tasks" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "move_tasks" says "move": a word for a change.

      What this check looks for
    Description, as the server wrote 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.

    Annotations the server declares

    • title: The one thing to do next, and the few after it
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • newcomer_optionsThe 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 a…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Bank account / phone plan / SSN, for someone with no SSN yet
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • search_listingsSearch PutRoots' San Francisco rental index.No findings

    Why it is in this group

    • The name "search_listings" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search SF rentals, with provenance
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
502
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 502.

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 502
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://www.putroots.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://www.putroots.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

4 warn
  • The server marks "move_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "move_plan" says "move": a word for a change.

    What this check looks for
  • The server marks "move_tasks" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "move_tasks" says "move": a word for a change.

    What this check looks for
  • The server marks "move_task" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "move_task" says "move": a word for a change.

    What this check looks for
  • The server marks "move_events" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "move_events" says "move": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 502; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 10 -> 0 (and 5 more).View diff
    • HTTP status of an anonymous initialize: 200 to 502
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://www.putroots.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://www.putroots.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__putroots__search_listings"
    ],
    "ask": [
      "mcp__putroots__listing_requirements",
      "mcp__putroots__newcomer_options",
      "mcp__putroots__start_move",
      "mcp__putroots__move_plan",
      "mcp__putroots__move_tasks",
      "mcp__putroots__move_task",
      "mcp__putroots__move_task_draft",
      "mcp__putroots__move_task_answer",
      "mcp__putroots__move_task_defer",
      "mcp__putroots__move_events"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as putroots. Review it before you use it.

Capability tags behind 2 rules
  • mcp__putroots__start_move outbound
  • mcp__putroots__move_task_draft outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.putroots/putroots/verify?hash=72b068c3076497a0e2c118552bd04137295394847cedab4c1607543cf88ee8b2" | jq -e '.changed == false'

Pinned hash 72b068c30764, from Nov 1, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.putroots/putroots/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.putroots/putroots
[![Anlyon Radar](https://radar.anlyon.com/badge/com.putroots/putroots.svg)](https://radar.anlyon.com/servers/com.putroots/putroots)

Source: MCP Registry. Synced Oct 21, 2026, 18:01 UTC.

PutRoots MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PutRoots MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 10 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PutRoots MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PutRoots MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: start_move and move_task_draft.

What tools does the PutRoots MCP server have?

11 tools: 2 irreversible, 8 write, 1 read. start_move, move_task_draft, listing_requirements, newcomer_options, move_plan, move_tasks, move_task, move_task_answer and 3 more.

Does the PutRoots MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the PutRoots MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): start_move and move_task_draft.

Has the PutRoots MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 1, 2026.