Skip to main content
Glama
hyperionxmota

Cook County / Chicago Property Data

README.md
# Cook County / Chicago Property Data — MCP server

[![hyperionxmota/cook-county-property-mcp MCP server](https://glama.ai/mcp/servers/hyperionxmota/cook-county-property-mcp/badges/score.svg)](https://glama.ai/mcp/servers/hyperionxmota/cook-county-property-mcp)
[![x402 resources](https://img.shields.io/badge/x402-resource_list-1f6feb)](https://api.ingest0r.com/.well-known/x402)
[![A2A agent card](https://img.shields.io/badge/A2A-agent_card-1f6feb)](https://api.ingest0r.com/.well-known/agent-card.json)
[![OpenAPI](https://img.shields.io/badge/OpenAPI-3.1-1f6feb)](https://api.ingest0r.com/openapi.json)
[![llms.txt](https://img.shields.io/badge/llms.txt-live-1f6feb)](https://api.ingest0r.com/llms.txt)
[![Pricing](https://img.shields.io/badge/pricing-machine_readable-1f6feb)](https://api.ingest0r.com/pricing)

A hosted, **pay-per-call** [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server for **Cook County, Illinois — including the City of Chicago** — property records: parcels, recorded sales & deed history, building permits, and property-tax assessment history, joined and normalized into one answer. Plus comparable sales (comps) and a lightweight automated valuation.

No signup, no API key — pay per call via the [x402](https://x402.org) protocol (USDC on Base or Solana).

## What this adds over raw open data

This returns **finished, joined answers** — not raw rows you have to query and stitch. The county open data (Socrata) can't give you:

- **Building permits linked to a PIN.** The Chicago permits feed has **no PIN field** — the permit→parcel link is *derived here* (exact address match + nearest-parcel geo match). You can't reproduce this with a raw SoQL query.
- **A street address on a parcel.** Parcel Universe has **no address**; it's joined in from a separate dataset here.
- **Comparable-sales valuation.** Arm's-length filtering, same-neighborhood/class matching, and an implied low/median/high range — derived analysis, not a row fetch.

So one call returns a normalized property record; against raw open data you'd orchestrate multiple datasets and rebuild joins that don't exist upstream.

## Connect

- **Remote MCP endpoint:** `https://api.ingest0r.com/mcp` (streamable-http — add it to any MCP client; nothing to install)
- **PulseMCP:** [cook-county-property-data](https://www.pulsemcp.com/servers/cook-county-property-data)
- **Official MCP Registry:** `com.ingest0r.api/cook-county-property-data`
- **Website / HTTP API:** https://api.ingest0r.com
- **Free example response (no payment):** https://api.ingest0r.com/v1/sample

## Tools

| Tool | Price | Description |
|------|-------|-------------|
| `get_free_sample` | **FREE** | Fixed example of every response shape — evaluate before paying. |
| `search_chicago_property_by_address` | **FREE** | Resolve a street address → parcel PIN(s). The no-PIN entry point. |
| `get_cook_county_parcel` | $0.01 | Single parcel record by 14-digit PIN. |
| `get_cook_county_property_dossier` | $0.03 | Full dossier: address, sales & deed history, permits, assessment history. |
| `find_chicago_comparable_sales` | $0.10 | Comparable sales + implied low/median/high valuation. |

The PIN tools return an HTTP **402** with machine-readable x402 payment terms; pay in USDC and retry. Search and the sample are free — and three real parcels are served **free on the paid routes** (live data you can verify against the county's own portals): [09253050270000](https://api.ingest0r.com/v1/dossier/09253050270000) · [09253060510000](https://api.ingest0r.com/v1/dossier/09253060510000) · [09253140190000](https://api.ingest0r.com/v1/dossier/09253140190000).

## Data & coverage

~1.9M parcels, refreshed nightly from Cook County Assessor, Cook County Recorder of Deeds, and City of Chicago open-data portals (Socrata). **Property-keyed public records only — no owner/occupant personal data.**

## Use cases

Real-estate due diligence, automated valuation / comps, title & lien research prep, lead enrichment, and market analysis — for autonomous agents and LLM pipelines.

TDQS

A4.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: address resolution, basic parcel lookup, full property dossier, and comparable sales/valuation. No overlap in functionality, and the descriptions explicitly guide usage order.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case. The verbs (find, get, search) accurately describe the operation, and the objects are specific and descriptive.

Tool Count5/5

4 tools is an appropriate scope for a property data API. It covers the essential workflows (address resolution, parcel lookup, full dossier, and valuation) without unnecessary bloat.

Completeness5/5

The tool set provides a complete workflow for accessing Cook County property data: address-to-PIN resolution, individual parcel details, a comprehensive dossier with sales/permits/assessments, and comparable sales analysis. No obvious gaps for a read-only data service.

Maintenance

ActivityStale
ResponsivenessUnresponsive