Ebsa
NPM · @PIPEWORX/MCP-EBSA · 2 COMPONENTS
EBSA enforcement — civil-penalty actions on ERISA benefit-plan filings
Available components
Last scanned (16 hours ago)
Scores higher than 72% of npm servers
Category Finance and Payments
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-ebsa). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +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.
- 2 Nov 26 +12
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 1 Nov 26 −10
- Known CVEs: pass → unverified ▼ security
- 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. security
- Dependency health: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 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-ebsa@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-ebsa |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ebsa/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617581911 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9c3343d26aa527b9c71d776a626571862e9691b7f3f2f1d2d0a395992376be3fcb7ddf4f40326b8f7003f573b8bba7dcb3174f8aae2ec12fe51bdb30e |
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 →
ebsa_coverage ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key. |
No output schema declared.
No examples provided.
ebsa_recent ~166
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".
| Name | Type | Req | Description |
|---|---|---|---|
| _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"). |
No output schema declared.
No examples provided.
ebsa_search ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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"). |
No output schema declared.
No examples provided.
ebsa_sponsor ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Plan sponsor / administrator name, matched against the plan administrator and the plan name. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-ebsa
claude mcp add pipeworx-io-ebsa -- npx -y @pipeworx/mcp-ebsa
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.