MCP.Market

Ebsa MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/ebsa·v0.2.1

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

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Ebsa yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Ebsa tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Ebsa 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
212 ms
faster than 62% of 30,031 servers

Release history: 4 versions in the registry since 2026-10-18, latest 2026-11-01, typically one every 5 days.

Install Ebsa in Claude Code, Cursor or VS Code

claude mcp add --transport http ebsa https://gateway.pipeworx.io/ebsa/mcp
Add to Cursor

What the publisher says

From the Ebsa repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/ebsa — EBSA civil-penalty enforcement

Closed US Department of Labor Employee Benefits Security Administration civil-penalty enforcement actions since 2000 — deficient-filer, late-filer and non-filer penalty assessments against ERISA benefit-plan sponsors for their Form 5500 filings. form5500 already covers the filings themselves (what sponsors reported); this is EBSA's own enforcement record against sponsors who filed deficiently, late, or not at all — distinct from dol-whd (Wage & Hour back-wage/overtime cases) and osha (safety citations), both of which already live on this same DOL API gateway.

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

This is a civil-penalty / filing-compliance enforcement record, not a fiduciary-breach litigation docket — EBSA does not publish a bulk dataset of individual fiduciary-breach case outcomes. This is the enforcement dataset that actually exists in structured, bulk-queryable form.

Tools

Auth

Platform key (PLATFORMDOLKEY, already set on the gateway for dol-whd and osha) with BYO override via apiKey. A free key from covers every DOL dataset on this gateway. A live sibling call (dolwhd whd_search) confirmed the platform key is valid right now (2026-10-17) — no new key needed.

Live proxy, same gateway as dol-whd and osha

This pack calls apiprod.dol.gov/v4 — the identical gateway, auth shape and query grammar dol-whd already documents in full in its own README and src/index.ts header. Every trap there applies verbatim here and is not re-derived:

or no key at all; the row endpoint (/v4/get/EBSA/ocats/json) rejects a header and needs the key as a query parameter.

  • The catalog endpoint (/v4/datasets/10361) takes an X-API-KEY header

{"data":[]}.

  • A zero-match query answers HTTP 204 with an empty body, not a 200 with

Retry-After — this pack backs off twice, then returns { found: false, reason: "upstreamratelimited" }.

  • The upstream throttles by source IP, not by key, and sends no

be lowercase; a wrong dataset name and a malformed filter both answer a generic HTTP 500.

  • filter_object keywords (field, operator, value, and, or) must

Fields (from the live dataset, not guessed)

Verified live 2026-10-17 against the dataset's own 10-row preview (no key needed to read it): casetype, ein, pn (plan number), planyear, planname, planadmin, planadminstate, planadminzipcode, finalclosereason, finalclosedate, penaltyamount, load_dt.

penaltyamount is a DOL-assigned STRING BUCKET, not an exact dollar figure — observed live values include "over $100,000", "$50,001 - $100,000", "$0-$10,000". This pack passes it through verbatim as penaltyamount_bucket and never parses it into a number.

casetype values observed live: "Deficient Filer" (the only value in the 10-row preview sample); the dataset's own description also names "late filers" and "non-filers" among the enforcement focus. casetype is matched with like (substring), not an exact enum, since the precise casing of every value was not exhaustively observed.

No individual PII

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Ebsa: common questions

Is Ebsa MCP server safe?
Mostly: it is graded B (77/100). Read the Ebsa safety report
How do I install Ebsa?
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 Ebsa need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Ebsa maintained?
The last commit was 10 days ago (2026-10-25). The latest release is v0.2.1.
Is Ebsa up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Ebsa 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 212 ms (faster than 62% of 30,031 servers). Full comparison.

More from pipeworx-io →