io.github.CloudCorpRecords/propdata
NPM · @RENETURCIOS/PROPDATA · 2 COMPONENTS
Zillow property data via APIllow: search, property details, price history, comps and usage.
Available components
Last scanned (23 hours ago)
Scores higher than 37% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 298 tokens (~33/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@reneturcios/propdata@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_addresses ~36
Check which addresses have an active Zillow listing; returns has_listing + listing URL
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | The street addresses to check. |
No output schema declared.
No examples provided.
check_usage ~18
See current usage, quota, and plan details
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_properties_by_addresses ~28
Look up several street addresses at once
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | The street addresses. |
No output schema declared.
No examples provided.
get_property ~27
Look up by Zillow Property ID
| Name | Type | Req | Description |
|---|---|---|---|
| zpid | integer | yes | The Zillow property ID. |
No output schema declared.
No examples provided.
get_property_by_address ~26
Look up one street address
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The street address. |
No output schema declared.
No examples provided.
get_property_by_url ~29
Get data from a Zillow listing URL
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The Zillow listing URL. |
No output schema declared.
No examples provided.
search_by_zip ~33
Search by ZIP codes (e.g. [90210])
| Name | Type | Req | Description |
|---|---|---|---|
| zip_codes | array | yes | ZIP codes to search. |
No output schema declared.
No examples provided.
search_properties ~65
Search by city or area (e.g. "Austin TX")
| Name | Type | Req | Description |
|---|---|---|---|
| max_items | integer | – | Maximum results to return. |
| query | string | yes | City or area to search, e.g. Austin TX. |
| type | string | – | Listing type, e.g. sale. |
No output schema declared.
No examples provided.
signup ~36
Create free account (50 properties/month); your API key arrives by email once you verify
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The account email address. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/propdata MCP server?
io.github.CloudCorpRecords/propdata runs locally as an npm package, launched with npx -y @reneturcios/propdata. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/propdata
claude mcp add cloudcorprecords-propdata -- npx -y @reneturcios/propdata
What is the io.github.CloudCorpRecords/propdata MCP server?
io.github.CloudCorpRecords/propdata is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/propdata. Zillow property data via APIllow: search, property details, price history, comps and usage. This page covers its npm package (@reneturcios/propdata).
Is the io.github.CloudCorpRecords/propdata MCP server safe to use?
io.github.CloudCorpRecords/propdata scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CloudCorpRecords/propdata MCP server expose?
io.github.CloudCorpRecords/propdata exposes 9 tools: search_properties, search_by_zip, get_property, get_property_by_url, get_property_by_address, and 4 more. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/propdata MCP server still maintained?
io.github.CloudCorpRecords/propdata is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/propdata MCP server under?
io.github.CloudCorpRecords/propdata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.