General Tools
putroots.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://www.putroots.com/mcp
MCP server metadata
- Name
- putroots
- Version
- 1.0.1
PutRoots is the renter's side of a San Francisco rental search: listings with provenance, and each listing's stated requirements compared line by line against the renter's own qualifications. For a signed-in person it is also their move: the one thing to do next, where the whole move stands, and drafting the letters and calls it takes. Four rules when relaying our output: 1. We never answer "you qualify" or "you don't". Each line says what the landlord wrote, what the renter filled in, and the gap. Do not collapse that into a verdict of your own. 2. "Not stated" is an answer. Most landlords state no requirements at all; for those, requirements are a question to ask, not something anyone knows. Do not fill the blank from general knowledge. 3. Every row carries where it came from and when we last saw it. Keep the source and the date attached when you quote it. 4. We prepare, the person presses send. Nothing here sends an email, places a call, submits a form or pays: there is no tool for it and there will not be one. Show them the draft and tell them to press send in PutRoots.
Known tools 11
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.
Inferred read-onlynewcomer_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 an SSN or US credit history.
Inferred read-onlystart_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 to you.
Inferred read-onlymove_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 many are overdue, plus the critical path.
Inferred read-onlymove_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.
Inferred read-onlymove_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.
Inferred read-onlymove_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).
Inferred read-onlymove_eventsThe signed-in person's move events after an epoch-millisecond timestamp, oldest first — drafted, sent, called, answered, done, skipped.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.putroots]
url = "https://www.putroots.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"putroots": {
"type": "http",
"url": "https://www.putroots.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: putroots
Remote MCP URL: https://www.putroots.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"putroots": {
"url": "https://www.putroots.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"putroots": {
"type": "http",
"url": "https://www.putroots.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "putroots",
"transport": "streamable-http",
"url": "https://www.putroots.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.