# propraven [Health: Active]

**Category:** 🏠 Real Estate  
**Repository:** https://github.com/jdw2111/propraven-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 357  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/propraven

## Description
Property intelligence: 180M+ US parcels — lookup, search, owners, hazards, permits, deeds.

## Tools
Capabilities this server exposes over MCP:

- **parcel_lookup** — Resolve a single US parcel by identifier (canonical state_fips:county_fips:parcel_id, PropRaven UUID, street address, or APN). An ID returns the canonical PropRaven parcel card (GET /api/v1/parcels/{id}): identity, current owner, valuation, geography and source provenance. An address or APN runs the text search and returns up to 5 candidates — re-call with the chosen candidate's `lookup_id` to get the card. Use when the user names one specific property. Do NOT use when ranking multiple parcels (use parcel_compare) or when filtering by criteria (use parcel_search). Example: `parcel_lookup({ query: "37:119:12104406" })` or `parcel_lookup({ query: "2232 Wilmore Dr, Charlotte, NC 28203" })`. Free read — never purchases anything.
- **parcel_search** — Text search over US parcels (GET /api/v1/search/full): pass `q` as a city, owner name, address fragment or APN, optionally narrowed by `field`, `state` and `city`. Returns `{ results, total, totalCapped, page, pages, hasMore, nextCursor }` (default 50 per page, max 200); each result carries parcel_id, apn, county_fips, state_fips, site_address, city, zip5, owner_name, total_value, latitude, longitude (in search rows `parcel_id` is the PropRaven UUID and `county_fips` is 5-digit), plus `lookup_id`, added by this server — pass it to parcel_lookup / parcel_compare. Page with `cursor` (the previous response's `nextCursor`) rather than `page`; `total` is a floor when `totalCapped` is true. Use when the user wants properties matching a name, place or address fragment. Do NOT use when looking up a single known property (use parcel_lookup) or ranking a known set (use parcel_compare). Free read — never purchases anything.
- **parcel_compare** — Fetch 2–25 parcels side by side so they can be ranked against criteria. For each parcel it reads the free parcel card (GET /api/v1/parcels/{id}: identity, owner, valuation, building, lot) and, unless include_risks=false, the hazard block (GET /api/v1/parcels/{id}/risks), and returns a normalized `summary` plus the raw `card` / `risks`. The calling agent does the per-criterion scoring and final ranking. NEVER buys the paid parcel report or any other paid product. Use when the user has identified candidate properties (often from parcel_search) and wants them ranked. Do NOT use to discover new candidates (use parcel_search) or for a single property (use parcel_lookup + hazard_score). For deed or permit timelines call sales_history / permits_history per parcel. The `criteria` argument is returned verbatim so the agent can pin its scoring to the user's intent.
- **owner_pierce** — List the parcels titled under an owner-of-record name (GET /api/v1/owners/{name}/portfolio). Returns the matched owner name, a portfolio `summary` (count, total_value, total_acreage, by_state, truncated) and the `properties` list (parcel_id, county_fips, state_fips, address, assessed values, last sale, match_basis, match_confidence). This matches owner-name SPELLINGS — it is NOT a verified corporate, parent-subsidiary or beneficial-ownership link. Use when the user names a person, LLC, trust, or company and wants to see what is titled under that name. Do NOT use when starting from a parcel (use parcel_lookup, which returns owner inline). `ticker` is best-effort: it runs an owner-name search (GET /api/v1/owners/search) for the ticker text and uses the top match, returning the candidates under `resolution` — verify them, or call again with `name`. `state` filters the returned properties client-side (the summary stays portfolio-wide). Free read — never purchases anything.
- **hazard_score** — Hazard profile for a parcel (GET /api/v1/parcels/{id}/risks): flood (FEMA zone + SFHA flag), wildfire, seismic, windstorm, air quality and crime blocks, plus withhold_gate / identity_gate provenance. Use when the user asks about a property's risk profile — insurance pricing, underwriting, or due diligence. Do NOT use to compare multiple parcels (use parcel_compare, which includes each parcel's hazards). Every requested key is present: the value, or null when PropRaven does not hold it. Coverage varies by hazard. Free read — never purchases anything (this is not the paid risk-score product).
- **valuation_estimate** — Value fields for a parcel from its free card (GET /api/v1/parcels/{id}): market_value, avm_value with avm_confidence / avm_method, total / land / improvement assessed value, tax, last sale price and date, price_per_sqft. Numbers are normalized to JSON numbers (null = not held). Use when the user asks for a property's value, market estimate, AVM, or wants to compare assessed vs market. Do NOT use as a substitute for an appraisal — this is a modeled estimate. Historical AVM (as_of) is not supported; the tool returns the current snapshot. Free read — never purchases anything.
- **permits_history** — Timeline of building / construction / demolition permits filed against a parcel (GET /api/v1/parcels/{id}/permits). Each permit includes permit_number, permit_type, permit_status, description, work_class, issued_date, completed_date, estimated_cost, contractor_name (where disclosed). Use when the user asks about construction activity, recent renovations, planned work, or wants to detect a property that's actively changing. Do NOT use to find properties WITH recent permits across a market. At most 100 permits are returned (newest first). `permit_count` is the parcel's TRUE count when `permit_count_basis` is "exact"; "capped" means it is the size of the 100-row window (a floor); `truncated: true` means the parcel has more permits than returned. `since` / `types` filter the returned window only (`returned_count` is after filtering). Coverage varies by county. Free read — never purchases anything.
- **sales_history** — Deed / transaction timeline for a parcel (GET /api/v1/parcels/{id}/deeds): recorded sales and transfers with recording and sale dates, sale price (where disclosed), grantor (seller), grantee (buyer), deed/document type and book/page. Use when the user asks about a property's transaction history, flip activity, or holding period. Do NOT use to find properties with recent sales market-wide, or to estimate current market value (use valuation_estimate). Note: 13 states do not disclose sale prices on deeds (KS, MS, TX, UT, WY, etc.). `event_count` is the number of events returned. `status` says where they came from: per_deed (deed rows), rollup_events (dated rollup entries), summary_only (no events served, but `known_deed_count` deeds are known — see known_deed_count_basis), or none. UCC liens are NOT available here (they are only in the paid parcel report, which this server never buys). Free read — never purchases anything.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "propraven": {
    "command": "npx",
    "args": ["-y","@propraven/mcp"],
    "env": {
      "PROPRAVEN_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `PROPRAVEN_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What propraven does

The propraven MCP server exposes PropRaven property data to MCP-compatible agents. Its dataset covers 191.3 million US parcels, including 110.0 million mapped parcels, with ownership, valuation, permits, deeds, hazards, and market information.

The tools support several common property-research tasks. `parcel_lookup` resolves a parcel from an ID, address, or APN, while `parcel_search` finds records using an owner name, address fragment, APN, or city. `owner_pierce` searches parcels associated with an owner name and can apply a state filter. `parcel_compare` returns free parcel cards and hazards for two to 25 parcels so an agent can rank them.

Additional tools provide hazard blocks for flood, wildfire, seismic, windstorm, air quality, and crime; valuation details such as market value, AVM, assessed values, last sale, and price per square foot; permit timelines; and deed or transfer histories.

## How it works

The propraven MCP server supports two connection methods. A hosted Streamable HTTP endpoint is available at `https://propraven.com/mcp`; clients send the API key as a bearer authorization header. A local stdio option runs through `npx @propraven/mcp` and communicates with the configured MCP client process.

Parcel identifiers use the canonical `state_fips:county_fips:parcel_id` form, such as `37:119:12104406`. Legacy five-digit county forms and PropRaven parcel UUIDs are also accepted. Address and search results include a lookup identifier that can be passed to lookup or comparison operations.

The tools issue read requests to PropRaven's free or metered API endpoints. They do not send payment headers or purchase reports. If an endpoint returns an x402 payment response, the tool reports that payment is required instead of paying. Calls still count toward the account's monthly quota. Temporary 429 and 503 responses are retried once when the response provides a retry interval of ten seconds or less.

## Setup and configuration

For hosted use, configure an HTTP-capable MCP client with the endpoint and a bearer token. For local use, install Node.js 18 or newer, obtain a PropRaven API key, and configure the client to run `npx -y @propraven/mcp` with `PROPRAVEN_API_KEY` in its environment. Restarting the client makes the eight tools available.

`PROPRAVEN_API_KEY` is required and uses the `pz_...` format. `PROPRAVEN_BASE_URL` optionally changes the API host and defaults to `https://propraven.com`. `PROPRAVEN_TIMEOUT_MS` controls the per-request timeout and defaults to 30,000 milliseconds. The repository also provides build, test, development, and MCP Inspector commands for local work.

## Tools and capabilities

- Resolve individual parcels by identifier, address, or APN.
- Search parcels by text with optional state and city filters and keyset pagination.
- Find parcels held under an owner name, with optional state filtering and best-effort ticker handling.
- Compare two to 25 parcels using parcel cards and hazard data.
- Retrieve valuation, assessment, sale, and price-per-square-foot information.
- Review hazard categories, permit records, and deed or transfer history.

## Limitations and notes

The propraven MCP server returns at most the 100 newest permit records, along with a count basis indicating the broader total. Owner searches are best effort, and ticker-based handling is also best effort. Search and lookup depend on the identifiers and address data accepted by the underlying API.

The tools are read-only and do not buy parcel reports, comp packs, risk scores, owner reports, leads, or storefront products. API errors are surfaced as RFC 7807-style status, code, and detail messages. The hosted Claude.ai connector uses OAuth, while other documented hosted configurations use bearer authentication.

_Full upstream README: https://allmcps.com/mcp/propraven/readme_