Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Dol M1 is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
DOL Form M-1 — multiple employer welfare arrangement (MEWA) filings
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http dol-m1-mcp https://gateway.pipeworx.io/dol-m1/mcp
# 2 — ask your agent for something these tools do
# ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded and 3 more
Dol M1 costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PIAll 1869 servers
pipeworx-io1869 servers
29 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http dol-m1-mcp https://gateway.pipeworx.io/dol-m1/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 7,077 tools across 1864 verified sou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases. |
| query | string | no | Alias for question. |
| q | string | no | Alias for question. |
| prompt | string | no | Alias for question. |
| text | string | no | Alias for question. |
| input | string | no | Alias for question. |
| ask | string | no | Alias for question. |
| message | string | no | Alias for question. |
| packs | array | no | OPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]) — the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_p |
Beta version of ask_pipeworx: identical universal router (same 7,077 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so this currently matches ask_pipeworx exactly. Use it exactly like ask_pipeworx when you want the newest routing; results
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases. |
| query | string | no | Alias for question. |
| q | string | no | Alias for question. |
| prompt | string | no | Alias for question. |
| text | string | no | Alias for question. |
| input | string | no | Alias for question. |
| ask | string | no | Alias for question. |
| message | string | no | Alias for question. |
| packs | array | no | OPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]) — the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_p |
Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,077 across 1864 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases. |
| query | string | no | Alias for question. |
| q | string | no | Alias for question. |
| prompt | string | no | Alias for question. |
| text | string | no | Alias for question. |
| input | string | no | Alias for question. |
| ask | string | no | Alias for question. |
| message | string | no | Alias for question. |
| prefer_tool | string | no | Run this exact tool instead of letting the router choose — use a name from a previous answer's alternatives[]. Arguments are still filled from your question. Unknown names are refused, never guessed. |
ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1864 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases. |
| query | string | no | Alias for question. |
| q | string | no | Alias for question. |
| prompt | string | no | Alias for question. |
| text | string | no | Alias for question. |
| input | string | no | Alias for question. |
| ask | string | no | Alias for question. |
| message | string | no | Alias for question. |
| depth | string | no | How many facets to research in parallel: quick=3 (single hop), standard=3 (default; adds a gap-recovery hop that re-angles unanswered facets + a contradictions[] scan across findings), thorough=6 (pai |
Search U.S. DOL 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. Filter by plan year, MEWA/plan name, sponsor name, EIN, headquarters state, state(s) where the plan offers coverage, filing type, and whether it carries stop-loss coverage or is fully insured. Returns
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_year | string/number | no | Plan year of the filing, e.g. 2024. Omit for all years (2003-2025). |
| mewa_name | string | no | Name of the MEWA or association health plan. Substring match. |
| sponsor | string | no | Name of the plan sponsor. Substring match. |
| ein | string | no | MEWA Employer Identification Number (9 digits, dashes optional). Exact match. |
| hq_state | string | no | Two-letter state code of the MEWA's headquarters (e.g. "TX"). |
| coverage_state | string | no | Two-letter state code of a state where the MEWA offers coverage — distinct from hq_state; a MEWA can be headquartered elsewhere and still cover this state. |
| filing_type | string | no | Type of Form M-1 filing. Omit for all types. |
| has_stop_loss | boolean | no | Restrict to MEWAs that do (true) or do not (false) carry stop-loss coverage. Omit for either. |
| fully_insured | boolean | no | Restrict to MEWAs that are (true) or are not (false) fully insured. Omit for either. |
| limit | number | no | Filings to return, 1-100 (default 20). |
| offset | number | no | Pagination offset (default 0). |
Full Form M-1 filing history for one named MEWA or sponsor — every plan year it filed, newest first, plus a count. Matches the name against both the MEWA name and the sponsor name, or pass an exact EIN instead. Use to answer "has this MEWA/association health plan filed Form M-1, and for which years" or "is this plan still registered".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | MEWA or sponsor name, matched as a substring against both fields. |
| ein | string | no | MEWA EIN (9 digits, dashes optional), exact match. Provide this or name. |
| limit | number | no | Filings to examine, 1-100 (default 100). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Dol M1 or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.1.1 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestc7c37c18502c31c1f9342dc066508defd2a711f78280538e9312b011b7e54499
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ask_pipeworx | untrusted-input | untrusted-input: keyword "web_search", declares openWorldHint: true (interacts with entities outside the server) |
| ask_pipeworx_beta | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ask_pipeworx_grounded | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| deep_research | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| recent_alerts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| company_facts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bet_research | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| polymarket_edge_tracker | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| release_calendar_markets | external-sinkuntrusted-input | external-sink: keyword "webhook"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| archive_compare | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pipeworx_feedback | state-write | state-write: declares readOnlyHint: false |
| remember | state-write | state-write: declares readOnlyHint: false |
| dol_m1_search | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| dol_m1_filer | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestc7c37c18502c31c1
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Dol M1 can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.