HMDA Mortgage Data MCP server

• get_aggregate_statsFree

  Get aggregate mortgage lending statistics for a geographic area. Returns summary statistics including total applications, originations, denials, and loan amounts. Useful for understanding overall lending activity in a state or county. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). county_fips: Five-digit county FIPS code (e.g. '06037' for LA County). year: Data year (e.g. 2022). Defaults to 2022 if not specified.

• get_denial_reasonsFree

  Get mortgage denial reasons breakdown for a geographic area. Returns the distribution of denial reasons for mortgage applications that were denied. Useful for identifying barriers to homeownership in specific communities. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). county_fips: Five-digit county FIPS code (e.g. '06037' for LA County). year: Data year (e.g. 2022). Defaults to 2022 if not specified.

• get_lending_by_raceFree

  Get mortgage lending patterns disaggregated by race and ethnicity. Returns mortgage origination and denial data broken down by the race/ethnicity of the applicant. Useful for fair lending analysis and identifying disparities in mortgage access. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). county_fips: Five-digit county FIPS code (e.g. '06037' for LA County). year: Data year (e.g. 2022). Defaults to 2022 if not specified.

• get_mortgage_dataFree

  Get Home Mortgage Disclosure Act (HMDA) loan-level data. Returns mortgage application and origination records reported by financial institutions under HMDA. At least one geographic filter (state or county_fips) is recommended to limit results. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). county_fips: Five-digit county FIPS code (e.g. '06037' for LA County). year: Data year (e.g. 2022). Defaults to 2022 if not specified. action_taken: Loan action code: '1' (originated), '2' (approved not accepted), '3' (denied), '4' (withdrawn), '5' (incomplete). loan_type: Loan type code: '1' (conventional), '2' (FHA-insured), '3' (VA-guaranteed), '4' (USDA/RHS). limit: Maximum number of records to return (default 100, max 1000).

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 58ms20/20
• Tool poisoning4 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Safety score

69/100

higher than 32% of 48,243 servers

Tools

4

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

106 ms

faster than 83% of 30,027 servers

HMDA Mortgage Data: common questions

Is HMDA Mortgage Data MCP server safe?

With care: it is graded C, so read the findings first (69/100). Read the HMDA Mortgage Data safety report

How do I install HMDA Mortgage Data?

It runs remotely at mcp.olyport.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does HMDA Mortgage Data need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is HMDA Mortgage Data maintained?

The latest release is v1.1.0.

Is HMDA Mortgage Data up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does HMDA Mortgage Data compare with other MCP servers?

safety score 69/100 (higher than 32% of 48,243 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.