mcpbeat

Realtystack MCP Server

io.github.IsaiahDupree/realtystack-mcp
answering

Realtystack MCP is answering right now. Last checked 4 min ago. It exposes 6 tools. Last commit 1 Aug 2026.

U.S. real-estate data: property records, AVM value + rent estimates, sale/rental listings.

Uptime history 39 hours of history · worst hour 25%
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
254 ms
Response time
average over 24h
0
Stars
last commit 1 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add realtystack-mcp --transport http https://realtystack-mcp.vercel.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "realtystack-mcp": {
      "url": "https://realtystack-mcp.vercel.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.realtystack-mcp]
url = "https://realtystack-mcp.vercel.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "realtystack-mcp": {
      "url": "https://realtystack-mcp.vercel.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "realtystack-mcp": {
      "url": "https://realtystack-mcp.vercel.app/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

avm
avm_rent
Run RentCast's automated model for long-term (12-month lease) rent and return a point rent estimate, a rentRangeLow/rentRangeHigh band, the resolved subjectProperty, and comparables[] — recent comparable rentals each scored with distance and correlation. Same subject-pinning rules as avm_value (address or latitude+longitude, plus optional subject attributes). Cached 6h upstream.
avm_value
Run RentCast's automated valuation model for a subject property and return a point price estimate, a priceRangeLow/priceRangeHigh band, the resolved subjectProperty, and comparables[] — recent comparable sales each scored with a distance (miles) and correlation (0-1 similarity). Pin the subject with either address or latitude+longitude; when subject attributes are unknown, supply propertyType/bedrooms/bathrooms/squareFootage (or leave lookupSubjectAttributes true to have RentCast fill them). Cached 6h upstream.
properties
search_properties
Search normalized U.S. property records (owner, structural attributes, tax assessments, tax + sale history) by location. Pin a location one of three ways: a full address, a city+state(+zipCode), or a latitude+longitude point with a radius (miles). All other parameters narrow the result set. Records are cached 24h upstream, so meta.cached may be true on repeat queries.
property
get_property
Full detail for a single property record, keyed by its RentCast id (the same id returned on every search_properties, avm_value, avm_rent, and listings record). Returns 404 if no property matches the id. Cached 24h upstream.
rental
search_rental_listings
Return a page of long-term (12-month lease) rental listings — same record shape as search_sale_listings (monthly price is the asking rent), but each record is tagged listingKind:"rental-long-term". Same location-pinning rules and 30-minute upstream cache as the sale-listings endpoint.
sale
search_sale_listings
Return a page of for-sale listings (list price, status, days on market, MLS name/number, listing agent + office contact, and price/status history) for a location. Same location-pinning rules as search_properties (address, city+state(+zipCode), or latitude+longitude+radius). Each record is tagged listingKind:"sale". Listings move faster than records, so these are cached only 30 minutes upstream.

Endpoints

URLTransportStateLatencyChecked
https://realtystack-mcp.vercel.app/mcp streamable-http answering 224 ms 4 min ago

Realtystack MCP — questions

Answers built from our own checks of this server.

What can Realtystack MCP do?
It exposes 6 tools, read directly from the server on our last check. Among them: avm_rent, avm_value, get_property, search_properties, search_rental_listings, search_sale_listings. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Realtystack MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 254 ms. The bar chart above shows every period we have measured.
How do I connect Realtystack MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Realtystack MCP need an API key?
No. Realtystack MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Realtystack MCP?
It answers our handshake in 254 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Realtystack MCP open source?
Yes — written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.