Form5500
NPM · @PIPEWORX/MCP-FORM5500 · 2 COMPONENTS
Form 5500 MCP — wraps the U.S. DOL/EBSA EFAST2 Form 5500 Search service (the live JSON backend…
Available components
Last scanned (4 hours ago)
Scores higher than 85% of npm servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-form5500). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Nov 26 +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.
- 20 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 19 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 15 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 12 Nov 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Analysed npm/@pipeworx/mcp-form5500@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-form5500 |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-form5500/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637318111 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:27c592bbb5e7ee7413becff5a81dbbd13dfcde016411b42b21488cfefa728945b0b129cebf0df9ec9558fa49aa5af78c07544ceeb9ff5768a71c96c8d |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
form5500_filing ~333
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
form5500_schedule ~212
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ein | string | yes | Employer Identification Number (9 digits, dashes optional). |
| plan_number | string | yes | Three-digit plan number (e.g. "001"; "1" is accepted). |
| plan_year | number | – | Plan year (e.g. 2022). Omit for every stored plan year. |
No output schema declared.
No examples provided.
form5500_search ~303
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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"). |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-form5500
claude mcp add pipeworx-io-form5500 -- npx -y @pipeworx/mcp-form5500
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.