Fac MCP server

@pipeworx/fac

Federal Audit Clearinghouse MCP — US single-audit filings (Uniform Guidance, formerly OMB A-133): who spends federal grant money, under which Assistance Listing program, and what the auditors found. api.data.gov key.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

• facsearchaudits(auditeename|uei|ein|state|zip|audityear|mintotalexpended, ...) — find audits; returns report_id, organization identity (including the ZIP on file), total federal awards expended, oversight agency, FAC acceptance date.
• facgetaudit(report_id, ...) — one audit plus every federal program row on its Schedule of Expenditures of Federal Awards (Assistance Listing number, program name, dollars expended, major-program flag, opinion type), auditee/auditor contact detail, and findings when FAC carries them.
• facauditfindings(reportid | auditeename | uei, ...) — findings recorded against an audit, or swept across every audit one recipient filed, rolled up into a severity summary (material weaknesses, significant deficiencies, questioned costs, repeat findings, modified opinions). include_text attaches the narrative finding text.
• facfederalawardsbyprogram(cfda | federalagencyprefix + federalawardextension, ...) — who expended money under a CFDA number (e.g. 93.224), ranked by dollars, joined to recipient name/state/year.
• facrecipientaudithistory(uei | auditeename | ein, ...) — one recipient's audits year by year with total expended per year and a percent-change read on the trend.

Forgiving aliases throughout: query / q / name for auditeename; zip / auditeezip / zipcode / zipcode / postalcode; cfda / programnumber / assistancelisting / program all accept "93.224", "93-224", "93224", or a bare "93" for every program at that agency.

An argument this pack does not recognize is reported, not dropped. Any unknown key comes back in ignored_arguments with a warnings line saying the filter was not applied and listing what the tool does accept. Silently discarding the most specific thing a caller said is worse than erroring, because the response still looks like an answer.

Auth

Platform key (PLATFORMDATAGOVKEY) with BYO fallback via ?_apiKey=.

This is an api.data.gov umbrella key — the same key works across every federal API behind the umbrella. Register free at https://api.data.gov/signup. Sent as the X-Api-Key header. A registered key gets 1,000 requests/hour; DEMOKEY works for smoke tests but caps around 30/hour and 50/day per source IP**.

Data sources

• https://api.fac.gov/general — one row per accepted audit submission (auditee identity, audit year, total federal awards expended, oversight agency, acceptance date)
• https://api.fac.gov/federal_awards — one row per federal program inside an audit (agency prefix + award extension, program name, amount expended, major-program flag, report type)
• https://api.fac.gov/findings — audit findings per report; carries auditeeuei and audityear alongside reportid, plus the ismaterialweakness / isrepeatfinding / isquestionedcosts Y-N flags and typerequirement
• https://api.fac.gov/findingstext — narrative finding text, keyed reportid + findingrefnumber (attached only when include_text: true)
• API docs: https://www.fac.gov/developers/ · Assistance Listing lookup: https://sam.gov/content/assistance-listings

Name and ZIP matching

ZIP is stored in two encodings and must be prefix-matched. auditeezip holds 5 digits (75082) for some rows and 9-digit ZIP+4 with no separator (009601588, 750814198) for others, so eq. misses most of the table — a Puerto Rico caller passing 00960 would match nothing at all. The pack filters on the 5-digit prefix (auditeezip=like.00960*), which is the only part both encodings share, and accepts ZIP+4 input by truncating it.

Shortened. The full README is on GitHub.