Tektolo Rental Property
REMOTE · TEKTOLO.COM
Rental property tools for agents: turnover cost estimates and security deposit rules by US state.
Available components
Last scanned (44 minutes ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5511 tokens (~551/item across 10 items; 5 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- “deposit_settlement_settle” added an optional parameter “colorado_post_closing_occupancy” cosmetic
- “deposit_settlement_settle” added an optional parameter “deposit_required_on” cosmetic
- “deposit_settlement_settle” reworded the description of “as_of” cosmetic
- “deposit_settlement_settle” reworded the description of “claim_notice_sent_on” cosmetic
- “deposit_settlement_settle” reworded the description of “county” cosmetic
- “deposit_settlement_settle” reworded the description of “deductions” cosmetic
- “deposit_settlement_settle” reworded the description of “demand_received_on” cosmetic
- “deposit_settlement_settle” reworded the description of “deposit_collected_on” cosmetic
- “deposit_settlement_settle” reworded the description of “deposit_in_separate_account” cosmetic
- “deposit_settlement_settle” reworded the description of “forwarding_address_received_on” cosmetic
- “deposit_settlement_settle” reworded the description of “interest_paid_through” cosmetic
- “deposit_settlement_settle” reworded the description of “interest_rate_percent” cosmetic
- “deposit_settlement_settle” reworded the description of “landlord_filed_action_on” cosmetic
- “deposit_settlement_settle” reworded the description of “lease_end_on” cosmetic
- “deposit_settlement_settle” reworded the description of “lease_signed_or_renewed_on” cosmetic
- “deposit_settlement_settle” reworded the description of “new_tenant_moved_in_on” cosmetic
- “deposit_settlement_settle” reworded the description of “owner_is_natural_person” cosmetic
- “deposit_settlement_settle” reworded the description of “pet_deposit_usd” cosmetic
- “deposit_settlement_settle” reworded the description of “prepaid_rent_usd” cosmetic
- “deposit_settlement_settle” reworded the description of “rent_ordinance_covered” cosmetic
- “deposit_settlement_settle” reworded the description of “renter_notice_served_on” cosmetic
- “deposit_settlement_settle” reworded the description of “returned” cosmetic
- “deposit_settlement_settle” reworded the description of “small_landlord” cosmetic
- “deposit_settlement_settle” reworded the description of “statement_sent_on” cosmetic
- “deposit_settlement_settle” reworded the description of “tenancy_ended_on” cosmetic
- “deposit_settlement_settle” reworded the description of “tenancy_type” cosmetic
- “deposit_settlement_settle” reworded the description of “tenant_abandoned” cosmetic
- “deposit_settlement_settle” reworded the description of “tenant_age_60_plus” cosmetic
- “deposit_settlement_settle” reworded the description of “tenant_gave_forwarding_address” cosmetic
29 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 25 Oct 26 +1
- “property_turnover_quick_estimate” added an optional parameter “pets” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 23 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “property_turnover_issue_codes” rewrote its description, which is the text the model reads security
- Tool “property_turnover_quick_estimate” rewrote its description, which is the text the model reads security
- Tool “property_turnover_scope” rewrote its description, which is the text the model reads security
- “deposit_settlement_settle” added an optional parameter “county” cosmetic
- “deposit_settlement_settle” added an optional parameter “deposit_in_separate_account” cosmetic
- “deposit_settlement_settle” added an optional parameter “landlord_filed_action_on” cosmetic
- “deposit_settlement_settle” added an optional parameter “owner_is_natural_person” cosmetic
- “deposit_settlement_settle” added an optional parameter “renter_notice_served_on” cosmetic
- “property_turnover_issue_codes” added an optional parameter “group” cosmetic
- “property_turnover_issue_codes” added an optional parameter “q” cosmetic
- “property_turnover_quick_estimate” added an optional parameter “walk_date” cosmetic
- “deposit_settlement_settle” reworded the description of “prepaid_rent_usd” cosmetic
- “property_turnover_issue_codes” reworded the description of “area” cosmetic
- “property_turnover_issue_codes” reworded the description of “include_aliases” cosmetic
- “property_turnover_issue_codes” reworded the description of “limit” cosmetic
- “property_turnover_issue_codes” reworded the description of “query” cosmetic
- “property_turnover_quick_estimate” reworded the description of “issues” cosmetic
- “property_turnover_scope” reworded the description of “detail” cosmetic
- “property_turnover_scope” reworded the description of “findings” cosmetic
- “property_turnover_scope” reworded the description of “read” cosmetic
- “property_turnover_scope” reworded the description of “retain” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://tektolo.com/mcp/rental-property
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tektolo.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 8 Oct 2026 | 8 Apr 2027 | RSA 2048 | SHA256-RSA | 3e5a18e1edd11ad1bee5e116a548bd9 |
| SANs: tektolo.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tektolo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tektolo.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tektolo.com/mcp/rental-property | Verified | 200 | |
| http (plaintext) | http://tektolo.com/mcp/rental-property | HTTPS enforced | 301 | https://tektolo.com/mcp/rental-property |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
deposit_settlement_rules Security deposit rules for a state (and city) ~444
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, penalties, the deposit cap and recent changes, with citations. Not for: settling a specific move-out (deposit_settlement_settle does that), evictions, unpaid-rent collection, rent increases or rent control, lease renewal or notice periods, legal advice. Deterministic and source-cited: the same input gives the same result.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional date (YYYY-MM-DD): show the law in force on that day, for a past move-out the day the tenancy ended. Omitted: the current law. |
| audit | boolean | – | Also return the run record and input/result hashes (an audit trail). Default false. |
| city | string | – | Optional city for its overlay (e.g. 'Chicago'). |
| expect_ruleset | string | – | Optional. The ruleset version you built against, as results carry it in provenance.ruleset_version (e.g. 'sd-2026.11.14'), or its sha256: hash. If the rules have changed since, the call fails (nothin… |
| serve_pinned | boolean | – | Optional, with expect_ruleset. True asks us to answer under the ruleset version you named even when the rules have changed since, from that version's signed bundle; the result says so in served_from_… |
| state | string | yes | US state, 2-letter code or name (e.g. 'TX'). |
| Name | Type | Req | Description |
|---|---|---|---|
| client_refs | object|null | – | – |
| deprecation | array|null | – | – |
| input_hash | string|null | – | – |
| links | object|null | – | – |
| reading | object|null | – | – |
| request_hash | string|null | – | – |
| result | object | yes | – |
| result_hash | string|null | – | – |
| review | object|null | – | – |
| run | object|null | – | – |
| signature | object|null | – | – |
{"city":"Chicago","state":"IL"}deposit_settlement_settle Settle a security deposit after move-out ~2,351
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 allowed or not (with depreciation), interest owed, refund due, penalty exposure, a draft itemized statement and a citation for every rule. Not for: legal advice, tenant demand letters, repair cost estimates, pet deposits, rentals outside the US. Deterministic and source-cited: the same input gives the same result.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Date for deadline status; defaults to today (UTC). Send YYYY-MM-DD for repeatable results. |
| audit | boolean | – | Also return the run record and input/result hashes (an audit trail). Default false. |
| building_units | integer | – | Units in the building. Some interest rules depend on it (NY 6+, IL 25+). |
| city | string | – | City, for a city overlay where covered (e.g. 'Chicago'). Optional. |
| claim_notice_sent_on | string | – | Written claim notice sent (YYYY-MM-DD). FL: within 30 days of termination; DC:45. Balance due 30 days after timely notice; late notice does not count. |
| client_refs | object | – | Your own reference ids (e.g. unit_id, job_id). Echoed back, never used. |
| colorado_post_closing_occupancy | boolean | – | Colorado: buyer-landlord bought this residence from seller-tenant; both executed purchase-contract post-closing occupancy before the deposit was required. True confirms all facts; false excludes; nul… |
| contractor_needed | boolean | – | Damage exceeds the deposit and needs a third-party contractor, and you said so in writing in time (Virginia, West Virginia: 15 more days). |
| county | string | – | TN county: act applies over 75,000 population by 2010 census (66-28-102(a)). Inferred from city only if unambiguous. |
| deductions | array | – | Charges to deduct (or the landlord's list). Explicit [] means no deductions and selects shorter periods (MT10 days, AK14); omit when unknown. |
| demand_received_on | string | – | Deposit demand received (YYYY-MM-DD): written in OK; first-class mail in MD (8-203(h)). Starts clocks in AZ/KS/OK/SC/MS. |
| deposit_collected_on | string | – | Collection date; defaults to move_in_on. CA AB12 uses it. CO: proxy only if deposit_required_on is absent; never proves the exception. |
| deposit_in_separate_account | boolean | – | TN 66-28-301(a): deposit-only separate account. No account and no damage listing means none can be kept (c). |
| deposit_required_on | string | – | Colorado cap: date submission was required. Collection, move-out and as_of cannot establish the 2027 exception. |
| deposit_usd | – | yes | Security deposit held, dollars. |
| documentation | object | – | What documentation you have; leave a field out when unknown. |
| expect_ruleset | string | – | Optional. The ruleset version you built against, as results carry it in provenance.ruleset_version (e.g. 'sd-2026.11.14'), or its sha256: hash. If the rules have changed since, the call fails (nothin… |
| forwarding_address_received_on | string | – | Written forwarding address received (YYYY-MM-DD). Can start/hold clocks in TX, CT, IA, MN. |
| furnished | boolean | – | The unit is rented furnished (California before AB 12: 3 months; Kansas: 1.5 months; Delaware: no cap). |
| interest_paid_through | string | – | Interest already paid/credited through this date; accrual starts here (annual-payment rules, e.g. SF/LA/Berkeley/CT/MA). |
| interest_rate_percent | – | – | Annual deposit-bank rate: NJ/ND/NH/NY/PA/Portland; MA uses lesser of bank rate or 5%. Omitted bank rate is unknown. IL 765 ILCS 715 uses published IDFPR rate instead. |
| landlord_filed_action_on | string | – | MI 554.613: date landlord sued for claimed damage (YYYY-MM-DD); sue or return balance within 45 days. Omitted assumes no suit. |
| landlord_units_owned | integer | – | Rental units the landlord owns in all (Arkansas 5 or fewer, Georgia 10 or fewer, with third_party_managed, may be exempt). |
| lease_end_on | string | – | Scheduled lease end (YYYY-MM-DD), if different from actual tenancy end. Lost rent/lease-break charges use it. Deadlines use tenancy_ended_on, else move-out; scheduled end remains a later alternative. |
| lease_return_days | integer | – | 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). |
| lease_signed_or_renewed_on | string | – | Current lease signing/last renewal (YYYY-MM-DD). GA cap from 2024-07-01; MD from 2024-10-01. Defaults move_in_on; warns later renewal may activate cap. |
| lease_term_months | integer | – | Term of the lease in months (0 for month-to-month). Delaware's cap applies to leases of a year or more, New Mexico's to shorter ones. |
| monthly_rent_usd | – | – | Monthly rent, for the deposit cap check. |
| move_in_on | string | – | Tenancy start (YYYY-MM-DD). Used for interest and, when an item's age is unknown, for depreciation. |
| new_tenant_moved_in_on | string | – | Re-rented: new tenant's move-in date (YYYY-MM-DD). Can shorten WV/WI periods; rent overlapping the new tenancy is unrecoverable. |
| new_tenant_rent_usd | – | – | Monthly rent the new tenant pays (with new_tenant_moved_in_on): the rent received for overlapping days is credited against rent claimed for them. |
| nonstandard_provision_signed | boolean | – | Wisconsin: the tenant signed a separate NONSTANDARD RENTAL PROVISIONS document covering the charge (ATCP 134.06(3)(b)); false makes such charges 'no'. |
| owner_is_natural_person | boolean | – | GA 44-7-36 only: true=natural-person owner; false=LLC/corporation/partnership/trust, which cannot claim small-landlord exemption. Omitted: exemption stays an alternative. |
| owner_occupied | boolean | – | The landlord lives in the building (ME, NH, NJ and Chicago exempt small owner-occupied buildings; with building_units). |
| pet_deposit_usd | – | – | Pet portion of deposit_usd: outside caps in MO/AL/ND/Saint Paul; extra cap allowance of 1 month in HI/AK, half in KS, quarter in NE. |
| prepaid_rent_usd | – | – | Advance rent beyond first month, held besides deposit_usd. Counts in AK/AZ/CA/CT/MD/MI/NY caps; earns interest in CT/MA(last-month rent)/MD/Chicago; Minneapolis cap becomes half-month. UT: send only… |
| rent_ordinance_covered | boolean | – | Covered by LA RSO or Berkeley Rent Ordinance: required for their deposit interest. Unknown interest stays beside, not inside, refund. |
| renter_notice_served_on | string | – | UT 57-17-3(3) renter notice served after deadline (YYYY-MM-DD). Owner gets 5 business days to comply (5); no notice means no 57-17-5 relief. |
| returned | object | – | Prior refund/statement and date; timeliness assesses each duty and days late. |
| serve_pinned | boolean | – | Optional, with expect_ruleset. True asks us to answer under the ruleset version you named even when the rules have changed since, from that version's signed bundle; the result says so in served_from_… |
| small_landlord | boolean | – | CA AB 12: natural person or LLC of natural persons, at most 2 properties containing at most 4 units total, tenant not a service member;2 month cap. |
| state | string | yes | US state, 2-letter code (e.g. 'CA'); a state name also works. |
| statement_sent_on | string | – | Itemized statement sent/delivered (YYYY-MM-DD), to assess timeliness; documentation.itemized_statement alone supplies no date. |
| tenancy_ended_on | string | – | Actual tenancy end: lease end, early termination or accepted surrender (YYYY-MM-DD). End-of-tenancy deadlines use this; send a different scheduled end as lease_end_on. Legacy scheduled ends still wor… |
| tenancy_type | string | – | written_lease or at_will. ME 6033(2): written period<=30 days, at-will 21. MA 15 B(4):30 days from move-out(at-will) or lease end(written). Omitted when vacated_on precedes tenancy_ended_on: earlier… |
| tenant_abandoned | boolean | – | Abandoned or evicted: MD 8-203(h) clock starts at written demand; WA 59.18.280 at landlord awareness; LA 9:3251(C) one-month rule excluded. Omitted: inferred from tenant_gave_proper_notice=false. If… |
| tenant_age_60_plus | boolean | – | An occupant is 60+ (NH 540-A:5,I: owner-occupied exemption excluded). tenant_age_62_plus=true implies this. |
| tenant_age_62_plus | boolean | – | The tenant is 62 or older (Connecticut: a one-month cap). |
| tenant_gave_forwarding_address | boolean | – | False: no written forwarding address ever given. May relieve penalties in IL/PA/OH/SC/NH; DE also accepts a lease notice address. forwarding_address_received_on implies true. |
| tenant_gave_proper_notice | boolean | – | A termination notice that meets the statute was given (Alaska: 14 days instead of 30 when nothing is deducted for damage). |
| third_party_managed | boolean | – | A third party manages the unit or collects rent for a fee. |
| vacated_on | string | yes | Day the tenant moved out and returned possession (YYYY-MM-DD). |
| Name | Type | Req | Description |
|---|---|---|---|
| client_refs | object|null | – | – |
| deprecation | array|null | – | – |
| input_hash | string|null | – | – |
| links | object|null | – | – |
| reading | object|null | – | – |
| request_hash | string|null | – | – |
| result | object | yes | – |
| result_hash | string|null | – | – |
| review | object|null | – | – |
| run | object|null | – | – |
| signature | object|null | – | – |
{"as_of":"2026-10-09","deductions":[{"amount_usd":"150","category":"cleaning"},{"amount_usd":"1200","category":"carpet","item_age_years":5}],"deposit_usd":"2000","monthly_rent_usd":"2000","move_in_on":"2023-06-01","state":"CA","vacated_on":"2026-09-30"}property_turnover_issue_codes Look up turnover issue codes ~570
The issue-code catalog for rental-unit turnover findings (group.issue codes such as carpet.pet_urine). Inputs, all optional: q (search words or a code), group (e.g. flooring), limit, include_aliases; query and area are older names for q and group. With no arguments it returns every code in short form (code, name, group, default extent, refer-out). With q it returns the best matches with description, aliases, not_when, rooms and examples. Returns the codes, the match count, every group, and general.manual_quote, the code for a condition no other code fits. Not for: cost estimates, legal or security-deposit questions, work other than rental turnover. Deterministic and source-cited: the same input gives the same result.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Older name for group; use group. |
| audit | boolean | – | Also return the run record and input/result hashes (an audit trail). Default false. |
| client_refs | object | – | Your own reference ids (e.g. unit_id, job_id). Echoed back, never used. |
| expect_ruleset | string | – | Optional. The ruleset version you built against, as results carry it in provenance.ruleset_version (e.g. 'sd-2026.11.14'), or its sha256: hash. If the rules have changed since, the call fails (nothin… |
| group | string | – | Only codes in this group, e.g. 'flooring' or 'walls' (a part of the unit, not a room). `groups` in the answer lists them all. |
| include_aliases | boolean | – | Also return aliases in the short list (search hits always carry them). |
| limit | integer | – | Most codes to return. Default: 8 with q, every code without. |
| q | string | – | Words to search for in the codes, names, aliases, descriptions and examples, e.g. 'pet stain carpet'. Hits come back with full detail. Leave out to list every code in short form. |
| query | string | – | Older name for q; use q. |
| serve_pinned | boolean | – | Optional, with expect_ruleset. True asks us to answer under the ruleset version you named even when the rules have changed since, from that version's signed bundle; the result says so in served_from_… |
| Name | Type | Req | Description |
|---|---|---|---|
| client_refs | object|null | – | – |
| deprecation | array|null | – | – |
| input_hash | string|null | – | – |
| links | object|null | – | – |
| reading | object|null | – | – |
| request_hash | string|null | – | – |
| result | object | yes | – |
| result_hash | string|null | – | – |
| review | object|null | – | – |
| run | object|null | – | – |
| signature | object|null | – | – |
No examples provided.
property_turnover_quick_estimate Quick turnover estimate (start here) ~875
Estimates what it costs to turn over a US rental unit after move-out; the first tool for a turnover estimate. Inputs: a 5-digit ZIP, bedrooms, bathrooms and the issues in plain English (e.g. "stained carpet in both bedrooms"), which may come from the user's photos; optional unit type, size, year built. Returns a priced make-ready estimate: repair tasks by trade with low/expected/high costs for the ZIP, priorities, refer-outs to licensed professionals, assumptions and links. An AI model reads the issues; the answer is a draft listing what it read (reading), and words it cannot place bill nothing. Not for: diagnosing hazards, legal advice on deposits, remodel bids, properties outside the US. The same findings under the same ruleset give the same result; AI never sets a number.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | boolean | – | Also return the run record and input/result hashes (an audit trail). Default false. |
| bathrooms | – | yes | Half baths count as 0.5. |
| bedrooms | integer | yes | 0 for a studio. |
| carpet | boolean | – | Is there wall-to-wall carpet? |
| client_refs | object | – | Your own reference ids (e.g. unit_id, job_id). Echoed back, never used. |
| detail | string | – | summary (default, small) or full (every line). |
| expect_ruleset | string | – | Optional. The ruleset version you built against, as results carry it in provenance.ruleset_version (e.g. 'sd-2026.11.14'), or its sha256: hash. If the rules have changed since, the call fails (nothin… |
| issues | array | – | What was found in plain English, e.g. ['stained carpet in both bedrooms', 'nail holes everywhere', 'oven is filthy']. Read like pasted notes: an entry may hold several conditions ('carpet stained, na… |
| pets | boolean | – | Did pets live in the unit? true adds an optional flea treatment. |
| price_tier | string | – | bulk_contract (portfolio contract prices) | pm_vendor (default: a property manager buying turns from local vendors) | retail_one_off (an owner hiring one contractor). |
| profile | string | – | minimum (rent-ready basics) | standard | premium (higher finish). |
| retain | boolean | – | Optional (contract 0.5.1). false: keep none of this request's text, so the AI reader's answer for the issues is not stored either. By default the text is kept with contact details and access codes re… |
| serve_pinned | boolean | – | Optional, with expect_ruleset. True asks us to answer under the ruleset version you named even when the rules have changed since, from that version's signed bundle; the result says so in served_from_… |
| sq_ft | integer | – | Interior sq ft. |
| unit_type | string | – | Single-family homes and townhomes get house-sized defaults (floor area, locks). |
| walk_date | string | – | The walk-through date; dated or aged items are judged against it. Omit if unknown. |
| year_built | integer | – | Drives lead-paint (pre-1978) handling. |
| zip | string | yes | The user's 5-digit US ZIP code. If it is missing or not exactly 5 digits, ask the user; never guess, pad or correct it. |
| Name | Type | Req | Description |
|---|---|---|---|
| client_refs | object|null | – | – |
| deprecation | array|null | – | – |
| input_hash | string|null | – | – |
| links | object|null | – | – |
| reading | object|null | – | – |
| request_hash | string|null | – | – |
| result | object | yes | – |
| result_hash | string|null | – | – |
| review | object|null | – | – |
| run | object|null | – | – |
| signature | object|null | – | – |
{"bathrooms":1,"bedrooms":2,"issues":["stained carpet in both bedrooms","nail holes everywhere","oven is filthy"],"zip":"43215"}property_turnover_scope Scope a property turnover ~595
Turns move-out inspection findings for a US rental unit into a priced make-ready scope. For a first estimate use property_turnover_quick_estimate (plain words). Inputs: property (ZIP, bedrooms, bathrooms, optional details) and findings, each an issue code from property_turnover_issue_codes with rooms, status, quantity and the original words (source_text); optional rate_card, decisions, detail. Returns tasks by trade, low/expected/high costs, priorities, vendor scopes, refer-outs, assumptions, unknowns and download links. Not for: diagnosing hazards, legal advice on deposits, remodel bids, properties outside the US. Deterministic and source-cited: the same input gives the same result.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | boolean | – | Also return the run record and input/result hashes (an audit trail). Default false. |
| client_refs | object | – | Your own reference ids (e.g. unit_id, job_id). Echoed back, never used. |
| constraints | object | – | Target ready date, whether the unit is occupied, access notes. |
| decisions | array | – | Approve, decline or defer lines or findings from an earlier scope. |
| detail | string | – | summary (small): totals, trade scopes, lines tied to findings. full: all. |
| expect_ruleset | string | – | Optional. The ruleset version you built against, as results carry it in provenance.ruleset_version (e.g. 'sd-2026.11.14'), or its sha256: hash. If the rules have changed since, the call fails (nothin… |
| findings | array | – | Move-out inspection findings, one per observed condition, coded. |
| property | object | yes | The unit: ZIP, size, type and year built. |
| rate_card | array | – | Your own prices by trade or task; they replace the regional library prices. |
| read | string | – | Deprecated and ignored: scope reads no free text. |
| retain | boolean | – | false: keep none of this request's text. |
| serve_pinned | boolean | – | Optional, with expect_ruleset. True asks us to answer under the ruleset version you named even when the rules have changed since, from that version's signed bundle; the result says so in served_from_… |
| standards | object | – | Finish profile, price tier and overrides. |
| tax_rate | – | – | Applied to all lines, e.g. 0.07. |
| trade_vendors | object | – | Vendor (name, contact) to put on each trade's lines. |
| Name | Type | Req | Description |
|---|---|---|---|
| client_refs | object|null | – | – |
| deprecation | array|null | – | – |
| input_hash | string|null | – | – |
| links | object|null | – | – |
| reading | object|null | – | – |
| request_hash | string|null | – | – |
| result | object | yes | – |
| result_hash | string|null | – | – |
| review | object|null | – | – |
| run | object|null | – | – |
| signature | object|null | – | – |
{"findings":[{"code":"carpet.pet_urine","rooms":"Bedroom 2","source_text":"pet urine in BR2 carpet"},{"code":"blinds.bent_missing","quantity":{"uom":"each","value":3}}],"property":{"bathrooms":1,"bedrooms":2,"zip":"43215"}}How do I install the Tektolo Rental Property MCP server?
Tektolo Rental Property is a hosted endpoint at https://tektolo.com/mcp/rental-property, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tektolo.com
claude mcp add --transport http com-tektolo-rental-property 'https://tektolo.com/mcp/rental-property'
What is the Tektolo Rental Property MCP server?
Tektolo Rental Property is an MCP server listed in the public MCP registry as com.tektolo/rental-property. Rental property tools for agents: turnover cost estimates and security deposit rules by US state. This page covers its hosted endpoint (https://tektolo.com/mcp/rental-property).
Is the Tektolo Rental Property MCP server safe to use?
Tektolo Rental Property scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tektolo Rental Property MCP server expose?
Tektolo Rental Property exposes 5 tools: deposit_settlement_settle, deposit_settlement_rules, property_turnover_quick_estimate, property_turnover_scope, property_turnover_issue_codes. Their descriptions and schemas cost roughly 4,835 tokens of context every time the server is loaded.
Does the Tektolo Rental Property MCP server require authentication?
No. We connected to Tektolo Rental Property without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tektolo Rental Property MCP server still maintained?
Tektolo Rental Property is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.