Realestateapi
NPM · @PIPEWORX/MCP-REALESTATEAPI · 2 COMPONENTS
RealEstateAPI MCP — property search, detail, and skip-trace (realestateapi.com)
Available components
Last scanned (19 hours ago)
Scores higher than 76% of npm servers
Category Maps and Location
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-realestateapi). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 572 tokens (~190/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +3
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-realestateapi@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-realestateapi |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-realestateapi/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691876791 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5f58f1a247153ca59492cb92361ce1882e878167f7002441c739c0c7865a7aa7d4100d025d9220b16d9dda83148a7e8eb7afeeb930aebeec02ba6092a |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
realestateapi_property_detail ~127
Get 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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | RealEstateAPI key from realestateapi.com |
| address | string | – | Full property address (use if you have no id) |
| id | string | – | RealEstateAPI property id (from a search result) |
No output schema declared.
No examples provided.
realestateapi_property_search ~251
Search 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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | RealEstateAPI key from realestateapi.com |
| absentee_owner | boolean | – | Only properties whose owner lives elsewhere |
| baths_min | integer | – | Minimum bathrooms |
| beds_min | integer | – | Minimum bedrooms |
| city | string | – | City name, e.g. "Austin" |
| property_type | string | – | One of SFR, MFR, CONDO, LAND, MOBILE, OTHER |
| size | integer | – | Max results to return (default 10, max 50) |
| state | string | – | Two-letter state code, e.g. "TX" |
| value_max | integer | – | Maximum estimated value (USD) |
| value_min | integer | – | Minimum estimated value (USD) |
| zip | string | – | ZIP code |
No output schema declared.
No examples provided.
realestateapi_skip_trace ~140
Skip-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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | RealEstateAPI key from realestateapi.com |
| address | string | yes | Full property/mailing address to trace |
| first_name | string | – | Owner first name (optional, improves match) |
| last_name | string | – | Owner last name (optional, improves match) |
No output schema declared.
No examples provided.
How do I install the Realestateapi MCP server?
Realestateapi runs locally as an npm package, launched with npx -y @pipeworx/mcp-realestateapi. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-realestateapi
claude mcp add pipeworx-io-realestateapi -- npx -y @pipeworx/mcp-realestateapi
What is the Realestateapi MCP server?
Realestateapi is an MCP server listed in the public MCP registry as io.github.pipeworx-io/realestateapi. RealEstateAPI MCP, property search, detail, and skip-trace (realestateapi.com). This page covers its npm package (@pipeworx/mcp-realestateapi).
Is the Realestateapi MCP server safe to use?
Realestateapi scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Realestateapi MCP server expose?
Realestateapi exposes 3 tools: realestateapi_property_search, realestateapi_property_detail, realestateapi_skip_trace. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.
Is the Realestateapi MCP server still maintained?
Realestateapi is still listed as active in the MCP registry. We last reached this channel on 5 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 Realestateapi MCP server under?
Realestateapi declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Realestateapi MCP server?
VerifyMCP ran 15 checks on Realestateapi, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Realestateapi: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.