Realestateapi vs Property Records
A side-by-side look at the Realestateapi and Property Records 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 Property Records 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 Property Records when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You want tools like
property_lookup, property_coverage.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 59/100 · Good | 52/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View Realestateapi | View Property Records |
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" })
Property Records tools 2
property_lookupAddress-level US property records from county and city open-data portals — keyless public records, no API key. Answers "when did this house last sell", "how much did <address> sell for", "who owns this property", "what is the assessed value of <address>", "property sale history", "county assessor d…property_coverageThe capability matrix for property_lookup: every county and city this pack can answer address-level property-record questions for, and exactly which fields each one publishes — sales history (and whether it includes a price), owner name, assessed value, physical characteristics — plus the data vint…
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"
]
}
}
}
Property Records
{
"mcpServers": {
"property-records": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-property-records"
]
}
}
}
Frequently asked questions
Realestateapi is categorized under Real Estate and uses a local stdio subprocess. Property Records belongs to Real Estate and uses a local stdio subprocess. Pick Realestateapi for real estate work and Property Records 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. Property Records 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 property-records 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. Property Records has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.