# Ebsa (npm · @pipeworx/mcp-ebsa)

EBSA enforcement — civil-penalty actions on ERISA benefit-plan filings

- Trust score: 82/100 (high trust)
- 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-ebsa/ebsa-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ebsa/ebsa-mcp)
- npm · `@pipeworx/mcp-ebsa`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ebsa/pipeworx-mcp-ebsa.md), [page](https://verifymcp.io/servers/pipeworx-io-ebsa/pipeworx-mcp-ebsa)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ebsa`
- 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-ebsa).
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 760 tokens (~190/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Ebsa MCP server?

Ebsa runs locally as an npm package, launched with npx -y @pipeworx/mcp-ebsa. 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-ebsa -- npx -y @pipeworx/mcp-ebsa
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 82, +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-02 (score 81, +12)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-01 (score 69, −10)

- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Dependency health: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 79)

First indexed and scored.

## MCP tools (4)

### `ebsa_search` (~301 tokens)

Search closed EBSA (Employee Benefits Security Administration) civil-penalty enforcement cases since 2000 — deficient-filer, late-filer and non-filer penalty assessments against ERISA benefit-plan sponsors for their Form 5500 filings. Filter by plan sponsor/administrator name, case type, state, or plan year. Returns the plan, sponsor, case type, close reason/date, and the penalty amount (a DOL-assigned dollar-range bucket, e.g. "over $100,000"). Complements the `form5500` pack, which covers the filings themselves rather than enforcement against them.

Input parameters:

- `_apiKey` (string): Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key.
- `case_type` (string): Case type, e.g. "Deficient Filer", "Late Filer", "Non Filer". Matched as a substring.
- `limit` (number): Cases to return, 1-100 (default 20).
- `plan_year` (string|number): Plan year of the filing that triggered the case, e.g. 2022.
- `sponsor` (string): Plan sponsor / administrator name, matched as a substring against both the plan administrator and the plan name.
- `state` (string): Two-letter or full state name of the plan administrator as DOL records it (e.g. "Texas").

### `ebsa_sponsor` (~151 tokens)

Full EBSA civil-penalty enforcement history for one named plan sponsor/administrator, with every closed case and a count by case type. Matches the sponsor against both the plan administrator name and the plan name and reports which one hit. Use to answer whether an employer's benefit plans have a history of filing-compliance penalties.

Input parameters:

- `_apiKey` (string): Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key.
- `limit` (number): Cases to examine, 1-100 (default 100).
- `sponsor` (string, required): Plan sponsor / administrator name, matched against the plan administrator and the plan name.

### `ebsa_recent` (~166 tokens)

The most recent closed EBSA civil-penalty enforcement actions, newest first, optionally restricted to one case type or state. Returns plan, sponsor, case type, close date/reason and penalty bucket for each. Use for "what EBSA enforcement actions closed recently".

Input parameters:

- `_apiKey` (string): Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key.
- `case_type` (string): Restrict to one case type, e.g. "Deficient Filer".
- `limit` (number): Cases to return, 1-100 (default 20).
- `state` (string): Restrict to one plan-administrator state as DOL records it (e.g. "California").

### `ebsa_coverage` (~90 tokens)

Report what the EBSA OCATS enforcement dataset currently covers: its publication date, update frequency and the close-date range of a sample query. Use to check how current the enforcement data is before relying on an absence of cases.

Input parameters:

- `_apiKey` (string): Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 69
- 2026-10-31: 79
- 2026-10-30: 79

## Common questions

### What is the Ebsa MCP server?

Ebsa is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ebsa. EBSA enforcement, civil-penalty actions on ERISA benefit-plan filings. This page covers its npm package (@pipeworx/mcp-ebsa).

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

Ebsa 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 Ebsa MCP server expose?

Ebsa exposes 4 tools: ebsa_search, ebsa_sponsor, ebsa_recent, ebsa_coverage. Their descriptions and schemas cost roughly 708 tokens of context every time the server is loaded.

### Is the Ebsa MCP server still maintained?

Ebsa 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 Ebsa MCP server under?

Ebsa 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 Ebsa MCP server?

VerifyMCP ran 16 checks on Ebsa, 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-ebsa
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-ebsa
- Repository: https://github.com/pipeworx-io/mcp-ebsa
- Website: https://pipeworx.io/packs/ebsa
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-ebsa/pipeworx-mcp-ebsa.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-ebsa/pipeworx-mcp-ebsa/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-ebsa/pipeworx-mcp-ebsa.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-ebsa/pipeworx-mcp-ebsa