RentCast MCP Server (unofficial)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_propertiesA | Search RentCast's property records database — the underlying county/MLS-sourced record for real US homes (NOT active listings; use list_active_listings for what's for sale/rent). Filter by a single address, or by a city+state, a zip code, or a lat/long + radius, then narrow with propertyType, bedrooms, bathrooms, or square footage. Returns a summarized list of matching properties (id, address, type, beds/baths, square footage, year built, last sale). Use the returned |
| get_property_detailsA | Fetch the FULL record for a single property — all structural attributes (type, beds, baths, square footage, lot size, year built), features, tax assessments and amounts, last sale price/date, and owner info where available. Look a property up either by its RentCast |
| get_rent_estimateA | Estimate the fair-market LONG-TERM monthly rent for a property using RentCast's AVM (automated valuation model). Give an address, or a lat/long. For the sharpest estimate, also pass the property's propertyType, bedrooms, bathrooms, and squareFootage — or set lookup_subject_attributes=true to have RentCast look those up automatically before estimating. Returns the point rent estimate plus a low–high range (all USD per month) and the top comparable rentals the model used (address, rent, beds/baths, square footage, distance in miles). This is the core valuation tool — pair it with get_market_stats to compare an estimate against the zip-code average, or call it per-listing to rank rental opportunities. |
| get_value_estimateA | Estimate the current SALE (market) value of a property using RentCast's AVM. This is the sale-price counterpart to get_rent_estimate. Give an address or a lat/long; optionally pass the subject's propertyType, bedrooms, bathrooms, and squareFootage, or set lookup_subject_attributes=true to have RentCast fill them in. Returns the point value estimate plus a low–high range (all USD) and the top comparable SALES the model used (address, price, beds/baths, square footage, distance in miles). Use to gauge what a property is worth, to compute a rent-to-value / gross-yield ratio alongside get_rent_estimate, or to sanity-check a list price. |
| get_market_statsA | Get aggregate market statistics and trends for a ZIP CODE — average and median sale price, average and median rent, price/rent per square foot, average days on market, and listing counts. Use this to establish the local baseline: e.g. compare a single property's get_rent_estimate against the zip's average rent, or gauge whether an area is hot (low days-on-market, many new listings). Choose data_type to get sale stats, rental stats, or both. All prices are USD; rents are USD/month. Returns a summarized snapshot; if RentCast has too little data for a zip, the corresponding sale or rental block is omitted. |
| list_active_listingsA | List CURRENTLY ACTIVE sale or rental listings for an area — the real, on-market inventory (unlike search_properties, which searches historical property records). Set listing_type to 'sale' or 'rental' to choose the market. Scope by city+state and/or zip code, and filter by bedrooms, bathrooms, and property type. Returns a summarized list (id, address, price, beds/baths, square footage, days on market, status), most recently seen first. Prices are USD (a total sale price for 'sale', a monthly rent for 'rental'). NOTE: RentCast does not filter by price server-side — request the listings, then filter/rank by the returned |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a clearly distinct purpose: searching property records, fetching full property details, estimating rent, estimating sale value, getting market stats, and listing active listings. The descriptions explicitly contrast related tools (e.g., search_properties vs. list_active_listings) so an agent will not confuse them.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_property_details, search_properties, get_rent_estimate, get_value_estimate, get_market_stats, list_active_listings. The verbs vary (get, search, list) but the style is uniform and predictable.
Six tools is well-scoped for a real estate data API, covering search, details, valuation, market stats, and listings without unnecessary bloat. Each tool has a concrete role, and the count feels appropriate for the domain.
The tool set covers the core workflows: lookup a property (search_properties), get its full record (get_property_details), estimate rent and value, compare against market stats, and find active listings. There are no obvious dead ends; listings feed into estimates via the returned addresses, and stats provide context.