Property Records

What the Property Records MCP server does

The Property Records MCP server exposes address-level US property data through two MCP tools: property_lookup and property_coverage. It is intended for applications and agents that need to answer questions about a specific property, such as when it last sold, its recorded sale prices, the owner of record, or its assessed value.

property_lookup queries public records from supported county and city open-data portals without requiring an API key. Depending on the jurisdiction, a response can include dated sales transactions, sale prices, owner information, assessed value, parcel identifiers, land use or building class, year built, square footage, and bed or bath counts. The available fields differ by local source.

How it works

Property records are maintained locally, so this service does not provide nationwide coverage. An address outside the supported set returns covered: false, along with the inferred jurisdiction and the supported list. This lets an application report that a county is unavailable instead of filling gaps with an unsupported result.

Use property_coverage with an empty argument object to inspect the capability matrix. It lists supported counties and cities, the fields each source publishes, whether sale prices are available, data vintage, refresh cadence, jurisdiction-specific caveats, and the upstream source URL. The tool is useful when a workflow needs to determine whether a requested field, such as owner name or bed and bath counts, exists before making a lookup.

The gateway endpoint also exposes shared Pipeworx tools, including routing and discovery functions. A direct connection to the pack endpoint therefore lists more tools than the two property-specific tools. The standalone package exposes only the pack tools.

Setup and configuration

For a remote MCP connection, add the following endpoint to an MCP client:

{
  "mcpServers": {
    "property-records": {
      "url": "https://gateway.pipeworx.io/property-records/mcp"
    }
  }
}

The full gateway is available at https://gateway.pipeworx.io/mcp when an application needs all catalog packs directly. Both gateway URLs can use ask_pipeworx to route a natural-language question across the catalog.

A local stdio installation requires Node.js and can be started with:

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

The package can also be called over HTTP through POST https://gateway.pipeworx.io/v1/tools/property_lookup with an address JSON object. The provided setup does not require an environment variable or API key. The gateway documentation states that initial calls do not require an account.

Tools and capabilities

• property_lookup: Retrieves supported address-level property records and returns only fields available from the relevant local source.
• property_coverage: Reports jurisdiction coverage, field availability, source details, data vintage, refresh cadence, and caveats.
• Gateway access: Supports MCP connections, direct HTTP tool calls, and the shared ask_pipeworx routing tool.
• Local access: Runs the property pack over stdin and stdout without a Pipeworx account or gateway round trip.

Limitations and notes

Coverage is limited to the jurisdictions included in the dataset; there is no national keyless property-record source. Sale prices, owners, physical characteristics, and other fields are not available from every jurisdiction. For example, the provided examples indicate that San Francisco supplies assessed value and characteristics but not sale price.

The source data is public, but the service does not imply that every address will produce a complete record. Check property_coverage when field-level availability matters, and treat the returned jurisdiction and coverage status as part of the lookup result.