Property Owner Records MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_property_owner_recordsA | Give US street addresses, or a state (NC, NY, FL, CO, AR, WI) with parcel IDs, owner names, or ZIP codes. Returns one row per parcel from public county tax rolls with the owner of record, the tax roll mailing address, property address, assessed and market values, land use, and last sale where published. No phone numbers or emails. Misses are free. Pay per event on Apify: 0.02 USD per parcel row. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool in the set, there is no possibility of confusion or misselection between tools. The single tool's purpose (property owner record lookup) is clearly and unambiguously stated.
The sole tool follows a clear verb_noun convention (lookup_property_owner_records) in snake_case. There is nothing to be inconsistent with, so the naming is trivially predictable.
A single tool is on the thin side even for a focused lookup service, which typically benefits from at least a search plus a detail/export variant. The count is borderline rather than clearly wrong for a narrow domain.
The tool appears to cover the core lookup and returns rich row-level data, but there are no companion operations (e.g. bulk export, schema/field discovery, or a coverage check for supported states) that agents would often need. The surface is functional but minimally so for a data-retrieval service.