Due for re-check: the scheduled review date of 2026-11-03 has passed. Every value below still carries the source it was taken from and the passage that states it — check it against the link.

1,561 records

Is this bank under an open Federal Reserve enforcement action?

1,561 records covering 1,412 banking organisations, one fact each. Every value is transcribed from the source that states it and carries the sentence it was taken from: 1 source across 1 site, last checked 2026-10-13, due for re-check by 2026-11-03. Every record has a page of its own, quoting the line that states it.

Recent changes

• 2026-10-193 records added or updated
• 2026-10-131 record added or updated
• 2026-10-051 record added or updated
• 2026-09-223 records added or updated
• 2026-09-011 record added or updated

Full change history · Atom feed

About this data

Which US banking organisations are or have been subject to a Federal Reserve supervisory enforcement action, what kind of action it is, when it took effect, and whether the Board has since terminated it. Each record is one action against one banking organisation, carrying the organisation's name and location exactly as the Board publishes them, the action type ('Written Agreement', 'Cease and Desist Order', 'Civil Money Penalty', 'Prompt Corrective Action', 'Formal Agreement'), the effective date, the termination date where one exists, and the link to the Board's own order or press release. Answers 'is this bank under a consent order', 'does the Federal Reserve have an open enforcement action against my sponsor bank', 'when was the written agreement with this holding company terminated', and 'which banks were placed under a Federal Reserve enforcement action this year'. The Board's own human-facing search page contains none of this text — it is a JavaScript application, and an assistant that fetches it gets a page on which the string 'cease and desist' does not appear — so the only agent-readable route to the answer is a CSV nobody links to from an answer page.

The data

Showing the first 400 of 1,561 records. Every record has its own page, with its source and the quoted line that states it; these list the rest.

• Records 1–4001st Brookfield, Inc., Brookfield, Illinois · Written Agreement · 2010-10-28 … BankSouth Corporation, First Chattanooga Corporation and Citizens Bank, Lawton, OK · Written Agreement · 1992-08-27
• Records 401–800BankVest, Inc., Castle Rock, Colorado · Written Agreement · 2011-02-02 … First New York Bank for Business Corp., New York, NY · Written Agreement · 1991-11-26
• Records 801–1,200First of Huron Corp., Bad Axe, Michigan · Written Agreement · 2011-07-07 … PGB Holdings, Inc. and Pacific Global Bank, both of Chicago, Illinois · Written Agreement · 2011-06-30
• Records 1,201–1,561Piedmont Trust Bank, Martinsville, VA · Cease and Desist Order · 1993-08-05 … Zia New Mexico Bank, Tucumcari, NM · Prompt Corrective Action · 1999-01-26

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 1 source this dataset was assembled from.

• federalreserve.govhttps://www.federalreserve.gov/supervisionreg/files/enforcementactions.csv

Machine-readable

• data.jsonThe whole dataset — every record with its source URL and source quote.
• Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
• data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
• changes.xmlAtom feed of what changed and when — poll this instead of re-fetching the dataset. Also as changes.json.
• What changedThe same change history as a readable page — each date, what moved, and the records' current state.
• How this is made and checkedWhat "verified against source" does and does not mean.

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup bank-enforcement-actions action="Written Agreement"

npx -y refsource lookup bank-enforcement-actions action="Written Agreement"

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "Federal Reserve enforcement actions against banks and holding companies: action type, effective date and whether it has been terminated", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `bank-enforcement-actions`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

1,561 records. last verified against source 2026-10-13. due for re-check by 2026-11-03.

Licence. Facts extracted from the Federal Reserve Board's published enforcement-actions data file, a US federal government publication carrying no licence statement. Institution names, action types and dates are facts and not copyrightable. Every record links back to the Board's own order or press release and quotes the source row verbatim.