LIHTC Year 15 and compliance-period data in Alaska

39 dated Alaska 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 Alaska, 6 records are dated ahead of today. Every one of them is listed below in full, and they are free. 39 have been published in Alaska in total, counting those already past.

All 6 in Alaska

That is the whole Alaska 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	200 W 20TH AVELOUSSAC PLACE APTS, ANCHORAGE, AK: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 120 units.	ANCHORAGE	120	—	hud_lihtc
2026-12-31	105 BURKHARR STSAWMILL CREEK, SITKA, AK: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 56 units.	SITKA	56	—	hud_lihtc
2027-12-31	4047 MAIN STREETHARBOR RIDGE-HOMER ASSOCIATES, LLC, HOMER, AK: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 24 units.	HOMER	24	—	hud_lihtc
2027-12-31	1821 SWETMAN AVEKIMBERLY COURT, SEWARD, AK: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 24 units.	SEWARD	24	—	hud_lihtc
2027-12-31	4047 MAIN STREETHARBOR RIDGE, HOMER, AK: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 24 units.	HOMER	24	—	hud_lihtc
2027-12-31	2785 TRAILSIDE LOOPTRAILSIDE HEIGHTS I, ANCHORAGE, AK: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 66 units.	ANCHORAGE	66	—	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":"AK","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 Alaska, 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 Alaska 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.