PropertyRadar MCP ServerVerifiedFeatured

@PropertyRadar

Homepage

Basic information

Transport

Streamable HTTP

Authentication

OAuth

About PropertyRadar MCP Server

Research U.S. markets and prospects conversationally using PropertyRadar's property and people data. Resolve an address, inspect Property details, transactions, comparable sales, ownership and contact information, discover supported Criteria and fields, search for matching Properties, and save selected results as a dynamic Audience. PropertyRadar accesses only the data available to your connected account.

#real estate #marketing#government data

Connection details

https://mcp.propertyradar.com/mcp

Setup

claude mcp add propertyradar --transport http https://mcp.propertyradar.com/mcp

PropertyRadar MCP Server tools

Acquire or re-fetch billable email contact data for one Person by person_id (same string as REST PersonKey, e.g. p4290). PropertyRadar covers all 50 US states and DC nationwide. Required: person_id. Optional: fields (default Standard; Standard and All return the same four Product email ids; comma-separated ids from get_fields are also accepted). Returns email contact data in results[] with data_acquisition_status (acquired, my_data, or unavailable). Bills one fixed billable hit when contact data is newly acquired; my_data and unavailable are non-billable (total_cost=0). No count_only quote on this tool. Typical chain: get_property_persons → take PersonID from a row → get_person_emails when the user wants emails only. Use get_person_phones or get_person_relatives for other contact data. User outreach compliance remains the subscriber responsibility.

Acquire or re-fetch billable relative data for one Person by person_id (same string as REST PersonKey, e.g. p4290). PropertyRadar covers all 50 US states and DC nationwide. Required: person_id. Optional: fields (default Standard; Standard and All return the same 13 Product relative ids; comma-separated ids from get_fields are also accepted). Returns at most five relative rows in API acquisition order with data_acquisition_status (acquired, my_data, or unavailable). Bills one fixed hit only when data is newly acquired; my_data and unavailable are non-billable (total_cost=0). No count_only quote on this tool. Typical chain: get_property_persons → take PersonID from a row → get_person_relatives. Each result has an mp-prefixed RelatedPersonID that can be passed as person_id to get_person_phones; owned relative email data may remain unavailable through get_person_emails.

Acquire or re-fetch billable phone contact data for one Person by person_id (same string as REST PersonKey, e.g. p4290). PropertyRadar covers all 50 US states and DC nationwide. Required: person_id. Optional: fields (default Standard; Standard and All return the same five Product phone ids). Returns phone contact data in results[] with data_acquisition_status (acquired, my_data, or unavailable). Bills one fixed billable hit when contact data is newly acquired; my_data and unavailable are non-billable (total_cost=0). No count_only quote on this tool. Typical chain: get_property_persons → take PersonID from a row → get_person_phones when the user wants phones only. Sibling contact data tools: get_person_emails, get_person_relatives. Not for property-scoped person fetch (use get_property_persons). User outreach compliance (TCPA/CCPA) remains the subscriber responsibility.

Discover exact output field ids for a consuming MCP record tool. Never bills and returns catalog metadata only. Required: tool; supports get_property_details, get_properties_details, get_property_summary, get_property_comps, get_property_transactions, get_property_persons, get_person_phones, get_person_emails, and get_person_relatives. With tool only, returns compact fieldsets[], groups[], and upgrade_field_ids[] indexes without full metadata rows. Add groups, field_ids, or query to return MCP-shaped fields[] with id, group, title, short_title, description, and included; those scopes are composable. Property record tools expose Standard (80) and All (200 shippable, including eight computed loan fields) fieldsets for get_property_details and get_properties_details. For get_property_summary, fieldset Standard or All returns full metadata for entitled members and both bundles have identical registered membership. For get_property_comps, Standard contains 19 available ids and All contains 24 available ids spanning sales and listings; CompDistance and ZipFive remain Product requirements. The billable comps tool omits fields that do not apply to the requested comp_type. For get_property_transactions, seven fieldsets register 94 available ids; the remaining unavailable field stays visible with included=unavailable. For get_property_persons, Standard exposes all 22 registered ids and All exposes all 33 registered ids; tool_status remains partial while primary_only is unavailable. For get_person_phones, get_person_emails, and get_person_relatives, Standard and All are identical within each tool and the catalog reports current Partial constraints. Fieldset cannot combine with other scopes. Summary accepts no fields argument itself; use this catalog to understand its fixed results. Do not call this tool to identify the owner; use get_property_persons for persons and contact channels. Use get_criteria for search filters. Other consuming tools are unsupported.

Fetch authoritative scalar property fields from PropertyRadar by RadarID. PropertyRadar covers all 50 US states and DC nationwide; RadarIDs are issued for properties in any state. This is the billable property-record path and bills per API terms. Use after resolve_address or get_property_summary when the user needs exact fields beyond the summary bands — DistressScore, equity detail, or assessor/tax scalars. Do not use this tool to identify an owner; use get_property_persons after get_property_summary. Never returns nested arrays or person-extracted contact data; route phone/email to get_property_persons. The fields argument selects the Standard fieldset by default or a comma-separated list of field ids from get_fields. Contacts-group field ids are rejected.

Return a model-safe summary of one Property by RadarID for single-property Q&A — not for bulk scoring, market sweeps, or looping across many RadarIDs. PropertyRadar covers all 50 US states and DC nationwide. Use after resolve_address when resolved is true, or when the user already has a RadarID. Never bills. Returns radar_id, provided_by, description, results with the fixed 14-field get_fields allowlist in registered order (city/state placement only — no street address or ZIP in results or description), optional field_notes for DistressBand and EquityBand, and related_tools[] pointing to billable depth (get_property_details, get_property_transactions, get_property_comps, get_property_persons). When the user asks who owns the Property, call get_property_persons next; do not call get_fields or get_property_details for ownership alone. Bands are coarse triage only — do not use summary for exact DistressScore, EquityPercent, distress signal types, owner contact, comps, sale history, building age, street address, or transaction rows; call the related billable tools instead. For market-level distress or equity characterization use search_properties (and get_properties_details when the user needs rows). This tool is distinct from future get_property_insights and is not for CSV/export workflows.

Fetch billable recorder history (title chain) for one Property by RadarID — deeds, loans, liens, notices, releases, and child documents. PropertyRadar covers all 50 US states and DC nationwide. Status: Partial until isNewConstruction is available. Required: radar_id. Optional: count_only (true returns result_count and estimated_cost with empty results[], non-billable — recommend before purchase when chain size is unknown); limit (default 100, max rows on purchase); fields (default Standard; seven Product fieldsets plus comma-separated field ids via get_fields — API Fields cap is 500 ids per request); document_id (scope to one row; omitted fields defaults to All when document_id is set); document_group (csv of Mortgage, Deed, Foreclosure, Lien, Notice, Release, Other — server-side instrument-class filter; preferred over document_type for intent such as all foreclosures or all loans); document_type (raw DocType codes, server-side filter; AND with document_group when both set); date_range (YYYY-MM-DD,YYYY-MM-DD inclusive recording bounds, server-side RecDate filter); current_owner_only (Filter=CurrentOwner). Returns flat results[] with RecordStatus on every row. Bills one billable unit per row returned. Use get_fields(tool="get_property_transactions") before first purchase. Not for scalar property record (use get_property_details).

Fetch billable comparable Property rows for one subject Property by RadarID. PropertyRadar covers all 50 US states and DC nationwide. Required: radar_id. Optional: comp_type sales (default) or listings (for-sale only); limit defaults to 10 and must be 1–50; fields defaults to the currently available 19-id Standard fieldset and also accepts the 24-id All fieldset or validated comma-separated field ids; fieldsets span both comp kinds and ids not applicable to the active kind are omitted; CompDistance and ZipFive remain Product requirements with accepted engineering deferral to v2; subject overrides PType, Beds, Baths, Units, SqFt, LotSize, and YearBuilt; transfer_types is sales-only and listing_types is listings-only. Bills per returned comp row; subject_property is non-billable. Returns ranked results[], symmetric subject_property, returned_count, total_cost, radar_id, comp_type, fields, and related_tools[]. Never returns retired/raw comparables ids or REST debug keys. Do not loop this tool across many RadarIDs unless the user explicitly intends the multiplied per-row cost. Use get_property_details for scalar subject fields and get_property_transactions for recorder history.

Fetch billable person records associated with one Property by RadarID — owners, principals, trustees, and entities (not skip-trace parity). PropertyRadar covers all 50 US states and DC nationwide. Required: radar_id. Optional: count_only (true returns result_count and estimated_cost with empty results[], non-billable — use before purchase); fields (default Standard fieldset per get_fields(tool="get_property_persons"); comma-separated Product field ids allowed). Bills one billable unit per top-level person record retrieved. When the user asks who owns a resolved property, call this after get_property_summary; do not use get_fields or get_property_details for ownership alone. Returns priority-ordered flat scalar rows (primary contact first) with RecordStatus on every row and PersonID for contact-data follow-up. Phones, emails, and relatives are Phase 2 via get_person_phones, get_person_emails, and get_person_relatives (PersonID-scoped) — not on person rows. Not for property field export (use get_property_details). User outreach compliance (TCPA/CCPA) remains the subscriber responsibility.

Resolve a US street address to Property RadarIDs for disambiguation before single-property tools. PropertyRadar has nationwide coverage of all 50 US states and DC; do not skip this tool based on the state or region in the address. Returns a JSON envelope with query (echo of input), resolved (true only when exactly one suggestion), message (when resolved is false, truncated, or no match), suggestions[] (max 20; each row has non-null radar_id and full normalized address label with city, state, and ZIP when available), and total_match_count when multiple properties match or the list is truncated. This tool never bills. For model-safe Q&A without UI, call get_property_summary. If the user asks who owns the property, then call get_property_persons; do not call get_fields or get_property_details for ownership alone. Call get_property_details only when the user needs exact billable property scalars or distress indicators. When resolved is false, confirm the user's pick from suggestions[] before downstream tools; if truncated or many units match, add a unit number or use search_properties for the full property set.

Create a saved dynamic Audience only after the user confirms both the criteria and name. Required: criteria (an array of {"name","value"} objects) and name (maximum 50 characters). Optional: monitored (default false). Never bills or purchases property data. Before setting monitored=true, explain that monitoring also enables Insights and Automations, that a monitored Audience stops growing when it reaches the package limit, and get explicit confirmation. Each criterion accepts at most 500 values. Returns audience_id, the stored name, total_count, effective monitored state, and related_tools[].

Non-billable property set characterization for all 50 US states and DC nationwide. Required: criteria, a JSON-encoded array of {"name","value"} objects. Call get_criteria to discover criterion names and value shapes; this description intentionally does not enumerate them. Optional: includeFacets. Every success returns total_result_count, the criteria echo, purchase: 0, and related_tools rows. When includeFacets is true, signals contains flat facet-label counts when total_result_count is at least 25 with no upper cap, and is empty below that privacy floor. Never returns property rows, RadarIDs, addresses, criteria catalog data, or an applet handoff. Never bills. After a satisfactory search, recommend create_dynamic_audience to save the property set; marketing flows must not default to get_properties_details. Use get_properties_details with count_only before purchasing billable rows. Use get_properties_insights for grouped, tab-depth characterization beyond flat signals; that tool accepts only 25 through 100,000 results.

Fetch billable property rows for a property set matching criteria. PropertyRadar covers all 50 US states and DC nationwide. Required: criteria (JSON-encoded array, same shape as search_properties). Optional: count_only (true returns total_result_count and estimated_cost with empty results[], non-billable — recommend before purchase); fields (default Standard fieldset per get_fields; comma-separated field ids allowed); limit (default 100, max 1000); start for paging; sort (e.g. AVM:desc). Saved Audience uses InList inside criteria — no audience_id parameter. Bills per row returned on purchase; usage is non-refundable — use count_only and search_properties before large sets. Each row is flat scalars only (no transaction/comp/person arrays or Contacts-group fields); use get_property_details, get_property_transactions, get_property_comps, or get_property_persons for depth. Not for a single RadarID (use get_property_details). Every success includes related_tools[].

Discover property search criteria ids, types, and example values before calling search_properties. PropertyRadar covers all 50 US states and DC nationwide. Call this tool at least once before your first search_properties in a workflow; make one scoped discovery call for the filters currently requested and do not repeat discovery for criteria already established in the conversation. Default (no params) returns a lightweight groups[] index with criteria_ids[] per group and subgroup plus upgrade_criteria_ids[] — not the full catalog. Scope with groups (an array of group names, or names prefixed "-" to exclude; never a bare string), criteria_ids (an array of exact catalog ids), and/or query (one literal substring across titles, descriptions, enumerations, and MCP usage guidance; not a space-separated multi-keyword search). Params compose in one call; every scoped call returns full matching criteria[] detail with included, description, criteria_type, optional criteria_example, enumeration[], and optional usage_guidance. Every success includes related_tools[] for search_properties, optional get_suggestions, and audience/insights paths. Suggestion-backed criteria include suggestion_field. County names always require get_suggestions to resolve the positive integer FIPS before search; complete City or Subdivision values can be passed directly. Never bills.

Non-billable value lookup before search_properties. Required for every County name so the agent uses the returned positive integer FIPS criteria fragment; optional for an incomplete or ambiguous City or Subdivision. PropertyRadar covers all 50 US states and DC nationwide. Do not call for a complete City paired with a two-letter State because those values can be passed directly to search_properties. Required: suggestion_field (City, County, or Subdivision) and query (prefix/typeahead). Optional: criteria (API-format scope array, e.g. State before City or County) and limit. Returns results[] with label and criteria fragments exactly as the Suggestions API returns them — merge into search_properties without reformatting. Every success includes related_tools[] for get_criteria, search_properties, and create_dynamic_audience. Empty prefix matches return results: []. SiteAddress and other address fields are not supported — use resolve_address. Never bills.

Frequently asked questions

What is the PropertyRadar remote MCP server?

The PropertyRadar remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.propertyradar.com/mcp, so AI assistants can connect to it without installing or running anything locally.

How do I connect to the PropertyRadar MCP server?

Add the endpoint https://mcp.propertyradar.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

Does the PropertyRadar MCP server require authentication?

Yes. PropertyRadar uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

Which transport does the PropertyRadar MCP server use?

PropertyRadar exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments

More remote MCP servers

ASO Atlas

App Store keyword research, rank tracking, competitor analysis and authorized performance data.

Adobe Journey Optimizer

Understand and troubleshoot your Journeys and Campaigns

42min

Official 42min MCP server: let Claude, ChatGPT, Cursor or any MCP client manage your meeting scheduling. Check availability, find free slots, book, cancel and reschedule meetings, manage recurring series, secret booking

AccountHub

One MCP connection for all your Gmail, Google Calendar, Drive and Contacts accounts, Slack workspaces and Notion — free.

AdLoop Cloud

Hosted AdLoop: Google Ads, Reddit Ads, GA4 and Tag Manager in claude.ai, ChatGPT and more, with a preview before every change.