# Housing Intel (npm · @pipeworx/mcp-housing-intel)

Housing Intel MCP — Meta-pack that chains FRED, BLS, ATTOM, and HUD APIs into higher-level housing…

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 87/100, [markdown](https://verifymcp.io/servers/pipeworx-io-housing-intel/housing-intel-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-housing-intel/housing-intel-mcp)
- npm · `@pipeworx/mcp-housing-intel`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-housing-intel/pipeworx-mcp-housing-intel.md), [page](https://verifymcp.io/servers/pipeworx-io-housing-intel/pipeworx-mcp-housing-intel)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-housing-intel`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-housing-intel).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2101 tokens (~210/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Housing Intel MCP server?

Housing Intel runs locally as an npm package, launched with npx -y @pipeworx/mcp-housing-intel. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-housing-intel -- npx -y @pipeworx/mcp-housing-intel
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-housing-intel": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-housing-intel"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-housing-intel": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-housing-intel"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-housing-intel -- npx -y @pipeworx/mcp-housing-intel
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-housing-intel": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-housing-intel"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-housing-intel --command npx --arg -y --arg @pipeworx/mcp-housing-intel
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-housing-intel:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-housing-intel"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-housing-intel": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-housing-intel"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-housing-intel -t stdio -c npx -a -y @pipeworx/mcp-housing-intel
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-housing-intel": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-housing-intel"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 81, +26)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-02 (score 55, −26)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (10)

### `case_shiller_metro_compare` (~323 tokens)

Compare Case-Shiller home price indices across multiple US metros in one call (the 20-city composite). For each metro returns latest level, 3-month change, 12-month change, all-time peak, drawdown from peak, and a softening flag. Output also ranks metros softest → strongest. Use for "which metros are softening", "Case-Shiller for [list of cities]", "compare housing prices in X, Y, Z" queries — picks the right per-metro FRED series IDs (DNXRSA, PHXRSA, TPXRSA, etc.) so callers don't have to. Available metros: Atlanta, Boston, Charlotte, Chicago, Cleveland, Dallas, Denver, Detroit, Las Vegas, Los Angeles, Miami, Minneapolis, New York, Phoenix, Portland, San Diego, San Francisco, Seattle, Tampa, Washington DC. NOT A CURRENT-MARKET READ: Case-Shiller is monthly, published on a roughly two-month lag, and each value is a three-month moving average — so the newest observation is typically 90-120 days old and describes a trailing quarter. The `freshness` block states the exact age of the call you made.

Input parameters:

- `_fredKey` (string): FRED API key (https://fred.stlouisfed.org/docs/api/api_key.html). Platform key used if omitted.
- `metros` (array, required): Metro names, case-insensitive. Example: ["Denver", "Phoenix", "Tampa", "Charlotte"]. Pass any subset of the 20-city composite.

### `housing_market_snapshot` (~222 tokens)

Get national housing market overview: mortgage rates, housing starts, Case-Shiller index, unemployment, construction employment. Optionally add metro-level prices (e.g., "Denver", "Atlanta"). For comparing Case-Shiller across multiple metros use case_shiller_metro_compare instead. THE COMPONENTS DO NOT SHARE A DATE — they are weekly, monthly and quarterly official statistics, each published on its own lag, so one call can span months of vintages. `freshness` states the span in days and names the oldest component; read it before comparing components against each other.

Input parameters:

- `_blsKey` (string): BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
- `_fredKey` (string): FRED API key (https://fred.stlouisfed.org/docs/api/api_key.html)
- `metro_name` (string): Metro area name for metro-level FHFA HPI (e.g., "Denver", "Atlanta"). Supports top 50 US metros. National data is always included.

### `housing_property_report` (~98 tokens)

Analyze a property by address and zip code. Returns valuation estimate, sales history, tax assessment, and detailed characteristics.

Input parameters:

- `_attomKey` (string, required): ATTOM API key (https://api.gateway.attomdata.com)
- `address1` (string, required): Street address (e.g., "4529 Winona Court")
- `address2` (string, required): City, state ZIP (e.g., "Denver, CO 80212")

### `housing_rental_analysis` (~164 tokens)

Evaluate rental investment potential by address and zip code. Returns estimated rent, fair market rents, and CPI rent trends.

Input parameters:

- `_attomKey` (string, required): ATTOM API key
- `_blsKey` (string): BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
- `_hudKey` (string): HUD API token (optional — needed for fair market rents)
- `address1` (string, required): Street address (e.g., "4529 Winona Court")
- `address2` (string, required): City, state ZIP (e.g., "Denver, CO 80212")
- `state_code` (string, required): Two-letter state code for HUD FMR lookup (e.g., "CO")

### `housing_affordability_check` (~281 tokens)

Check housing affordability in a market. Returns mortgage rate, median price, monthly payment, required income, and HUD limits. Optionally specify metro (e.g., "Denver"). The inputs are official statistics on DIFFERENT cadences — a weekly mortgage rate against a quarterly median price — so the monthly payment is an illustrative ratio of published figures, not a live quote. `freshness` states the span and the age of each input.

Input parameters:

- `_blsKey` (string): BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
- `_fredKey` (string): FRED API key
- `_hudKey` (string): HUD API token (optional — needed for income limits)
- `metro_name` (string): Metro name for metro-level FHFA HPI (e.g., "Denver", "Savannah"). Optional.
- `state` (string): State name or two-letter code (e.g., "California" or "CA"). Resolved for you — pass this rather than state_code. Optional: without it you still get the national mortgage rate, median price and afford…
- `state_code` (string): Two-letter state code for HUD income limits (e.g., "CO"). `state` is preferred and accepts either form.

### `housing_employment_outlook` (~150 tokens)

Assess labor market health for housing demand. Returns employment, construction jobs, residential building employment, unemployment rate, and job openings. All BLS monthly releases; each series carries its own `observation_date` and `cadence` (JOLTS runs an extra month behind CES/LAUS), and `freshness` states the span. `snapshot_date` is the call date, not the data date.

Input parameters:

- `_blsKey` (string): BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
- `_fredKey` (string): FRED API key (accepted for consistency but not used — BLS is free)

### `housing_signal_scan` (~168 tokens)

Scan 45+ housing indicators for anomalies and reversals. Flags unusual moves across rates, starts, sales, prices, wages, unemployment, and rent. Each signal carries its own `observation_date` and `cadence` — series here span weekly (mortgage rate) to quarterly (median sales price), and Case-Shiller is additionally a 3-month moving average, so "turned negative" does not mean "this month" for every series. `freshness` states the full span and the oldest component.

Input parameters:

- `_blsKey` (string): BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
- `_fredKey` (string): FRED API key (gateway-injected; only needed outside the gateway)

### `housing_mortgage_history` (~164 tokens)

Freddie Mac Primary Mortgage Market Survey — the weekly US mortgage INTEREST rate (the annual percentage borrowers pay on a home loan, e.g. 6.5%), back to 1971. This is the borrowing cost paid by home buyers. Returns the latest snapshot, a time series for the requested window, and min/max/avg stats. Sourced from Freddie Mac directly (not FRED), ingested weekly by the Pipeworx data pipeline.

Input parameters:

- `as_of` (string): Optional YYYY-MM-DD — returns the rate for the closest observation on or before that date instead of the latest.
- `window` (string): 1m | 3m | 6m | 1y | 5y | all (default 1y)

### `housing_market_screen` (~235 tokens)

Rank US metros for rental cash flow in ONE call — the "which markets are best for a landlord" view. Returns metros sorted by gross rent yield = (Zillow median monthly rent × 12) ÷ Zillow typical home value. No per-metro orchestration and no API key. Use for "best/worst rental markets", "highest-yield metros", "where does rent go furthest vs. home prices". Tune with direction (top = highest yield / best cash flow, bottom = lowest), limit, and optional home-value bounds. rent_as_of and home_value_as_of are two independent Zillow queries and can land on different months; `freshness` says whether they matched this call.

Input parameters:

- `direction` (string): top = highest gross yield (best cash flow), bottom = lowest. Default top.
- `limit` (number): Metros to return (default 25, max 100).
- `max_home_value` (number): Optional: only metros with typical home value ≤ this (USD).
- `min_home_value` (number): Optional: only metros with typical home value ≥ this (USD).

### `housing_metro_demand` (~241 tokens)

Demand + rent-durability signals for a shortlist of US metros in ONE call — population & 5-year growth, renter share, median household income, and unemployment, straight from Census ACS. Deterministic by metro (CBSA-keyed) — NO FRED series-ID guessing. Pass `metros` ("City, ST", e.g. the top results from housing_market_screen). This is the Stage-2 "is the demand real?" filter on a yield shortlist — high yield in a shrinking metro is a trap. No API key needed. HIGHEST-LAG SOURCE IN THIS PACK: figures are a Census ACS 5-YEAR rolling average (currently 2018-2022, released Dec 2023) — for structural demand, not a current-quarter read. `freshness` states the exact age.

Input parameters:

- `limit` (number): Max metros to enrich (default 25, max 100).
- `metros` (array, required): Metro names to enrich, "City, ST" form, e.g. ["Lubbock, TX","Pittsburgh, PA"] — match the housing_market_screen output. Required.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-housing-intel/pipeworx-mcp-housing-intel#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 55
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79

## Common questions

### What is the Housing Intel MCP server?

Housing Intel is an MCP server listed in the public MCP registry as io.github.pipeworx-io/housing-intel. Housing Intel MCP, Meta-pack that chains FRED, BLS, ATTOM, and HUD APIs into higher-level housing… This page covers its npm package (@pipeworx/mcp-housing-intel).

### Is the Housing Intel MCP server safe to use?

Housing Intel scores 82 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 Housing Intel MCP server expose?

Housing Intel exposes 10 tools: case_shiller_metro_compare, housing_market_snapshot, housing_property_report, housing_rental_analysis, housing_affordability_check, and 5 more. Their descriptions and schemas cost roughly 2,046 tokens of context every time the server is loaded.

### Is the Housing Intel MCP server still maintained?

Housing Intel 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 Housing Intel MCP server under?

Housing Intel 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 Housing Intel MCP server?

VerifyMCP ran 16 checks on Housing Intel, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-housing-intel
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-housing-intel
- Repository: https://github.com/pipeworx-io/mcp-housing-intel
- Website: https://pipeworx.io/packs/housing-intel
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-housing-intel/pipeworx-mcp-housing-intel.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-housing-intel/pipeworx-mcp-housing-intel/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-housing-intel/pipeworx-mcp-housing-intel.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-housing-intel/pipeworx-mcp-housing-intel