HouseData — Zillow data vs Evlek MCP
A side-by-side look at the HouseData — Zillow data and Evlek MCP 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 declaredE
Evlek MCPReal Estate · Remote HTTP/SSELive Northern Cyprus property data for AI agents — listings, price index, market overview.37FairAuth: not declaredVerdict: choose HouseData — Zillow data for real estate work; choose Evlek MCP for real estate over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
HChoose HouseData — Zillow data when
- You need dedicated capabilities in the Real Estate domain.
EChoose Evlek MCP when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H HouseData — Zillow data | E Evlek MCP |
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 38/100 · Fair | 37/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View HouseData — Zillow data | View Evlek MCP |
Tools & capabilities
HouseData — Zillow data tools
No tool names declared yet. Check the project README from the listing page.
Evlek MCP 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.
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.
Evlek MCP
{
"mcpServers": {
"mcp-server-6": {
"url": "https://evlek.app/mcp"
}
}
}
Frequently asked questions
HouseData — Zillow data is categorized under Real Estate and uses an install path we have not confirmed yet. Evlek MCP belongs to Real Estate and uses a remote HTTP/SSE transport. Pick HouseData — Zillow data for real estate work and Evlek MCP 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.
HouseData — Zillow data is listed as a paid service. Evlek MCP 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 housedata-zillow-data and mcp-server-6 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, HouseData — Zillow data has a quality signal of 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Evlek MCP has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.