此 MCP 可以做什么
Helps users search San Francisco rentals, compare listing requirements, manage move tasks, prepare drafts, and find relocation-related banking and phone options.
功能
工具
11
工具
listing_requirements
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.
只读
输入模式
{'type': 'object', 'required': ['listing_url'], 'properties': {'listing_url': {'type': 'string', 'description': "The listing's url, exactly as returned by search_listings."}}, 'additionalProperties': False}
输出模式
{'type': 'object', 'required': ['listing', 'price', 'source', 'items'], 'properties': {'items': {'type': 'array', 'items': {'type': 'object', 'required': ['key', 'label', 'status', 'required', 'yours', 'detail'], 'properties': {'key': {'type': 'string'}, 'src': {'type': ['string', 'null'], 'description': "The landlord's own sentence this line was read from."}, 'label': {'type': 'string'}, 'yours': {'type': ['string', 'null'], 'description': 'What the renter filled in (null = not filled in).'}, 'detail': {'type': 'string'}, 'status': {'enum': ['meets', 'info', 'gap', 'unknown_user', 'unknown_landlord'], 'type': 'string'}, 'blocking': {'type': 'boolean'}, 'required': {'type': ['string', 'null'], 'description': 'What the landlord wrote (null = not stated).'}}}}, 'price': {'type': ['number', 'null']}, 'source': {'type': 'object', 'required': ['kind', 'from', 'fetched_at'], 'properties': {'from': {'type': 'string'}, 'kind': {'enum': ['landlord_rules', 'listing_text'], 'type': 'string'}, 'name': {'type': ['string', 'null']}, 'fetched_at': {'type': ['number', 'string', 'null'], 'description': 'Epoch ms for landlord rules; ISO date for listing text.'}, 'fetched_from': {'type': ['string', 'null']}}}, 'listing': {'type': 'string'}, 'summary': {'anyOf': [{'type': 'object', 'properties': {'met': {'type': 'integer'}, 'gaps': {'type': 'integer'}, 'info': {'type': 'integer'}, 'askYou': {'type': 'integer'}, 'askLandlord': {'type': 'integer'}}}, {'type': 'null'}]}, 'triage_tier': {'type': ['string', 'null']}}}
move_events
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.
只读
输入模式
{'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}
输出模式
{'type': 'object', 'required': ['ok', 'since', 'events', 'more'], 'properties': {'ok': {'type': 'boolean'}, 'more': {'type': 'integer'}, 'since': {'type': 'integer'}, 'events': {'type': 'array', 'items': {'type': 'object', 'required': ['ts', 'type'], 'properties': {'ts': {'type': 'integer'}, 'type': {'type': 'string'}, 'detail': {'type': 'object'}}}}}}
move_plan
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.
只读
输入模式
{'type': 'object', 'properties': {}, 'additionalProperties': False}
输出模式
{'type': 'object', 'required': ['ok', 'd0', 'days_to_d0', 'total', 'done', 'actionable', 'blocked', 'overdue', 'critical_path', 'health'], 'properties': {'d0': {'type': 'string'}, 'ok': {'type': 'boolean'}, 'done': {'type': 'integer', 'description': 'Settled: done, sent, called, replied or marked not applicable (full ruler).'}, 'total': {'type': 'integer', 'description': 'Every task in this move (full ruler).'}, 'health': {'type': 'object', 'properties': {'ok': {'type': 'boolean'}, 'line': {'type': 'string'}}}, 'blocked': {'type': 'integer', 'description': 'total - done - actionable: tasks missing an answer AND tasks not yet unlocked, together.'}, 'overdue': {'type': 'integer', 'description': 'Past due, not in flight, not blocked (unlocked ruler).'}, 'actionable': {'type': 'integer', 'description': 'Unlocked and not waiting on an answer (unlocked ruler).'}, 'days_to_d0': {'type': 'integer'}, 'critical_path': {'type': 'object', 'properties': {'ids': {'type': 'array', 'items': {'type': 'string'}}, 'first': {'type': ['string', 'null']}, 'blocks': {'type': 'integer'}, 'remaining': {'type': 'integer'}}}}}
move_task
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.
只读
输入模式
{'type': 'object', 'required': ['task_id'], 'properties': {'task_id': {'type': 'string', 'description': 'A task id exactly as move_tasks / move_plan returned it.'}}, 'additionalProperties': False}
输出模式
{'type': 'object', 'required': ['ok', 'id', 'title', 'kind', 'actor', 'due', 'dlabel', 'due_day', 'state'], 'properties': {'id': {'type': 'string'}, 'ok': {'type': 'boolean'}, 'due': {'type': 'integer'}, 'kind': {'type': 'string'}, 'actor': {'type': 'string'}, 'draft': {'type': 'object', 'description': 'Prepared, never sent.'}, 'state': {'type': 'string'}, 'title': {'type': 'string'}, 'dlabel': {'type': 'string'}, 'due_day': {'type': 'string'}, 'missing': {'type': 'array', 'items': {'type': 'string'}}, 'missing_text': {'type': 'array', 'items': {'type': 'string'}}}}
move_task_answer
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.
输入模式
{'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}
输出模式
{'type': 'object', 'required': ['ok', 'id', 'field'], 'properties': {'id': {'type': 'string'}, 'ok': {'type': 'boolean'}, 'field': {'type': 'string'}, 'state': {'type': ['string', 'null']}, 'closeout': {'type': 'object'}}}
move_task_defer
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.
输入模式
{'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}
输出模式
{'type': 'object', 'required': ['ok', 'state'], 'properties': {'ok': {'type': 'boolean'}, 'state': {'type': 'string'}, 'later_until': {'type': 'integer'}}}
move_task_draft
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.
输入模式
{'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}
输出模式
{'type': 'object', 'required': ['ok', 'state'], 'properties': {'ok': {'type': 'boolean'}, 'draft': {'type': 'object', 'description': 'to / subject / body, or the call script. Prepared, not sent.'}, 'state': {'type': 'string', 'description': 'drafted = ready for them to press send; blocked = waiting on an answer.'}, 'missing': {'type': 'array', 'items': {'type': 'string'}}, 'missing_text': {'type': 'array', 'items': {'type': 'string'}}}}
move_tasks
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.
只读
输入模式
{'type': 'object', 'properties': {}, 'additionalProperties': False}
输出模式
{'type': 'object', 'required': ['hero', 'rows', 'moreCount'], 'properties': {'hero': {'anyOf': [{'type': 'object', 'required': ['id', 'title', 'state', 'kind', 'actor', 'due', 'dlabel', 'due_day', 'unlocks'], 'properties': {'id': {'type': 'string'}, 'due': {'type': 'integer'}, 'kind': {'type': 'string', 'description': "How it gets done: email, call, walk (fill a form on someone's site), research (find candidates / book / fill an application), or user (only the person can)."}, 'actor': {'type': 'string', 'description': 'agent = we can do it for them; user = only they can.'}, 'state': {'type': 'string', 'description': 'todo / blocked / drafted / approved / sent / called / replied / done / skipped.'}, 'title': {'type': 'string'}, 'dlabel': {'type': 'string'}, 'due_day': {'type': 'string'}, 'missing': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Field names this task is waiting on — pass one to move_task_answer.'}, 'unlocks': {'type': 'integer', 'description': "How many tasks that don't exist yet would appear once this one is finished."}, 'in_flight': {'type': 'boolean', 'description': 'Evidence says they already started it, so it is not overdue and never the next thing to press.'}, 'overdue_days': {'type': 'integer'}}}, {'type': 'null'}], 'description': 'The single next thing, or null with blockedReason set.'}, 'rows': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'title', 'state', 'kind', 'actor', 'due', 'dlabel', 'due_day', 'unlocks'], 'properties': {'id': {'type': 'string'}, 'due': {'type': 'integer'}, 'kind': {'type': 'string', 'description': "How it gets done: email, call, walk (fill a form on someone's site), research (find candidates / book / fill an application), or user (only the person can)."}, 'actor': {'type': 'string', 'description': 'agent = we can do it for them; user = only they can.'}, 'state': {'type': 'string', 'description': 'todo / blocked / drafted / approved / sent / called / replied / done / skipped.'}, 'title': {'type': 'string'}, 'dlabel': {'type': 'string'}, 'due_day': {'type': 'string'}, 'missing': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Field names this task is waiting on — pass one to move_task_answer.'}, 'unlocks': {'type': 'integer', 'description': "How many tasks that don't exist yet would appear once this one is finished."}, 'in_flight': {'type': 'boolean', 'description': 'Evidence says they already started it, so it is not overdue and never the next thing to press.'}, 'overdue_days': {'type': 'integer'}}}}, 'moreCount': {'type': 'integer'}, 'blockedReason': {'type': ['string', 'null'], 'description': 'no_move / nothing_open / all_in_flight — why there is no next thing.'}}}
newcomer_options
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.
只读
输入模式
{'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}
输出模式
{'type': 'object', 'required': ['topic', 'places', 'places_total', 'options'], 'properties': {'topic': {'type': 'string'}, 'places': {'type': 'array', 'items': {'type': 'object', 'description': 'A branch / store: name, addr, tel, hours, the no-SSN line with its source.'}}, 'options': {'type': 'array', 'items': {'type': 'object', 'description': 'A no-branch option: name, stance (official page) and firsthand stance, facts, url, source.'}}, 'prefNote': {'type': ['string', 'null']}, 'prefScope': {'type': ['string', 'null']}, 'places_total': {'type': 'integer'}}}
search_listings
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.
只读
输入模式
{'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}
输出模式
{'type': 'object', 'required': ['gated', 'total', 'searched', 'matched', 'listings'], 'properties': {'gated': {'type': 'boolean', 'description': 'true = free sample only (anonymous or partner key); total still tells the true index size.'}, 'total': {'type': 'integer'}, 'matched': {'type': 'integer'}, 'listings': {'type': 'array', 'items': {'type': 'object', 'required': ['url', 'price', 'source', 'requirements_stated'], 'properties': {'url': {'type': 'string'}, 'beds': {'type': ['string', 'null']}, 'hood': {'type': ['string', 'null']}, 'price': {'type': ['number', 'null']}, 'title': {'type': ['string', 'null']}, 'posted': {'type': ['string', 'null']}, 'source': {'type': ['string', 'null']}, 'last_seen': {'type': ['string', 'null']}, 'requirements_stated': {'type': 'boolean'}, 'not_checked_vs_budget': {'type': 'boolean'}}}}, 'searched': {'type': 'integer'}, 'not_checked_vs_budget': {'type': 'integer'}, 'listings_with_no_stated_requirements': {'type': 'integer'}}}
start_move
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.
输入模式
{'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}
输出模式
{'type': 'object', 'required': ['id', 'url', 'partner', 'trigger', 'dry_run'], 'properties': {'d0': {'type': ['string', 'null']}, 'id': {'type': 'string'}, 'to': {'type': ['string', 'null']}, 'url': {'type': 'string'}, 'stage': {'type': ['string', 'null']}, 'dry_run': {'type': 'boolean', 'description': 'true when called with a pr_test_ key.'}, 'partner': {'type': 'string'}, 'trigger': {'type': 'string'}}}
历史
近期工具变更
已添加
move_events
2026年9月26日 02:40
已添加
move_task_defer
2026年9月26日 02:40
已添加
move_task_answer
2026年9月26日 02:40
已添加
move_task_draft
2026年9月26日 02:40
已添加
move_task
2026年9月26日 02:40
已添加
move_tasks
2026年9月26日 02:40
已添加
move_plan
2026年9月26日 02:40
已添加
start_move
2026年9月26日 02:40
已添加
newcomer_options
2026年9月26日 02:40
已添加
listing_requirements
2026年9月26日 02:40
已添加
search_listings
2026年9月26日 02:40
发现
类似的 MCP 服务器
Enel SP: Gestão Imobiliária
io.github.mcp-dir/contas_enel_sp_gestao_imob-mcp
Supports Enel São Paulo utility account lookups for property management workflows.
freedom-mcp
com.getfreedomos/freedom-mcp
Supports company operations through commitments, teams, agents, customer evidence, leads, content workflows, spreadsheets, commer…
Calcgrid
com.tttkmbb/calcgrid
Runs general-purpose calculators for loans, dates, lunar and solar terms, time zones, units, and a larger catalog of specialized …
Local MCP
com.local-mcp/local-mcp
Connects AI assistants to Mac email, calendars, reminders, notes, tasks, files, Microsoft 365, Todoist, spreadsheets, and daily b…
Stable Baseline
io.stablebaseline/sb
Manages company documents, knowledge graphs, whiteboards, projects, plans, tasks, teams, and improvement workflows.
hopi
uk.co.hopi/hopi
Provides read-only calculators, converters, validators, text utilities, encoders, and generators for everyday and technical tasks.
Microburbs Australian Property Data
au.com.microburbs/property-data
Provides Australian property, suburb, valuation, sales, rental, zoning, school, risk, geospatial, and census statistics.
mu
mu.micro/mu
Supports personal and collaborative tasks including web browsing, app creation, blogs, bookmarks, discussions, and contact manage…