MCP.Market

Dol M1 MCP server

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

DOL Form M-1 — multiple employer welfare arrangement (MEWA) filings

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

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Dol M1 yet.

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

Dol M1 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 Dol M1 compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 39% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
434 ms
faster than 34% of 30,031 servers

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

Install Dol M1 in Claude Code, Cursor or VS Code

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

What the publisher says

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

@pipeworx/dol-m1 — Form M-1 (MEWA/AHP) filings

U.S. Department of Labor Form M-1 filings — the federal report filed by multiple employer welfare arrangements (MEWAs) and association health plans (AHPs) that pool health coverage across unrelated employers. form5500 already covers annual plan/pension financial returns, and ebsa covers EBSA's own civil-penalty enforcement record against deficient Form 5500 filers — this is a third, unrelated filer population and form.

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.

Tools

Auth

Keyless. No login, no API key, no approval step.

Data sources

M-1 Filings Database. 17,313 filings live as of 2026-10-18, plan years 2003-2025.

  • U.S. Department of Labor, Employee Benefits Security Administration — Form

Gotchas

published REST API — the endpoint shape came from the search page's own bundled JavaScript (m1search.build_url), not from any API docs. It is still a plain, publicly reachable GET with no auth; nothing here needs a browser or a session.

  • Reverse-engineered, not documented. This is a public search tool, not a

field does. Plan year and filing type default to "ALL", and the stop-loss/fully-insured flags default to "0" ("Any") in the real form. Sending "" for any of those four throws an unhandled server exception — the endpoint answers HTTP 500 with a full HTML error page**, not a structured error. This pack always sends the correct default.

  • **The dropdown filters do not accept an empty string the way a free-text

aliases. hqstate filters where the MEWA is based; coveragestate filters where it offers coverage — a MEWA headquartered in New Jersey can show up filtered by coveragestate: "NY" with hq_state: "NJ" on its own row. Verified live.

  • **Headquarters state and coverage state are different facets, not

past that — it silently resets to a 25-row default.** Measured live: limit=100 returns 100 rows, limit=101 returns 25. This pack clamps its own limit argument to 1-100 before calling, so a caller's limit: 500 cannot trigger the silent fallback.

  • **limit has an undocumented cap of 100, and it does not clamp or error

not an error. This pack turns that into { found: false, reason: "nomatchingfilings", filters_applied: {...} } rather than passing through a bare [].

  • A zero-match query is a clean HTTP 200 with {"total":0,"rows":[]} —

the filingtype request filter — every row observed across every filing-type query (Amended, Extension, Regular Filing, Registration) came back FilingType: 0. The request-side filter itself works (verified live: filtering narrows the total count correctly per type); only the echoed field is unreliable, so it is left out of the shaped output.

  • **The FilingType field on each returned row does not reliably reflect

For small MEWAs the Form M-1 administrator of record is sometimes a natural person's own name — this is the DOL's own mandatory public-filing field, passed through exactly as the federal filing discloses it, the same way form5500 and ebsa already pass through their own sponsor fields.

  • The administrator/sponsor name can be an individual, not a business.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "dol-m1": {
      "url": "https://gateway.pipeworx.io/dol-m1/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.

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

Dol M1: common questions

Is Dol M1 MCP server safe?
Mostly: it is graded B (73/100). Read the Dol M1 safety report
How do I install Dol M1?
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 Dol M1 need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Dol M1 maintained?
The last commit was 10 days ago (2026-10-25). The latest release is v0.2.1.
Is Dol M1 up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Dol M1 compare with other MCP servers?
safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 434 ms (faster than 34% of 30,031 servers). Full comparison.

More from pipeworx-io →