# Fac (npm · @pipeworx/mcp-fac)

Federal Audit Clearinghouse (FAC) MCP — US single-audit data, served from a served from a…

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-fac/fac-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-fac/fac-mcp)
- npm · `@pipeworx/mcp-fac`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-fac/pipeworx-mcp-fac.md), [page](https://verifymcp.io/servers/pipeworx-io-fac/pipeworx-mcp-fac)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-fac`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fac).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2415 tokens (~345/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Fac MCP server?

Fac runs locally as an npm package, launched with npx -y @pipeworx/mcp-fac. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-fac -- npx -y @pipeworx/mcp-fac
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-fac": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fac"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-fac": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fac"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-fac -- npx -y @pipeworx/mcp-fac
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-fac": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-fac"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-fac --command npx --arg -y --arg @pipeworx/mcp-fac
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-fac:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-fac"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-fac": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-fac"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-fac -t stdio -c npx -a -y @pipeworx/mcp-fac
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-fac": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fac"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +1)

- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (7)

### `fac_search_audits` (~589 tokens)

Search US single audits (Uniform Guidance / former OMB A-133) filed with the Federal Audit Clearinghouse — "the FAC" — by auditee name, UEI, EIN, state, ZIP code, audit year, or minimum federal dollars expended. Covers every kind of non-federal recipient: cities, towns, counties, school districts, fire and water districts, housing authorities, universities, tribes, hospitals and nonprofits. Returns the report_id, summary_url (the official FAC dissemination summary page for that submission), the organization name, city, state and ZIP on file, total federal awards expended for the year, the cognizant/oversight agency, and the date FAC accepted the submission. Puerto Rico municipalities are found under either their Spanish or English legal name. Answered without a live api.data.gov key or its rate limit. Answers "does this grant recipient file a single audit and how much federal money does it run", and "what is the FAC report ID / summary URL for this entity".

Input parameters:

- `ascending` (boolean): Sort ascending instead of descending.
- `audit_year` (number): Fiscal audit year, e.g. 2023.
- `audit_year_min` (number): Earliest audit year to include.
- `auditee_name` (string): Organization name, matched as a forgiving case-insensitive substring (e.g. "stanford", "county of los angeles"). A municipality name is searched in both languages FAC files under, so "MUNICIPIO DE BA…
- `ein` (string): Employer Identification Number, digits only, exact match. Alias: auditee_ein.
- `limit` (number): Rows to return, 1-200 (default 20).
- `min_total_expended` (number): Only audits whose total federal awards expended is at least this many dollars (e.g. 100000000 for billion-dollar-scale recipients).
- `offset` (number): Rows to skip, for paging.
- `order_by` (string): Sort column, descending by default. Defaults to total_amount_expended.
- `state` (string): 2-letter auditee state code (e.g. "CA"). Alias: auditee_state.
- `uei` (string): SAM.gov Unique Entity Identifier (12 chars), exact match. Alias: auditee_uei.
- `zip` (string): Auditee ZIP code, matched on the 5-digit prefix so it works against both the 5-digit and 9-digit forms FAC stores ("75082", "009601588"). An auditee's ZIP on file changes between filing years; if it…

### `fac_get_audit` (~254 tokens)

Fetch one single audit by its FAC report_id (e.g. "2025-09-GSAFAC-0000422512"), including its summary_url — the official Federal Audit Clearinghouse dissemination summary page for that report — enriched with the full federal program detail: every Assistance Listing (CFDA) number the entity expended money under, the program name, dollars expended per program, whether it was audited as a major program, and the opinion type. Also returns the auditor firm and audit findings when FAC recorded any. Does NOT return named-individual contact details (auditee/auditor contact name, email, phone) — those are not carried here; see the report's summary_url on fac.gov for that. Answers "what did this specific audit cover and what did it conclude".

Input parameters:

- `award_limit` (number): Max federal award rows to include, 1-500 (default 200).
- `include_findings` (boolean): Attach audit findings for this report (default true).
- `report_id` (string, required): FAC report id as returned by fac_search_audits, e.g. "2025-09-GSAFAC-0000422512". Aliases: id, audit_id.

### `fac_audit_findings` (~244 tokens)

Audit findings recorded against single audits — the compliance exceptions, material weaknesses, significant deficiencies, questioned costs and repeat findings that auditors reported. Query by report_id, or by recipient name/UEI to sweep every audit that recipient filed. Answers "has this grant recipient had audit findings, and were they material or repeated".

Input parameters:

- `audit_year` (number): Restrict the resolved audits to one audit year (used with auditee_name or uei).
- `auditee_name` (string): Recipient name substring; the tool resolves matching audits first, then their findings. Aliases: query, q, name.
- `include_text` (boolean): Also attach the narrative finding text when FAC recorded any (default false — the text rows are long; a pre-2022 migrated audit often has none on file).
- `limit` (number): Max finding rows to return, 1-200 (default 50).
- `report_id` (string): FAC report id to pull findings for. Aliases: id, audit_id.
- `uei` (string): Recipient UEI; resolves that recipient's audits, then their findings. Alias: auditee_uei.

### `fac_federal_awards_by_program` (~345 tokens)

List the organizations that expended money under a given federal Assistance Listing / CFDA number (e.g. "93.224" community health centers, "84.010" Title I, "20.205" highway planning), ranked by dollars expended, with the recipient name, state, audit year and whether it was a major program. Answers "who spends the money in this federal grant program and how much does each one run".

Input parameters:

- `audit_year` (number): Restrict to one audit year, e.g. 2023.
- `cfda` (string): Assistance Listing / CFDA number. Accepts "93.224", "93-224", "93 224", "93224", or a bare agency prefix "93" for every program at that agency. Aliases: program_number, assistance_listing, program, c…
- `federal_agency_prefix` (string): Two-digit agency prefix on its own, e.g. "93" for HHS. Alias: prefix.
- `federal_award_extension` (string): Program extension on its own, e.g. "224". Alias: extension.
- `include_recipients` (boolean): Resolve each report_id to the recipient name and state (default true; one extra local query).
- `limit` (number): Rows to return, 1-200 (default 25).
- `major_only` (boolean): Keep only programs audited as major programs.
- `min_amount` (number): Only rows expending at least this many dollars.
- `state` (string): 2-letter recipient state code to narrow the ranking, e.g. "TX".

### `fac_recipient_audit_history` (~210 tokens)

Year-by-year single-audit history for one grant recipient, identified by UEI or by name. Returns each audit year with total federal awards expended, the report_id, the oversight agency and the FAC acceptance date, plus a growth read on the spend trend. Answers "how has this organization's federal funding moved over time and which years were audited".

Input parameters:

- `auditee_name` (string): Recipient name substring when the UEI is unknown, e.g. "johns hopkins". Aliases: query, q, name.
- `ein` (string): Employer Identification Number, an alternative exact identifier. Alias: auditee_ein.
- `state` (string): 2-letter state code, useful to disambiguate a common name.
- `uei` (string): SAM.gov Unique Entity Identifier, the precise way to pin one recipient. Alias: auditee_uei.
- `years` (number): Max audit years to return, 1-40 (default 15).

### `fac_findings_search` (~344 tokens)

Full-text search over audit finding NARRATIVES — the actual prose auditors wrote describing a compliance exception ("failed to submit the Federal Single Audit report within the timeframe prescribed", "total available cash was less than total advances from grantors"). This is not possible against the live FAC API, which exposes no cross-table join; it is what searching the underlying text directly unlocks. Optionally narrow by state, audit year, CFDA agency prefix, or material-weakness-only. Narrative text is only on file for more recent filings — audits migrated from the pre-2022 Census-run FAC often have none, and rows without text are simply not returned rather than shown blank. Answers "which audits mention X in their findings", e.g. "data security", "cash management", "timesheet".

Input parameters:

- `audit_year` (number): Restrict to one audit year.
- `federal_agency_prefix` (string): Restrict to findings on awards under this 2-digit agency prefix (e.g. "93" for HHS). Alias: cfda_prefix.
- `limit` (number): Rows to return, 1-100 (default 25).
- `material_weakness_only` (boolean): Only findings flagged as a material weakness.
- `offset` (number): Rows to skip, for paging.
- `query` (string, required): Search phrase, e.g. "data security" or "questioned costs travel". Uses PostgreSQL websearch syntax (quote a phrase, "-word" to exclude). Aliases: q, text.
- `state` (string): 2-letter auditee state code to narrow the search, e.g. "TX".

### `fac_cross_table_screen` (~378 tokens)

Screen single audits across state, federal program (CFDA), and finding type / material weakness in ONE call — a join FAC's own live API cannot express (its PostgREST has no foreign key between /general, /federal_awards and /findings). Answers compound diligence questions like "material weaknesses in Texas under CFDA 93.224" or "questioned-cost findings on highway funding (20.205) over $1M". Every filter is optional; pass at least one to keep the result meaningful. Returns one row per matching (audit, award, finding) combination, ranked by award dollar amount.

Input parameters:

- `audit_year` (number): Restrict to one audit year.
- `cfda` (string): Assistance Listing / CFDA number, e.g. "93.224" or a bare 2-digit agency prefix "93". Aliases: program_number, assistance_listing, program, cfda_number.
- `federal_agency_prefix` (string): Two-digit agency prefix on its own. Alias: prefix.
- `federal_award_extension` (string): Program extension on its own, e.g. "224". Alias: extension.
- `finding_type` (string): Substring match on FAC's finding type_requirement code (e.g. "A" internal control, "B" allowable costs — FAC packs several letters into one field, so this matches loosely).
- `limit` (number): Rows to return, 1-100 (default 25).
- `material_weakness_only` (boolean): Only findings flagged as a material weakness.
- `min_amount` (number): Only award rows expending at least this many dollars.
- `offset` (number): Rows to skip, for paging.
- `state` (string): 2-letter auditee state code, e.g. "TX".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-fac/pipeworx-mcp-fac#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### What is the Fac MCP server?

Fac is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fac. Federal Audit Clearinghouse (FAC) MCP, US single-audit data, served from a served from a… This page covers its npm package (@pipeworx/mcp-fac).

### Is the Fac MCP server safe to use?

Fac scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Fac MCP server expose?

Fac exposes 7 tools: fac_search_audits, fac_get_audit, fac_audit_findings, fac_federal_awards_by_program, fac_recipient_audit_history, and 2 more. Their descriptions and schemas cost roughly 2,364 tokens of context every time the server is loaded.

### Is the Fac MCP server still maintained?

Fac is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Fac MCP server under?

Fac declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Fac MCP server?

VerifyMCP ran 16 checks on Fac, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-fac
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-fac
- Repository: https://github.com/pipeworx-io/mcp-fac
- Website: https://pipeworx.io/packs/fac
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-fac/pipeworx-mcp-fac.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-fac/pipeworx-mcp-fac/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-fac/pipeworx-mcp-fac.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-fac/pipeworx-mcp-fac