
Propdata
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Zillow property data via APIllow: search, property details, price history, comps and usage.
Overview
Propdata's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Propdata in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
propdata
Zillow property data through the APIllow API: search homes by city or ZIP code, pull a single property by its Zillow ID, its listing URL or its street address, look up several addresses in one call, check which addresses currently have an active listing, create a free account, and see how much of the monthly quota is left.
Property answers come from the upstream service and are passed through untouched, so a property record carries what APIllow returns for it — identifiers, address, status and type, bed and bath counts, living area and lot size, year built, pricing and estimates, sale and tax history, a small set of comparable homes, photos, and nearby schools.
Nine tools are provided. A tenth tool in the upstream catalogue, a plan-upgrade helper whose only output is a payment link, is deliberately not part of this package.
The nine tools:
search_properties— search by city or area, with an optional listing type and a cap on how many results come back.search_by_zip— search by one or more ZIP codes.get_property— one property by its Zillow property ID.get_property_by_url— one property from its Zillow listing URL.get_property_by_address— one property by street address.get_properties_by_addresses— several street addresses looked up in a single request.check_addresses— which of a set of addresses has an active Zillow listing, with the listing URL.signup— create a free account; the API key arrives by email after verification.check_usage— current usage, quota and plan details.
Configuration
Without a key, every tool except signup fails with
APILLOW_API_KEY is not set, before any argument checking.
The key is sent to the API as an X-API-Key header.
CLI
Each tool is a subcommand taking one JSON argument string:
Output is the upstream JSON, printed unchanged. Exit codes:
0 on success, 1 on a runtime error (including a
validation or upstream failure), 2 on a usage error.
MCP server
MCP client config:
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit f665954
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts