LIHTC Year 15 and compliance-period data in Alabama

158 dated Alabama records, read from filed public sources rather than modelled, and callable by an AI agent with no key.

Short answer

Which LIHTC properties are reaching the end of a compliance period? In Alabama, 16 records are dated ahead of today. Every one of them is listed below in full, and they are free. 158 have been published in Alabama in total, counting those already past.

All 16 in Alabama

That is the whole Alabama population for this family, not a sample. The call underneath returns the same rows, up to its own fifty-row ceiling.

Date	Property	City	Units	Amount	Source
2026-12-31	700 JUBILEE CIRJUBILEE, PELL CITY, AL: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 72 units.	PELL CITY	72	—	hud_lihtc
2026-12-31	381 34TH AVE ECHASTAIN MANOR, TUSCALOOSA, AL: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 56 units.	TUSCALOOSA	56	—	hud_lihtc
2026-12-31	5821 OLD PASCAGOULA RDTHE GARDENS AT WELLINGTON, MOBILE, AL: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 51 units.	MOBILE	51	—	hud_lihtc
2026-12-31	1520 VILLAS AT CLOVERDALE SETHE VILLAS AT CLOVERDALE, CULLMAN, AL: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 37 units.	CULLMAN	37	—	hud_lihtc
2026-12-31	1042 BAY SPRINGS RDPINE VIEW CROSSING II, CENTRE, AL: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 40 units.	CENTRE	40	—	hud_lihtc
2026-12-31	1066 CODY RD NHALLMARK AT MOBILE, MOBILE, AL: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 92 units.	MOBILE	92	—	hud_lihtc
2027-12-31	550 SMYTHE STTHE PLAZA AT CENTENNIAL HILL PHASE I, MONTGOMERY, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 129 units.	MONTGOMERY	129	—	hud_lihtc
2027-12-31	1330 SHUG JORDAN PKWYSHEPHERD'S COVE, AUBURN, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 72 units.	AUBURN	72	—	hud_lihtc
2027-12-31	5300 MILLENNIUM DR NWFRANKLIN HILLS, HUNTSVILLE, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 56 units.	HUNTSVILLE	56	—	hud_lihtc
2027-12-31	1925 CENTRAL PKWYKENDRICK'S WAY, MONTGOMERY, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 72 units.	MONTGOMERY	72	—	hud_lihtc
2027-12-31	1004 28TH AVEHALLMARK AT PHENIX, PHENIX CITY, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 56 units.	PHENIX CITY	56	—	hud_lihtc
2027-12-31	1060 COMER STBRADBERRY POINTE, ALEXANDER CITY, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 56 units.	ALEXANDER CITY	56	—	hud_lihtc
2027-12-31	1570 LAWRENCE ST ECREEKSTONE APTS, RUSSELLVILLE, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 48 units.	RUSSELLVILLE	48	—	hud_lihtc
2027-12-31	2808 TENTH AVEROSEDALE REDEVELOPMENT I, TUSCALOOSA, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 88 units.	TUSCALOOSA	88	—	hud_lihtc
2027-12-31	494 STRATFORD DRAVON SQUARE TOWNHOMES, OZARK, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 56 units.	OZARK	56	—	hud_lihtc
2027-12-31	3195 LINCOLN DRHALLMARK AT SELMA, SELMA, AL: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 56 units.	SELMA	56	—	hud_lihtc

Read from the published event tape on 2026-09-12.

The call that returns this

One anonymous POST. No key, no signup, no rate card. Raise limit to 50, or change state to any of the 56 covered.

curl -s https://exchange-production-9123.up.railway.app/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_property_events","arguments":{"event_type":"COMPLIANCE_PERIOD_ENDING","state":"AL","within_days":1825,"limit":500}}}'

Putting this in your own agent

The same endpoint is a Model Context Protocol server, so an assistant can ask it the question instead of you reading a table. It answers for every covered state, not just Alabama, and it is the same free tier.

Add to Cursor Add to VS Code

Claude Code

one command, then it is available in every session

claude mcp add --transport http dfx-real-estate https://exchange-production-9123.up.railway.app/mcp

Claude Desktop

claude_desktop_config.json, then restart the app. It cannot reach a remote server directly, so this bridges through mcp-remote.

{
  "mcpServers": {
    "dfx-real-estate": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://exchange-production-9123.up.railway.app/mcp"
      ]
    }
  }
}

Cursor, Windsurf, Cline and Zed

the mcp.json their settings panel writes

{
  "mcpServers": {
    "dfx-real-estate": {
      "url": "https://exchange-production-9123.up.railway.app/mcp"
    }
  }
}

VS Code

the servers key, which is spelled differently to everything above

{
  "servers": {
    "dfx-real-estate": {
      "type": "http",
      "url": "https://exchange-production-9123.up.railway.app/mcp"
    }
  }
}

Then ask it this

Nothing names DFX. If the install worked, the assistant picks the tool itself.

Which LIHTC properties in Alabama reach Year 15 in the next three years?

There is no signup, no API key and no OAuth for anything free, and eleven of the twelve tools are free. A plain GET on the endpoint returns every tool schema, so a client can be pointed at it and evaluated before it is trusted.

Where this does not help

Compliance periods are statutory and every one falls on 31 December, so a count bucketed by day shows a December cliff that is an artefact of the statute rather than a market event.

The same question in other states

Facts on this page were last checked against the running product on August 19, 2026. Prices are read from the live billing configuration, so this page and your invoice cannot disagree. The machine-readable version of this record is at /ai/entity.json.