Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Housing Intel

NPM · @PIPEWORX/MCP-HOUSING-INTEL · 2 COMPONENTS

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

+3 this week 82 Trust /100

Last scanned (16 hours ago)

Scores higher than 72% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

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-housing-intel). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • 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. 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 4 Nov 26 +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.

  • 3 Nov 26 +26
    • Known CVEs: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 2 Nov 26 −26
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: pass → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 +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.

  • 30 Oct 26 +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.

  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

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-housing-intel@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-housing-intel
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-housing-intel/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637393606
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a96e05e3ec637aa46cf6a99fdfa4ed610740f941f793ac390e218b2383feef5395802f58d66175dd41de54897f7f0aee0a1e754e768d24e448f00ac3d

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~2,046 tokens

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 →

Tool Tokens
case_shiller_metro_compare ~323

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.

NameTypeReqDescription
_fredKeystring–FRED API key (https://fred.stlouisfed.org/docs/api/api_key.html). Platform key used if omitted.
metrosarrayyesMetro names, case-insensitive. Example: ["Denver", "Phoenix", "Tampa", "Charlotte"]. Pass any subset of the 20-city composite.

No output schema declared.

No examples provided.

housing_affordability_check ~281

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.

NameTypeReqDescription
_blsKeystring–BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
_fredKeystring–FRED API key
_hudKeystring–HUD API token (optional — needed for income limits)
metro_namestring–Metro name for metro-level FHFA HPI (e.g., "Denver", "Savannah"). Optional.
statestring–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_codestring–Two-letter state code for HUD income limits (e.g., "CO"). `state` is preferred and accepts either form.

No output schema declared.

No examples provided.

housing_employment_outlook ~150

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.

NameTypeReqDescription
_blsKeystring–BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
_fredKeystring–FRED API key (accepted for consistency but not used — BLS is free)

No output schema declared.

No examples provided.

housing_market_screen ~235

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.

NameTypeReqDescription
directionstring–top = highest gross yield (best cash flow), bottom = lowest. Default top.
limitnumber–Metros to return (default 25, max 100).
max_home_valuenumber–Optional: only metros with typical home value ≤ this (USD).
min_home_valuenumber–Optional: only metros with typical home value ≥ this (USD).

No output schema declared.

No examples provided.

housing_market_snapshot ~222

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.

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

No output schema declared.

No examples provided.

housing_metro_demand ~241

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.

NameTypeReqDescription
limitnumber–Max metros to enrich (default 25, max 100).
metrosarrayyesMetro names to enrich, "City, ST" form, e.g. ["Lubbock, TX","Pittsburgh, PA"] — match the housing_market_screen output. Required.

No output schema declared.

No examples provided.

housing_mortgage_history ~164

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.

NameTypeReqDescription
as_ofstring–Optional YYYY-MM-DD — returns the rate for the closest observation on or before that date instead of the latest.
windowstring–1m | 3m | 6m | 1y | 5y | all (default 1y)

No output schema declared.

No examples provided.

housing_property_report ~98

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

NameTypeReqDescription
_attomKeystringyesATTOM API key (https://api.gateway.attomdata.com)
address1stringyesStreet address (e.g., "4529 Winona Court")
address2stringyesCity, state ZIP (e.g., "Denver, CO 80212")

No output schema declared.

No examples provided.

housing_rental_analysis ~164

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

NameTypeReqDescription
_attomKeystringyesATTOM API key
_blsKeystring–BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
_hudKeystring–HUD API token (optional — needed for fair market rents)
address1stringyesStreet address (e.g., "4529 Winona Court")
address2stringyesCity, state ZIP (e.g., "Denver, CO 80212")
state_codestringyesTwo-letter state code for HUD FMR lookup (e.g., "CO")

No output schema declared.

No examples provided.

housing_signal_scan ~168

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.

NameTypeReqDescription
_blsKeystring–BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
_fredKeystring–FRED API key (gateway-injected; only needed outside the gateway)

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-housing-intel

# add to Claude Code
claude mcp add pipeworx-io-housing-intel -- npx -y @pipeworx/mcp-housing-intel
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.