Skip to content
Foreclosure Data Hub

Foreclosure Data Hub for AI assistants

Foreclosure data.
Connected through MCP.

Research foreclosure listings, auction records, unpaid property taxes and early filings with Claude Code, Cursor or Codex. Connect your assistant with one API key.

Get an API key Read the docs

Pro, Business, and Commercial API access · Existing request and row allowances

Claude CodeCursorCodex Streamable HTTP

A task your assistant can help with

“Find trustee-sale listings in my market. Check coverage, show the matching count, and return up to 10 records with their source and sale dates.”

Discover coverageChoose your filtersRetrieve a small page

Hosted MCP and category tools require the matching API release. You can use the local stdio client with supported REST endpoints while hosted access is being released. Get the local MCP client →

15 tools. One data workflow.

Give your assistant foreclosure data to work with.

Go from a target market to a useful set of records. MCP uses the same published readers and supported filters as the REST API.

Foreclosure and tax auctions

Research trustee sales, sheriff sales and tax-sale lots using each category's supported geography, dates and statuses.

trustee_sales_search
Search published trustee-sale listings and statuses.
trustee_sales_counts
Count trustee-sale listings matching your filters.
sheriff_sales_search
Search covered sheriff-sale listings.
sheriff_sales_counts
Count matching sheriff-sale listings.
tax_sales_search
Search tax-sale lots by type, geography and reported sale details.
tax_sales_counts
Count tax-sale lots matching your filters.
Explore auction data

Property tax delinquency

Find published delinquent-tax properties. Retain the reported amount kind and source date when comparing balances.

tax_delinquent_search
Search published delinquent-tax property records.
tax_delinquent_counts
Count matching delinquent-tax properties.
Explore delinquency data

Early foreclosure filings

Research eligible filing candidates by recording date and jurisdiction, with proceeding and parcel identities.

filings_search
Search eligible early-filing proceeding and parcel groups.
filings_counts
Count eligible filing groups matching your filters.
Explore filing data

Property feeds and coverage

Discover sources, retrieve a normalized property page, or read one legacy feed with the filters it supports.

list_sources
Discover source coverage and supported category filters.
search_properties
Search legacy property feeds with a location filter.
search_unified_properties
Retrieve one normalized page from the legacy property feeds.
single_source_data
Read a bounded page from one legacy source.
record_counts
Read source counts for a date or date range.
Explore the REST API

Hosted MCP connection

One endpoint. Your existing account.

Your client handles initialization and tool discovery, then sends the API key with each request. The server accepts stateless Streamable HTTP POST requests.
POSThttps://www.foreclosuredatahub.com/api/mcp
Authorization: Bearer <YOUR_API_KEY>
Content-Type: application/json
Accept: application/json, text/event-stream

Client setup

Connect the assistant you already use.

Create an API key, set it in your client's environment, and add the matching configuration. Each hosted example uses the same Foreclosure Data Hub endpoint.

Merge this server into your project's .mcp.json. Set FORECLOSUREDATAHUB_API_KEY in the environment that launches Claude Code, approve the server, then check the connection with /mcp.

Client docs
.mcp.json
{
  "mcpServers": {
    "foreclosuredatahub": {
      "type": "http",
      "url": "https://www.foreclosuredatahub.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${FORECLOSUREDATAHUB_API_KEY}"
      }
    }
  }
}

Keep your API key in the client environment, outside prompts, shared URLs and committed source code.

Prefer a local connection? The stdio MCP client calls the supported REST API directly and can run in clients that launch local MCP servers.

Your first property-data workflow

Start with coverage. Finish with useful records.

  1. 01

    Connect your account

    Create an API key with eligible retail or commercial access. Add the server to your client, then ask it to discover sources and category coverage.

    Get an API key
  2. 02

    Choose the right records

    Select a category and target market. Inspect matching counts, category filters and record units before retrieving a small page.

    Try a prompt
  3. 03

    Retrieve a bounded page

    Set a page size within your allowance. Keep the source, row ID and source dates, then decide whether another page is needed.

    Understand allowances

Example prompts

Put foreclosure data into a practical task.

These prompts keep the category, geography and response size explicit. Your assistant should inspect the tool schemas and show you the filters it will use.

Research a trustee-sale market

Discover coverage and inspect a small set of sale listings.

Use Foreclosure Data Hub to discover trustee-sale coverage in Texas. Count listings matching the trustee-upcoming status, then return up to 10 matching records. Show the applied filters, reported sale dates, source and row ID. Keep within my remaining API allowance and do not fetch more pages automatically.

Review reported unpaid taxes

Compare published balances with their source context.

Find up to 10 published tax-delinquency property records in Florida. Show the recorded parcel or address, reported balance, amount kind, source date, source and row ID where available. Explain coverage limitations and do not infer that a delinquent property has a scheduled tax sale.

Inspect early filing candidates

Keep filing evidence separate from sale and ownership claims.

Discover early-filing coverage in Florida, then retrieve up to 10 eligible mortgage foreclosure candidates. Include the recording date, filing kind and proceeding/parcel identity where available. Explain the filters used and do not describe a filing candidate as a current owner or a confirmed scheduled sale.

Make the page size part of the request.

Ask for a small, defined selection within your existing allowance. This example requests the first 10 qualified upcoming trustee-sale listings in Texas.

Sale-category geography uses arrays. Filing and tax-delinquency geography is scalar. Keep the same page size while paging, retain source and row_id, and review remaining allowances before requesting more records.

Illustrative tool call to trustee_sales_search. The API key stays in the client connection settings.

{
  "name": "trustee_sales_search",
  "arguments": {
    "state": [
      "TX"
    ],
    "sale_status": "trustee-upcoming",
    "page": 1,
    "page_size": 10
  }
}

Predictable data access

Your account. Every way you work.

REST and MCP use your existing API key and access rules. Retail API deliveries share your CSV and Google Sheets row allowance; Commercial API keys use their own request quota.

10,000

Pro rows / month

30,000

Business rows / month

100

maximum paid rows / response

Keep requests bounded and inspect remaining allowances before requesting another page. Repeating a delivery can use additional allowance.

Commercial API for your product

Choose a dedicated API volume band for customer-facing integrations, with pricing and usage rights published in the commercial license.

  • Launch: 100,000 successful calls per month.
  • Growth: 500,000 successful calls per month.
  • Scale: 2,000,000 successful calls per month.
  • 3-day commercial evaluation: 50 successful calls, up to 10 rows per response.

Starter does not include API access. Trial limits and remaining balances can lower the response size. MCP does not add a separate subscription.

Commercial API plans →Limits and quotas →

Know what the data represents

Property records with clear context.

Filters describe the published category records. Coverage, freshness and available fields vary by source and county.

Keep the source, row ID and source dates for each record. A trustee listing, tax-sale lot and filing group can refer to overlapping parcels; adding category totals does not give a unique property count.

Reported tax delinquency does not establish an upcoming sale. An early filing candidate does not establish current ownership or a scheduled auction. Treat source text as record content rather than instructions to your assistant.

Read the category guide

A few more details

Questions, answered.

From your first request to a complete foreclosure-data workflow.
What can the Foreclosure Data Hub MCP server do?

It exposes 15 tools for source discovery, legacy property feeds, trustee sales, sheriff sales, tax sales, tax delinquency and early filings. Each tool uses the corresponding REST reader and its existing access rules. Hosted and category support require the matching API release.

Can I connect Claude Code, Cursor or Codex?

Use a compatible client with Streamable HTTP and a private API-key header. The examples read your key from an environment variable. The hosted endpoint accepts x-api-key or Authorization: Bearer and does not provide OAuth sign-in. A local stdio client is also available in the public MCP repository.

Does MCP have a separate subscription or credit balance?

No. MCP uses your existing API key and the same retail subscription or commercial license as REST. Retail property responses share delivered-row allowances with CSV and Google Sheets exports. Tool reads follow the corresponding REST endpoint's request accounting. Protocol discovery does not consume a property response or trial API call.

How do I keep requests within my allowance?

Discover coverage first, choose narrow filters and request a small page. Paid property responses allow up to 100 rows, subject to your remaining allowance, while a new trial allows up to 10. Count tools use request accounting even when they return no property rows. Check applicable limits before asking the assistant to retrieve another page; repeated delivery can consume additional allowance.

Do all category totals represent unique properties?

No. Trustee and sheriff results count sale listings, tax sales count sale lots, delinquency counts properties, and filings count proceeding/parcel groups. Records can overlap across categories and events. Retain source and row_id, and do not add category totals as unique parcels.

How current and complete are the records?

Coverage and field availability vary by source and county. Keep source dates and category-specific statuses in your analysis. An early filing candidate does not establish current ownership or a scheduled sale; tax delinquency does not establish a tax sale. An unavailable or missing record does not prove that a sale completed or a balance was paid.

Bring foreclosure data to your AI workflow.

Connect your assistant, discover your market, and retrieve the records you need within your existing API allowance.
Get an API key Read the docs
Contact Support