# Property Records (npm · @pipeworx/mcp-property-records)

Property Records MCP — address-level US property records (sales history, assessed value, owner…

- Trust score: 81/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`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-property-records/property-records-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-property-records/property-records-mcp)
- npm · `@pipeworx/mcp-property-records`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-property-records/pipeworx-mcp-property-records.md), [page](https://verifymcp.io/servers/pipeworx-io-property-records/pipeworx-mcp-property-records)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-property-records`
- 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-property-records).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 834 tokens (~417/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Property Records MCP server?

Property Records runs locally as an npm package, launched with npx -y @pipeworx/mcp-property-records. 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-property-records -- npx -y @pipeworx/mcp-property-records
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-property-records -- npx -y @pipeworx/mcp-property-records
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-property-records --command npx --arg -y --arg @pipeworx/mcp-property-records
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 81, +1)

- [security regression] Stability: 0.17 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 80, +2)

- [functional improvement] Stability: unverified → 0.13

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

First indexed and scored.

## MCP tools (2)

### `property_lookup` (~587 tokens)

Address-level US property records from county and city open-data portals — keyless public records, no API key. Answers "when did this house last sell", "how much did <address> sell for", "who owns this property", "what is the assessed value of <address>", "property sale history", "county assessor data for an address". Returns the property sale history (dated transactions with price where the county publishes it), current assessed value, owner of record, parcel id (DC SSL / NYC BBL / Philadelphia OPA account / Cook County PIN / SF block-lot), land use or building class, year built, square footage, and bed/bath counts where available. SUPPORTED JURISDICTIONS ONLY — property records are maintained per county and there is no national keyless source. Currently covered: dc (Washington, District of Columbia); nyc (New York City (Manhattan, Bronx, Brooklyn, Queens, Staten Island)); philadelphia (Philadelphia, Pennsylvania); cook (Cook County, Illinois (Chicago and suburbs)); sf (San Francisco, California). An address in any other county returns covered:false with the inferred jurisdiction and the supported list, so you can tell the user plainly that this county is not in the dataset rather than guessing. Call property_coverage first if you want the field-by-field capability matrix. Examples: {"address":"1642 30th St NW, Washington DC"} → DC row house, SSL 1282 0198, owner, $1,354,300 assessed, sold 2012-08-09 for $1,085,000, 3 bed / 2.5 bath / 1,510 sqft built 1907. {"address":"232 East 6th Street, Manhattan"} → NYC BBL 1004610024 with the 2016-present sale list. {"address":"228 Spruce St, Philadelphia"} → full recorded deed chain with grantor/grantee. {"address":"3000 N Sheffield Ave, Chicago"} → Cook County PIN, sale, assessed value. {"address":"450 Sutter St, San Francisco"} → assessed value and characteristics (no price — SF does not publish it).

Input parameters:

- `address` (string, required): Street address as free text. City / state / ZIP are optional but improve jurisdiction inference, e.g. "1600 Pennsylvania Ave NW", "232 East 6th Street, New York, NY 10003", "3000 N Sheffield Ave, Chi…
- `jurisdiction` (string): Optional. Skip inference and query a specific portal. One of: dc | nyc | philadelphia | cook | sf.
- `max_sales` (number|string): Maximum sale/transfer records to return, 1-50 (default 20, newest first).

### `property_coverage` (~193 tokens)

The capability matrix for property_lookup: every county and city this pack can answer address-level property-record questions for, and exactly which fields each one publishes — sales history (and whether it includes a price), owner name, assessed value, physical characteristics — plus the data vintage, refresh cadence, per-jurisdiction caveats, and the upstream source URL. Use this before promising a user an answer, to check whether their county is in the dataset and whether the specific field they asked about (sale price, owner, bed/bath) actually exists there. US property records are county-maintained and there is no national keyless source, so this list is the whole supported set. Example: {} → 5 jurisdictions, of which 4 publish sale prices and 4 publish owner names.

Input parameters:

- `jurisdiction` (string): Optional. Return detail for one jurisdiction only: dc | nyc | philadelphia | cook | sf.

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Property Records MCP server?

Property Records is an MCP server listed in the public MCP registry as io.github.pipeworx-io/property-records. Property Records MCP, address-level US property records (sales history, assessed value, owner… This page covers its npm package (@pipeworx/mcp-property-records).

### Is the Property Records MCP server safe to use?

Property Records scores 81 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 Property Records MCP server expose?

Property Records exposes 2 tools: property_lookup, property_coverage. Their descriptions and schemas cost roughly 780 tokens of context every time the server is loaded.

### Is the Property Records MCP server still maintained?

Property Records 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 Property Records MCP server under?

Property Records 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 Property Records MCP server?

VerifyMCP ran 16 checks on Property Records, 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-property-records
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-property-records
- Repository: https://github.com/pipeworx-io/mcp-property-records
- Website: https://pipeworx.io/packs/property-records
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-property-records/pipeworx-mcp-property-records.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-property-records/pipeworx-mcp-property-records/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-property-records/pipeworx-mcp-property-records.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-property-records/pipeworx-mcp-property-records