property_coverage
Pack: property-records · Endpoint: https://gateway.pipeworx.io/property-records/mcp
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.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
jurisdiction | string | no | Optional. Return detail for one jurisdiction only: ${COVERED_SLUGS.join(’ | ’)}. |
Example call
curl -X POST https://gateway.pipeworx.io/property-records/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"property_coverage","arguments":{}}}'Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"property-records": {
"url": "https://gateway.pipeworx.io/property-records/mcp"
}
}
}See Getting Started for client-specific install steps.