Oig Self Disclosure Settlements MCP server

@pipeworx/oig-self-disclosure-settlements

HHS-OIG Self-Disclosure Protocol settlements — has this provider, grantee or contractor voluntarily self-disclosed conduct to OIG and settled a Civil Monetary Penalties Law case over it? Complements oig-corporate-integrity: a Corporate Integrity Agreement is an ongoing compliance obligation, while most Self-Disclosure Protocol settlements are a one-time payment resolving a self-reported issue, often with no CIA attached at all.

Part of Pipeworx — an MCP gateway connecting AI agents to 1837+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

self-disclosure cases, newest first. Returns totals first (matching count, totals by program, and the approximate dollar sum of the returned page) and then the settlements themselves: provider, date, headline amount, allegation and a detail-page link. program filters to "provider" (Provider Self-Disclosure Protocol, the large majority), "grant" (Grant and Contractor Self-Disclosure Program) or "all" (default).

• oigsdprecent(program?, limit?, offset?) — the most recent settled

grantee or contractor settled a self-disclosure case? Matches a name against the baked settlement list (exact title, exact/substring provider name, or token match, each labelled); for the best match, fetches the settlement's own detail page live to return the exact settlement amount, the full entity description and the complete allegation narrative — the headline figure baked into the list is frequently rounded (e.g. a title reading "$442,000" against a detail page reading "$442,713.81"), so this is the call to make when the exact figure matters. Returns found: false with the list's as-of date and total settlement count when no match exists.

• oigsdpcheck(name, program?, limit?) — has a specific provider,

Auth

Keyless.

Data sources

Protocol settlements. Covers both the Provider Self-Disclosure Protocol (~1,057 settlements as captured) and the Grant and Contractor Self-Disclosure Program (~17 as captured). No JSON/REST endpoint and no bulk CSV/Excel export exist for this slice of OIG's enforcement record.

• HHS Office of Inspector General, Enforcement Actions — Self-Disclosure

full legal name and location, the exact settlement amount, and the complete allegation narrative. Fetched live, per call, never baked.

• Each settlement's own enforcement-action detail page — the provider's

Why only the LIST is baked

Root CLAUDE.md's standing rule for this shape: a baked table never sits in gateway module scope. scripts/bake-index.mjs crawls both programs' full page ranges and bakes only the headline (which carries the provider name, an approximate dollar figure, and the allegation in one sentence), the detail-page path, the publish date and the program — into src/sdp-index-data.ts, registered in workers/gateway/src/pack-baked-indexes.json, uploaded to KV at deploy, and injected as args._bakedIndex (fleet #2754 pattern, same as oig-corporate-integrity). A missing or malformed injection throws loudly rather than answering "no settlement found" — see the ensureIndex guard in src/index.ts.

The exact settlement amount, the provider's full legal name/location, and the full allegation narrative are deliberately not baked — they are fetched live from that one settlement's own detail page on every oigsdpcheck call. Most callers never ask about most of the ~1,074 rows, so pre-crawling every detail page would be wasted work; fetching live also means a newly-posted settlement's narrative is visible as soon as the list is next re-baked, without a second crawl pass.

Shortened. The full README is on GitHub.