@pipeworx/mcp-dol-m1 0.0.0-stage → 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +169 -2
- package/bin/cli.js +17 -0
- package/package.json +30 -4
- package/server.json +18 -0
- package/src/index.ts +1307 -0
- package/src/server.ts +48 -0
- package/tsconfig.json +18 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Mojibake Inc.
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.md
CHANGED
|
@@ -1,3 +1,170 @@
|
|
|
1
|
-
#
|
|
1
|
+
# @pipeworx/dol-m1 — Form M-1 (MEWA/AHP) filings
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
U.S. Department of Labor Form M-1 filings — the federal report filed by
|
|
4
|
+
multiple employer welfare arrangements (MEWAs) and association health plans
|
|
5
|
+
(AHPs) that pool health coverage across unrelated employers. `form5500`
|
|
6
|
+
already covers annual plan/pension financial returns, and `ebsa` covers
|
|
7
|
+
EBSA's own civil-penalty enforcement record against deficient Form 5500
|
|
8
|
+
filers — this is a third, unrelated filer population and form.
|
|
9
|
+
|
|
10
|
+
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1843+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
|
|
11
|
+
|
|
12
|
+
## Tools
|
|
13
|
+
|
|
14
|
+
| Tool | Answers |
|
|
15
|
+
|---|---|
|
|
16
|
+
| `dol_m1_search` | Search filings by plan year, MEWA/sponsor name, EIN, headquarters state, state(s) where coverage is offered, filing type, stop-loss, fully-insured |
|
|
17
|
+
| `dol_m1_filer` | Full filing history (every plan year filed) for one named MEWA/sponsor or EIN |
|
|
18
|
+
|
|
19
|
+
## Auth
|
|
20
|
+
|
|
21
|
+
Keyless. No login, no API key, no approval step.
|
|
22
|
+
|
|
23
|
+
## Data sources
|
|
24
|
+
|
|
25
|
+
- U.S. Department of Labor, Employee Benefits Security Administration — Form
|
|
26
|
+
M-1 Filings Database. 17,313 filings live as of 2026-10-18, plan years
|
|
27
|
+
2003-2025.
|
|
28
|
+
|
|
29
|
+
## Gotchas
|
|
30
|
+
|
|
31
|
+
- **Reverse-engineered, not documented.** This is a public search tool, not a
|
|
32
|
+
published REST API — the endpoint shape came from the search page's own
|
|
33
|
+
bundled JavaScript (`m1search.build_url`), not from any API docs. It is
|
|
34
|
+
still a plain, publicly reachable `GET` with no auth; nothing here needs a
|
|
35
|
+
browser or a session.
|
|
36
|
+
- **The dropdown filters do not accept an empty string the way a free-text
|
|
37
|
+
field does.** Plan year and filing type default to `"ALL"`, and the
|
|
38
|
+
stop-loss/fully-insured flags default to `"0"` ("Any") in the real form.
|
|
39
|
+
Sending `""` for any of those four throws an unhandled server exception —
|
|
40
|
+
the endpoint answers **HTTP 500 with a full HTML error page**, not a
|
|
41
|
+
structured error. This pack always sends the correct default.
|
|
42
|
+
- **Headquarters state and coverage state are different facets, not
|
|
43
|
+
aliases.** `hq_state` filters where the MEWA is based; `coverage_state`
|
|
44
|
+
filters where it offers coverage — a MEWA headquartered in New Jersey can
|
|
45
|
+
show up filtered by `coverage_state: "NY"` with `hq_state: "NJ"` on its own
|
|
46
|
+
row. Verified live.
|
|
47
|
+
- **`limit` has an undocumented cap of 100, and it does not clamp or error
|
|
48
|
+
past that — it silently resets to a 25-row default.** Measured live:
|
|
49
|
+
`limit=100` returns 100 rows, `limit=101` returns 25. This pack clamps its
|
|
50
|
+
own `limit` argument to 1-100 before calling, so a caller's `limit: 500`
|
|
51
|
+
cannot trigger the silent fallback.
|
|
52
|
+
- **A zero-match query is a clean `HTTP 200` with `{"total":0,"rows":[]}`** —
|
|
53
|
+
not an error. This pack turns that into `{ found: false, reason:
|
|
54
|
+
"no_matching_filings", filters_applied: {...} }` rather than passing
|
|
55
|
+
through a bare `[]`.
|
|
56
|
+
- **The `FilingType` field on each returned row does not reliably reflect
|
|
57
|
+
the `filing_type` request filter** — every row observed across every
|
|
58
|
+
filing-type query (Amended, Extension, Regular Filing, Registration) came
|
|
59
|
+
back `FilingType: 0`. The request-side filter itself works (verified live:
|
|
60
|
+
filtering narrows the total count correctly per type); only the echoed
|
|
61
|
+
field is unreliable, so it is left out of the shaped output.
|
|
62
|
+
- **The administrator/sponsor name can be an individual**, not a business.
|
|
63
|
+
For small MEWAs the Form M-1 administrator of record is sometimes a
|
|
64
|
+
natural person's own name — this is the DOL's own mandatory public-filing
|
|
65
|
+
field, passed through exactly as the federal filing discloses it, the same
|
|
66
|
+
way `form5500` and `ebsa` already pass through their own sponsor fields.
|
|
67
|
+
|
|
68
|
+
## Quick Start
|
|
69
|
+
|
|
70
|
+
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
|
|
71
|
+
|
|
72
|
+
```json
|
|
73
|
+
{
|
|
74
|
+
"mcpServers": {
|
|
75
|
+
"dol-m1": {
|
|
76
|
+
"url": "https://gateway.pipeworx.io/dol-m1/mcp"
|
|
77
|
+
}
|
|
78
|
+
}
|
|
79
|
+
}
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
### What this endpoint actually serves
|
|
83
|
+
|
|
84
|
+
`tools/list` at `https://gateway.pipeworx.io/dol-m1/mcp` returns the tools in the table
|
|
85
|
+
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
|
|
86
|
+
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
|
|
87
|
+
gateway-wide set. So the tool count you see is larger than this table: a
|
|
88
|
+
single-pack endpoint currently lists roughly 30 shared tools alongside the
|
|
89
|
+
pack's own. The connection's `initialize` response states its exact scope, and
|
|
90
|
+
is the authoritative answer for a given day.
|
|
91
|
+
|
|
92
|
+
This is deliberate, not multiplexing by accident. The meta-tools are what let a
|
|
93
|
+
scoped connection answer a question this pack does not cover — via
|
|
94
|
+
`ask_pipeworx`, which routes across the whole catalog — without you adding a
|
|
95
|
+
second MCP server. There is currently no way to mount a pack endpoint without
|
|
96
|
+
them; if the extra schemas cost you more context than the routing is worth,
|
|
97
|
+
connect to the full gateway once rather than to several pack endpoints.
|
|
98
|
+
|
|
99
|
+
Or connect to the full Pipeworx gateway to get every pack's tools listed
|
|
100
|
+
directly, instead of just this one's:
|
|
101
|
+
|
|
102
|
+
```json
|
|
103
|
+
{
|
|
104
|
+
"mcpServers": {
|
|
105
|
+
"pipeworx": {
|
|
106
|
+
"url": "https://gateway.pipeworx.io/mcp"
|
|
107
|
+
}
|
|
108
|
+
}
|
|
109
|
+
}
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
Both URLs reach the same gateway and the same 1843+ data sources. The
|
|
113
|
+
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
|
|
114
|
+
reaches all of them from either one.
|
|
115
|
+
|
|
116
|
+
## No MCP client? Call it over HTTP
|
|
117
|
+
|
|
118
|
+
```bash
|
|
119
|
+
curl -X POST https://gateway.pipeworx.io/v1/tools/dol_m1_search \
|
|
120
|
+
-H 'Content-Type: application/json' \
|
|
121
|
+
-d '{"hq_state":"TX","plan_year":2024,"limit":5}'
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/dol_m1_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
|
|
125
|
+
|
|
126
|
+
## Standalone (no gateway account)
|
|
127
|
+
|
|
128
|
+
This package also runs as a local stdio MCP server — no Pipeworx account, no
|
|
129
|
+
gateway round-trip:
|
|
130
|
+
|
|
131
|
+
```json
|
|
132
|
+
{
|
|
133
|
+
"mcpServers": {
|
|
134
|
+
"dol-m1": {
|
|
135
|
+
"command": "npx",
|
|
136
|
+
"args": ["-y", "@pipeworx/mcp-dol-m1"]
|
|
137
|
+
}
|
|
138
|
+
}
|
|
139
|
+
}
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
Or run it directly to confirm it starts:
|
|
143
|
+
|
|
144
|
+
```bash
|
|
145
|
+
npx -y @pipeworx/mcp-dol-m1
|
|
146
|
+
```
|
|
147
|
+
|
|
148
|
+
It speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`
|
|
149
|
+
for **only** this pack's tools — none of the shared meta-tools the gateway
|
|
150
|
+
connection above adds. Same source, same tools, no ask_pipeworx routing.
|
|
151
|
+
|
|
152
|
+
## Using with ask_pipeworx
|
|
153
|
+
|
|
154
|
+
Instead of calling tools directly, you can ask questions in plain English —
|
|
155
|
+
this works on the pack endpoint above as well as on the full gateway:
|
|
156
|
+
|
|
157
|
+
```
|
|
158
|
+
ask_pipeworx({ question: "your question about Dol M1 data" })
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
The gateway picks the right tool and fills the arguments automatically.
|
|
162
|
+
|
|
163
|
+
## More
|
|
164
|
+
|
|
165
|
+
- [Docs and guides](https://pipeworx.io/docs)
|
|
166
|
+
- [pipeworx.io](https://pipeworx.io)
|
|
167
|
+
|
|
168
|
+
## License
|
|
169
|
+
|
|
170
|
+
MIT
|
package/bin/cli.js
ADDED
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
//
|
|
3
|
+
// Entry point for `npx @pipeworx/mcp-<slug>`.
|
|
4
|
+
//
|
|
5
|
+
// Packs ship as raw TypeScript (no build step — see publish-pack.sh for why:
|
|
6
|
+
// tsx sidesteps every extensionless-import / bare-JSON-import edge case a
|
|
7
|
+
// per-pack tsc build would have to solve one pack at a time). This file
|
|
8
|
+
// registers tsx's ESM loader programmatically, then hands off to src/server.ts,
|
|
9
|
+
// which wraps the pack's {tools, callTool} export in a stdio MCP server.
|
|
10
|
+
//
|
|
11
|
+
// Copied verbatim into every published pack repo by scripts/publish-pack.sh —
|
|
12
|
+
// edit this file, not a per-pack copy.
|
|
13
|
+
import { register } from 'tsx/esm/api';
|
|
14
|
+
|
|
15
|
+
register();
|
|
16
|
+
|
|
17
|
+
await import('../src/server.ts');
|
package/package.json
CHANGED
|
@@ -1,6 +1,32 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pipeworx/mcp-dol-m1",
|
|
3
|
-
"version": "0.
|
|
4
|
-
"
|
|
5
|
-
"
|
|
6
|
-
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"description": "DOL Form M-1 — multiple employer welfare arrangement (MEWA) filings",
|
|
5
|
+
"type": "module",
|
|
6
|
+
"main": "src/index.ts",
|
|
7
|
+
"types": "src/index.ts",
|
|
8
|
+
"bin": {
|
|
9
|
+
"mcp-dol-m1": "bin/cli.js"
|
|
10
|
+
},
|
|
11
|
+
"keywords": ["mcp", "mcp-server", "model-context-protocol", "pipeworx", "dol-m1"],
|
|
12
|
+
"license": "MIT",
|
|
13
|
+
"repository": {
|
|
14
|
+
"type": "git",
|
|
15
|
+
"url": "git+https://github.com/pipeworx-io/mcp-dol-m1.git"
|
|
16
|
+
},
|
|
17
|
+
"scripts": {
|
|
18
|
+
"typecheck": "tsc --noEmit"
|
|
19
|
+
},
|
|
20
|
+
"dependencies": {
|
|
21
|
+
"@modelcontextprotocol/sdk": "^1.30.0",
|
|
22
|
+
"tsx": "^4.19.0"
|
|
23
|
+
},
|
|
24
|
+
"devDependencies": {
|
|
25
|
+
"typescript": "^5.9.3",
|
|
26
|
+
"@cloudflare/workers-types": "^4.20260405.1"
|
|
27
|
+
},
|
|
28
|
+
"pipeworx": {
|
|
29
|
+
"sourceHash": "v1-de11f7b15675bc9b847fbedd68c3d8c2a51fbb9344f6a6a67adcb23573d56dde",
|
|
30
|
+
"sourceCommit": "351c40908821cfecc9bb2f5849d87bbfdbb26d75"
|
|
31
|
+
}
|
|
32
|
+
}
|
package/server.json
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
{
|
|
2
|
+
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
|
|
3
|
+
"name": "io.github.pipeworx-io/dol-m1",
|
|
4
|
+
"title": "Dol M1",
|
|
5
|
+
"description": "DOL Form M-1 — multiple employer welfare arrangement (MEWA) filings",
|
|
6
|
+
"version": "0.1.0",
|
|
7
|
+
"websiteUrl": "https://pipeworx.io/packs/dol-m1",
|
|
8
|
+
"repository": {
|
|
9
|
+
"url": "https://github.com/pipeworx-io/mcp-dol-m1",
|
|
10
|
+
"source": "github"
|
|
11
|
+
},
|
|
12
|
+
"remotes": [
|
|
13
|
+
{
|
|
14
|
+
"type": "streamable-http",
|
|
15
|
+
"url": "https://gateway.pipeworx.io/dol-m1/mcp"
|
|
16
|
+
}
|
|
17
|
+
]
|
|
18
|
+
}
|