RentCast MCP Server

RentCast

RentCast aggregates US rental and sale market data from listings and public records. All tools are read-only GET endpoints.

Data model

• Property records — tax, structure, owner, and sale history for matched addresses.
• Rent estimate (AVM) — long-term monthly rent for one property.
• Value estimate (AVM) — estimated sale price for one property.
• Rental listings — active long-term for-rent inventory in an area.
• Sale listings — active for-sale inventory in an area.
• Market statistics — zip-level medians, inventory, and trend series.

Operational order

1. Single-property underwriting — start with property records when you need tax/owner context, then run rent and/or value estimates on the same full address string.
2. Area comps — use rental or sale listings with zipCode or city+state (optional radius) before quoting individual AVMs.
3. Market pulse — use market statistics when the question is zip-level trends (median rent, inventory); statistics require zipCode only, not a street address.
4. Pagination — property and sale listing searches may return many rows; pass offset from the prior response when continuing a large search.

Selector rules

Optional AVM refinements: propertyType, bedrooms, bathrooms, squareFootage. Statistics optional: dataType (All/Rental/Sale), historyRange (months).

Gotchas

• Calling rent/value estimate or statistics without the required selectors returns HTTP 400 upstream — supply selectors before retrying.
• City names are case-sensitive on area searches.
• Radius is capped at 100 miles when used with address or coordinates.