Realestateapi vs HasData Redfin
A side-by-side look at the Realestateapi and HasData Redfin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Realestateapi for real estate work as a local process; choose HasData Redfin for real estate as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Realestateapi when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You want tools like
realestateapi_property_search, realestateapi_property_detail, realestateapi_skip_trace.
Choose HasData Redfin when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HASDATA_API_KEY. - You want tools like
hasdata_redfin_listing_getRealEstateListings, hasdata_redfin_property_getPropertyDetails.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 59/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | HASDATA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 11 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View Realestateapi | View HasData Redfin |
Tools & capabilities
Realestateapi tools 3
realestateapi_property_searchSearch properties by city/state/filters (off-market, absentee-owner, value range) — returns matching properties with address, owner, beds/baths, and estimated value. Example: realestateapi_property_search({ city: "Austin", state: "TX", absentee_owner: true, value_max: 400000, size: 25, _apiKey: "your-key" })realestateapi_property_detailGet full property detail by id or address — returns owner, estimated value, last sale, characteristics (beds/baths/sqft/year/lot), and mortgage. Example: realestateapi_property_detail({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })realestateapi_skip_traceSkip-trace owner contact info for an address — returns the owner name plus phone numbers and emails. Regulated PII: pure passthrough, nothing is stored. Example: realestateapi_skip_trace({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })
HasData Redfin tools 2
hasdata_redfin_listing_getRealEstateListingsGet Redfin Real Estate Listings Searches Redfin for-sale, for-rent, or sold listings with pagination. The location accepts a zipcode, city, neighborhood, school, school district, apartment-building name, or a full street address. Returns each listing with address, Redfin URL, list price, beds/baths, square footage, year built, days on market, status, coordinates, photos, and MLS number; an address or building returns a single property card instead. Use for real-estate market research, lead generation for agents, price/DOM trend analysis, and feeding URLs into the Redfin Property endpoint for deep-dive details.hasdata_redfin_property_getPropertyDetailsGet Redfin Property Details Fetches the full Redfin property page by URL. Returns address, list/sold price, price history, Redfin Estimate, beds/baths, square footage, lot size, year built, property type, HOA, days on market, school ratings, tax history, listing agent, full description, photos, and nearby comparables. Use for CMA reports, investor due-diligence, valuation models, listing enrichment, and powering buyer-assistant agents with verified property facts.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Realestateapi
{
"mcpServers": {
"realestateapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-realestateapi"
]
}
}
}
HasData Redfin
{
"mcpServers": {
"hasdata-redfin": {
"command": "npx",
"args": [
"-y",
"@hasdata/redfin-mcp"
],
"env": {
"HASDATA_API_KEY": "YOUR_HASDATA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Realestateapi is categorized under Real Estate and uses a local stdio subprocess. HasData Redfin belongs to Real Estate and uses a local stdio subprocess. Pick Realestateapi for real estate work and HasData Redfin for real estate.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Realestateapi has no declared pricing — check the project's own site. HasData Redfin has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add realestateapi and hasdata-redfin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Realestateapi has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. HasData Redfin has 63/100 (Good) with 1 views, 0 installs and 11 GitHub stars.