
Oig Corporate Integrity MCP server
online · 100% uptimeHHS-OIG Corporate Integrity Agreements — does this healthcare company have a CIA, since when, what…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Oig Corporate Integrity yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Oig Corporate Integrity tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Oig Corporate Integrity compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 179 ms
- faster than 67% of 30,031 servers
Release history: 7 versions in the registry since 2026-10-08, latest 2026-11-03, typically one every 4 days.
Install Oig Corporate Integrity in Claude Code, Cursor or VS Code
claude mcp add --transport http oig-corporate-integrity https://gateway.pipeworx.io/oig-corporate-integrity/mcp
What the publisher says
From the Oig Corporate Integrity repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/oig-corporate-integrity
HHS-OIG Corporate Integrity Agreements — does this healthcare company or individual have a Corporate Integrity Agreement (CIA), since when, what obligations does it impose, and what is its current status? A CIA is a different condition from an exclusion (see the leie and ny-omig-exclusions packs): an entity under a CIA is still participating in Medicare/Medicaid, under binding compliance obligations OIG negotiated instead of seeking exclusion.
Part of Pipeworx — an MCP gateway connecting AI agents to 1764+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
HHS-OIG CIA roster. An exact name match is the strongest signal; a normalized-name or token match is returned as a labelled candidate, since CIA entity names are frequently compound (a company plus named co-signers, e.g. "SNAP Diagnostics, LLC and Gil Raviv"). For the best match, fetches the entity's own detail page live to return the effective date, term/duration, settlement amount and the agreement PDF URL — none of that is baked, so it is never stale. Returns found: false with the list's as-of date and total agreement count when no match exists.
- oigciacheck(name, limit?) — checks an entity against the current
matching as oigciacheck) or takes a documenturl directly, fetches the agreement PDF live** from oig.hhs.gov, extracts its text, and reports which of six obligation categories (Board Resolution, Independent Review Organization/IRO reviews, Compliance Officer/Committee, Annual or Implementation reporting, a disclosure program, excluded-persons screening) actually appear in the text, each with a short excerpt. Not every CIA includes every category — a sole-individual CIA typically has no Board Resolution clause — and some older, fully closed agreements have no PDF posted at all, reported as found: false, not an error.
- oigciaobligations(name?, document_url?) — resolves the entity (same
status (Effective / Suspended / Closed / Refused). Fast (no live fetch), but carries only what the list card shows — call oigciacheck on a specific entity for effective date, term and the agreement document.
- oigcialist(status?, limit?, offset?) — browses the baked CIA list by
Auth
Keyless.
Data sources
— the paginated, filterable CIA roster (339 agreements as captured, 20 per page). No JSON/REST endpoint and no bulk CSV/Excel export exist.
(/compliance/corporate-integrity-agreements/browse-cias//) — effective date, term, settlement amount, category/tags, and the agreement PDF's URL. Fetched live, per call, never baked.
- Each agreement's own detail page
text PDFs, extracted with shared/src/pdf-text.ts.
- The agreement PDF itself (oig.hhs.gov/documents/cias//.pdf) —
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 all 17 pages of the browse list and bakes only the entity name, detail-page path, the status badge/date shown on the list card, location and report type — into src/oig-cia-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 south-dakota-code / ny-omig-exclusions / usgs-mineral-commodities). A missing or malformed injection throws loudly rather than answering "no CIA found" — see src/index.test.ts.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Oig Corporate Integrity: common questions
- Is Oig Corporate Integrity MCP server safe?
- Mostly: it is graded B (77/100). Read the Oig Corporate Integrity safety report
- How do I install Oig Corporate Integrity?
- It runs remotely at gateway.pipeworx.io. 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 Oig Corporate Integrity need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Oig Corporate Integrity maintained?
- The last commit was 25 days ago (2026-10-10). The latest release is v0.2.1.
- Is Oig Corporate Integrity up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Oig Corporate Integrity compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 179 ms (faster than 67% of 30,031 servers). Full comparison.