Oig Corporate Integrity
NPM · @PIPEWORX/MCP-OIG-CORPORATE-INTEGRITY · 2 COMPONENTS
HHS-OIG Corporate Integrity Agreements — does this healthcare company have a CIA, since when, what…
Available components
Last scanned (3 hours ago)
Scores higher than 72% of npm servers
Category Health and Science
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-oig-corporate-integrity). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 804 tokens (~268/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-oig-corporate-integrity@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-oig-corporate-integrity |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-oig-corporate-integrity/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679660474 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:82bbd21236567bd2b784385152af21914fc248f8668f99d1d4f4ff946a2dad3bf4bef8a00de800f38494c930f80713b3a9648a3011c8ac242e0bf5ec0 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
oig_cia_check ~321
Does this healthcare company or individual have an HHS-OIG Corporate Integrity Agreement (CIA)? Checks a name against the current HHS-OIG CIA roster — companies and individuals OIG agreed not to exclude from Medicare/Medicaid in exchange for binding compliance obligations, as part of a False Claims Act or other settlement. Different from an EXCLUSION (see the leie / ny-omig-exclusions packs): a CIA entity is still participating, under obligations. An exact name match is the strongest signal; a normalized-name or partial/token match is returned as a labelled CANDIDATE, since CIA entity names are often compound (a company plus named co-signers) — e.g. searching "SNAP Diagnostics" finds "SNAP Diagnostics, LLC and Gil Raviv" as a candidate. Returns, for the best match: status (Effective/Suspended/Closed/Refused), effective date, term/duration, settlement amount, and the agreement PDF URL (fetched live from the entity's own detail page — not stale). Returns found:false with the list's as-of date and total agreement count when no match exists. Sourced from HHS-OIG, keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum candidates to return (default 5, max 20). Only the top/best candidate is enriched with live detail-page data. |
| name | string | yes | Company or individual name to check, e.g. "SNAP Diagnostics" or "Alliance Parent, Inc.". Any word order; partial names are matched as candidates. |
No output schema declared.
No examples provided.
oig_cia_list ~167
Browse the current HHS-OIG Corporate Integrity Agreement roster by status — e.g. list every currently Suspended or Refused-by-Entity agreement. Reads the baked CIA list (refreshed periodically; data_as_of says when) rather than live detail pages, so it is fast but does not include effective dates/terms/documents — call oig_cia_check for those on a specific entity. Sourced from HHS-OIG, keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max rows to return (default 25, max 100). |
| offset | number | – | Rows to skip, for paging (default 0). |
| status | string | – | Filter to one status: Effective, Suspended, Closed, or Refused. Omit to list all. |
No output schema declared.
No examples provided.
oig_cia_obligations ~254
What obligations does this entity's Corporate Integrity Agreement actually impose — Board Resolution, Independent Review Organization (IRO) reviews, Compliance Officer/Committee, Annual/Implementation reporting, a disclosure program, excluded-persons screening? Resolves the entity (same matching as oig_cia_check) or takes a direct document_url (from oig_cia_check's agreement_url field), fetches the agreement PDF LIVE from oig.hhs.gov, extracts its text, and reports which of those obligation categories appear in the text with a short excerpt for each. Not every CIA includes every category — a sole-individual CIA typically has no Board Resolution clause, and some older closed agreements have no PDF posted at all (reported as found:false, not an error). Sourced from HHS-OIG, keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| document_url | string | – | A specific agreement PDF URL under oig.hhs.gov/documents/cias/..., e.g. from a prior oig_cia_check call's agreement_url field. Overrides name-based lookup when given. |
| name | string | – | Company or individual name to look up (resolved the same way as oig_cia_check). Omit if passing document_url directly. |
No output schema declared.
No examples provided.
How do I install the Oig Corporate Integrity MCP server?
Oig Corporate Integrity runs locally as an npm package, launched with npx -y @pipeworx/mcp-oig-corporate-integrity. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-oig-corporate-integrity
claude mcp add pipeworx-io-oig-corporate-integrity -- npx -y @pipeworx/mcp-oig-corporate-integrity
What is the Oig Corporate Integrity MCP server?
Oig Corporate Integrity is an MCP server listed in the public MCP registry as io.github.pipeworx-io/oig-corporate-integrity. HHS-OIG Corporate Integrity Agreements, does this healthcare company have a CIA, since when, what… This page covers its npm package (@pipeworx/mcp-oig-corporate-integrity).
Is the Oig Corporate Integrity MCP server safe to use?
Oig Corporate Integrity 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 Oig Corporate Integrity MCP server expose?
Oig Corporate Integrity exposes 3 tools: oig_cia_check, oig_cia_obligations, oig_cia_list. Their descriptions and schemas cost roughly 742 tokens of context every time the server is loaded.
Is the Oig Corporate Integrity MCP server still maintained?
Oig Corporate Integrity 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 Oig Corporate Integrity MCP server under?
Oig Corporate Integrity declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.