Nyc Property Intel MCP Server

Nyc Property Intel MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP server that gives Claude AI access to 20+ NYC public record datasets for real estate due diligence. Ask Claude about any NYC property in plain English — violations, liens, sales history, ownership, permits, rent stabilization, zoning.

What the assistant can call

Once Nyc Property Intel is connected, these are the calls the assistant has available:

• lookup_property — Resolve any NYC address or BBL to a full property profile: owner, building class, zoning, FAR, assessed value, lot dimensions. **Always call this
• get_property_issues — HPD housing violations (Class A/B/C), DOB building code violations, and ECB/OATH monetary penalties. Filter by severity, status, and date
• get_property_history — DOF sales records and ACRIS deed transfers. Price trajectory, buyer/seller names, document types going back to 2003
• get_hpd_complaints — Tenant-reported HPD complaints — leading indicators of building distress before formal violations are issued
• get_hpd_litigations — HPD housing court cases, open judgements, and harassment findings against building owners
• get_hpd_registration — Legal owner, managing agent, and head officer registration records
• get_building_permits — DOB job filings: new buildings, alterations, demolitions, sign permits. Status, cost estimate, applicant name
• get_liens_and_encumbrances — DOF tax lien sale list entries and ACRIS mortgage records. Outstanding liens, lender names, amounts, satisfactions
• get_tax_info — Tax assessments, market value estimates, taxable value, and active exemptions (421a, J-51, STAR)
• get_rent_stabilization — Rent-stabilized unit counts by year (2007–2017). Trend analysis for deregulation signal
• search_comps — Comparable sales by zip code. Filter by building class, price, date. Includes quarterly market stats
• search_neighborhood_stats — Area-level aggregates: property stock, median sale prices, violation rates, rent stabilization share

Configuration and credentials

You will need 4 environment variables: DATABASE_URL, YOUR_TOKEN, NYC_GEOCLIENT_SUBSCRIPTION_KEY, SOCRATA_APP_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.12+ - uv package manager - PostgreSQL 16+ - nycdb CLI (pip install nycdb)

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Nyc Property Intel's toolset — lookup_property, get_property_issues, get_property_history and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ccedacero; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Nyc Property Intel.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the nyc property intel mcp server does with a few real requests.