Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Tektolo is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Deterministic, source-cited rental property tools: turnover estimates and deposit rules by US state.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tektolo-mcp https://tektolo.com/mcp
# 2 — ask your agent for something these tools do
# deposit_settlement_settle, deposit_settlement_rules, property_turnover_quick_estimate and 2 more
Tektolo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http tektolo-mcp https://tektolo.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Settles a US residential security deposit after move-out under the state's statute (50 states and DC) and a covered city's ordinance. Inputs: state, deposit_usd, vacated_on; optional city, monthly_rent_usd, move_in_on, deductions (category, amount, item age, whether the tenant caused it), the dates that start a state's clock, and as_of. Returns the return deadline and its status, each deduction al
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_refs | no | Your own reference ids (e.g. unit_id, job_id). Echoed back, never used. | |
| state | string | yes | — |
| city | no | City, for a city overlay where covered (e.g. 'Chicago'). Optional. | |
| deposit_usd | yes | — | |
| monthly_rent_usd | no | Monthly rent, for the deposit cap check. | |
| building_units | no | Units in the building. Some interest rules depend on it (NY 6+, IL 25+). | |
| move_in_on | no | Tenancy start (YYYY-MM-DD). Used for interest and, when an item's age is unknown, for depreciation. | |
| tenancy_ended_on | no | Lease end or termination date (YYYY-MM-DD), if different. | |
| vacated_on | string | yes | — |
| forwarding_address_received_on | no | Day you received the tenant's written forwarding address (YYYY-MM-DD). Several states start or hold the clock on it (Texas, Connecticut, Iowa, Minnesota). | |
| demand_received_on | no | Day you received the tenant's written demand for the deposit (YYYY-MM-DD). Arizona, Kansas, Oklahoma, South Carolina and Mississippi start the clock on it. | |
| new_tenant_moved_in_on | no | Day a new tenant moved in, if the unit was re-rented (YYYY-MM-DD). West Virginia and Wisconsin can end the period earlier. | |
| claim_notice_sent_on | no | Day you sent the written notice of intent to impose a claim on the deposit (YYYY-MM-DD). Florida (due within 30 days of termination) and the District of Columbia (within 45 days): the balance is due 3 | |
| lease_return_days | no | Return period the lease sets, in days, where the statute lets a lease set one (Colorado up to 60, Idaho up to 30, Maine shorter). | |
| tenant_gave_proper_notice | no | A termination notice that meets the statute was given (Alaska: 14 days instead of 30 when nothing is deducted for damage). | |
| contractor_needed | no | Damage exceeds the deposit and needs a third-party contractor, and you said so in writing in time (Virginia, West Virginia: 15 more days). | |
| deductions | array | no | What you intend to deduct (or, for a tenant, what the landlord listed); may be empty. |
| returned | no | What the landlord has returned so far and when. With it, timeliness says whether the refund and the itemized statement were on time and how many days late. | |
| documentation | no | What documentation you have; leave a field out when unknown. | |
| as_of | string | no | Today's date (YYYY-MM-DD) for the deadline status. Defaults to today (UTC); send it for repeatable results. |
Looks up the security deposit rules (deposits only) for one US state, with a covered city's deposit ordinance (Chicago, San Francisco, Berkeley, Los Angeles, Seattle, Portland, Minneapolis, Saint Paul). Inputs: state (two-letter code); optional city. Returns the deposit return deadline and what starts it, itemization and documentation duties, allowed deductions and depreciation, deposit interest,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | — |
| city | no | Optional city for its overlay (e.g. 'Chicago'). | |
| audit | boolean | no | Also return the run record and input/result hashes (an audit trail). Default false. |
Estimates what it costs to turn over a US rental unit after move-out. Inputs: a 5-digit ZIP, bedrooms, bathrooms and the issues in plain English (e.g. "stained carpet in both bedrooms"); optional unit type, size, year built. Returns a priced make-ready estimate: repair tasks by trade with low/expected/high costs for the ZIP's labor market, must/should/could priorities, refer-outs to licensed profe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_refs | no | Your own reference ids (e.g. unit_id, job_id). Echoed back, never used. | |
| zip | string | yes | — |
| bedrooms | integer | yes | — |
| bathrooms | yes | — | |
| issues | array | no | What was found, one plain-English item per entry, e.g. ['stained carpet in both bedrooms', 'nail holes everywhere', 'oven is filthy']. A room at the start sets the location ('Bedroom 2 carpet torn'). |
| unit_type | no | — | |
| sq_ft | no | Interior sq ft. | |
| year_built | no | — | |
| carpet | no | Is there wall-to-wall carpet? | |
| profile | no | — | |
| price_tier | no | — | |
| detail | string | no | summary (default, small) or full (every line). |
| audit | boolean | no | Also return the run record and input/result hashes (an audit trail). Default false. |
Turns move-out inspection findings for a US rental unit into a priced make-ready scope. Inputs: property (ZIP, bedrooms, bathrooms; optional unit type, size, year built) and findings (a plain description or an issue code, with location, extent and quantity); optional rate_card (the manager's own prices), decisions (owner approve/decline) and detail. Returns tasks by trade with regional low/expecte
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_refs | no | Your own reference ids (e.g. unit_id, job_id). Echoed back, never used. | |
| property | yes | — | |
| findings | array | no | — |
| standards | no | — | |
| rate_card | array | no | — |
| trade_vendors | object | no | — |
| constraints | no | — | |
| tax_rate | no | Applied to all lines, e.g. 0.07. | |
| decisions | array | no | — |
| detail | string | no | summary: totals, trade scopes, every line tied to a finding (capped at 40) plus the largest must-fix/refer-out lines, a one-line note on the routine lines left out, notes, and only findings needing at |
| audit | boolean | no | Also return the run record and input/result hashes (an audit trail). Default false. |
Searches the standard taxonomy of rental-unit turnover issues (component.issue codes such as carpet.pet_urine). Inputs, all optional: query (keywords), area (e.g. flooring), limit (default 8). With no arguments it lists the taxonomy areas and the first codes. Returns matching codes with names and areas, and the total match count. Codes are optional: the turnover estimate tools also accept plain de
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_refs | no | Your own reference ids (e.g. unit_id, job_id). Echoed back, never used. | |
| query | no | Keywords to match against codes, names and aliases, e.g. 'pet stain carpet'. | |
| area | no | Optional taxonomy area filter, e.g. 'flooring' or 'walls' (not a room). Call with no arguments to list every area in areas. | |
| limit | integer | no | — |
| include_aliases | boolean | no | Also return each code's aliases (larger result). |
| audit | boolean | no | Also return the run record and input/result hashes (an audit trail). Default false. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tektolo or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Tektolo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.