Attom vs HouseData — Zillow data
A side-by-side look at the Attom and HouseData — Zillow data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
HouseData — Zillow dataReal EstateZillow data for agents: listings, records, Zestimate history, market stats. 19 tools, pay per call.38FairAuth: not declaredVerdict: choose Attom for real estate work as a local process; choose HouseData — Zillow data for real estate. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Attom when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
HChoose HouseData — Zillow data when
- You need dedicated capabilities in the Real Estate domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H HouseData — Zillow data | |
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 41/100 · Fair | 38/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Attom | View HouseData — Zillow data |
Tools & capabilities
Attom tools
No tool names declared yet. Check the project README from the listing page.
HouseData — Zillow data tools
No tool names declared yet. Check the project README from the listing page.
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.
Attom
{
"mcpServers": {
"attom": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-attom"
]
}
}
}
HouseData — Zillow data
No confirmed install command for HouseData — Zillow data yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Attom is categorized under Real Estate and uses a local stdio subprocess. HouseData — Zillow data belongs to Real Estate and uses an install path we have not confirmed yet. Pick Attom for real estate work and HouseData — Zillow data 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. HouseData — Zillow data has no confirmed install command yet — follow its own setup instructions.
Attom has no declared pricing — check the project's own site. HouseData — Zillow data is listed as a paid service. 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 attom and housedata-zillow-data as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Attom has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. HouseData — Zillow data has 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.