# Form5500 (npm · @pipeworx/mcp-form5500)

Form 5500 MCP — wraps the U.S. DOL/EBSA EFAST2 Form 5500 Search service (the live JSON backend…

- Trust score: 90/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `gateway.pipeworx.io`: 88/100, [markdown](https://verifymcp.io/servers/pipeworx-io-form5500/form5500-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-form5500/form5500-mcp)
- npm · `@pipeworx/mcp-form5500`: 90/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-form5500/pipeworx-mcp-form5500.md), [page](https://verifymcp.io/servers/pipeworx-io-form5500/pipeworx-mcp-form5500)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-form5500`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-form5500).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 902 tokens (~300/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Form5500 MCP server?

Form5500 runs locally as an npm package, launched with npx -y @pipeworx/mcp-form5500. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-form5500 -- npx -y @pipeworx/mcp-form5500
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-form5500": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-form5500"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-form5500": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-form5500"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-form5500 -- npx -y @pipeworx/mcp-form5500
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-form5500": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-form5500"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-form5500 --command npx --arg -y --arg @pipeworx/mcp-form5500
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-form5500:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-form5500"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-form5500": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-form5500"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-form5500 -t stdio -c npx -a -y @pipeworx/mcp-form5500
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-form5500": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-form5500"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-20 (score 89, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-19 (score 88, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-18 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 86, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-14 (score 86, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-12 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `form5500_search` (~303 tokens)

Search U.S. Department of Labor Form 5500 / 5500-SF filings (employee benefit & pension plans, EFAST2) by plan sponsor name, employer EIN, plan name, state, and/or plan year. Returns matching filings with sponsor, plan name/number, participant counts, plan assets, plan type, and a link to the filing PDF. Provide at least one of sponsor, ein, plan_name, or state.

Input parameters:

- `ein` (string): Employer Identification Number (9 digits, dashes optional). Exact match.
- `limit` (number): Number of results to return (1-200, default 20).
- `plan_name` (string): Plan name (e.g. "401(k) Profit Sharing Plan"). Partial/phrase match.
- `plan_year` (number): Plan year of the filing (e.g. 2022).
- `sort` (string): Sort order. One of: "datereceived desc" (default), "datereceived asc", "planyear desc", "planyear asc", "assetseoy desc", "participantsboy desc".
- `sponsor` (string): Plan sponsor / employer name (e.g. "Apple Inc", "Microsoft"). Partial/phrase match.
- `start` (number): Offset for pagination (default 0).
- `state` (string): Two-letter U.S. state code of the sponsor (e.g. "CA", "NY").

### `form5500_filing` (~333 tokens)

Get Form 5500 filing detail from the DOL EFAST2 index. Pass ack_id for a single filing (sponsor, plan name/number, participant counts, begin/end-of-year plan assets, plan type, filing date, and full filing PDF URL). Pass ein instead to get a plan sponsor's full filing history (all Form 5500 filings for that EIN, newest first). For an ack_id the response also carries the plan's Schedule H (large plans) or Schedule I (small plans) financial line items - employer / participant / total contributions, income, benefits paid, expenses, assets and liabilities - from the U.S. Department of Labor, EBSA, Form 5500 Schedule H/I datasets (stored copy, data_as_of stated), under schedule_h or schedule_i. schedule_status is always one of h, i, not_filed_sf (5500-SF filers file neither schedule), full_form_no_schedule, not_loaded_year, not_in_dataset_yet, unknown_plan_year, store_unavailable - never a silent null. Schedule C service providers are not included; pdf_url links to the complete filing.

Input parameters:

- `ack_id` (string): EFAST2 Acknowledgement ID (the 30-char filing id, e.g. "20230407122300NAL0001820321001"). Returns one filing.
- `ein` (string): Employer Identification Number (9 digits, dashes optional). Returns the full filing history for that employer.
- `limit` (number): For ein history: max filings to return (1-200, default 50).

### `form5500_schedule` (~212 tokens)

Schedule H (large plan) or Schedule I (small plan) financial line items for a retirement / benefit plan, looked up by employer EIN + plan number (+ plan year) with no Ack ID needed. Returns employer, participant and total contributions, income, benefits paid, administrative expenses, assets and liabilities, plus every stored DOL line by its DOL column name. Source: U.S. Department of Labor, EBSA, Form 5500 Schedule H/I datasets (stored copy; data_as_of and loaded plan years in every response). Omit plan_year for all stored years, newest first. A plan that filed a Form 5500-SF has neither schedule.

Input parameters:

- `ein` (string, required): Employer Identification Number (9 digits, dashes optional).
- `plan_number` (string, required): Three-digit plan number (e.g. "001"; "1" is accepted).
- `plan_year` (number): Plan year (e.g. 2022). Omit for every stored plan year.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-form5500/pipeworx-mcp-form5500#diagnostics

## Score history

- 2026-11-22: 90
- 2026-11-21: 89
- 2026-11-20: 89
- 2026-11-19: 88
- 2026-11-18: 88
- 2026-11-17: 87
- 2026-11-16: 87
- 2026-11-15: 86
- 2026-11-14: 86
- 2026-11-13: 85
- 2026-11-12: 85
- 2026-11-11: 84
- 2026-11-10: 84
- 2026-11-09: 84
- 2026-11-08: 83
- 2026-11-07: 83
- 2026-11-06: 82
- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 65
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Form5500 MCP server?

Form5500 is an MCP server listed in the public MCP registry as io.github.pipeworx-io/form5500. Form 5500 MCP, wraps the U.S. DOL/EBSA EFAST2 Form 5500 Search service (the live JSON backend… This page covers its npm package (@pipeworx/mcp-form5500).

### Is the Form5500 MCP server safe to use?

Form5500 scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Form5500 MCP server expose?

Form5500 exposes 3 tools: form5500_search, form5500_filing, form5500_schedule. Their descriptions and schemas cost roughly 848 tokens of context every time the server is loaded.

### Is the Form5500 MCP server still maintained?

Form5500 is still listed as active in the MCP registry. We last reached this channel on 22 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 Form5500 MCP server under?

Form5500 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 Form5500 MCP server?

VerifyMCP ran 16 checks on Form5500, 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-form5500
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-form5500
- Repository: https://github.com/pipeworx-io/mcp-form5500
- Website: https://pipeworx.io/packs/form5500
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-form5500/pipeworx-mcp-form5500.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-form5500/pipeworx-mcp-form5500/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-form5500/pipeworx-mcp-form5500.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-form5500/pipeworx-mcp-form5500
