Pbgc
NPM · @PIPEWORX/MCP-PBGC · 2 COMPONENTS
PBGC MCP — pension plan terminations and premium filings.
Available components
Last scanned (10 hours ago)
Scores higher than 72% 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-pbgc). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 921 tokens (~230/item across 4 items; 4 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 Management23
- Stability observed for 7 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 4 Nov 26 +1
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-pbgc@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-pbgc |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-pbgc/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685268084 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1db508dcf44b900b746de55f06fa47a8d1f09fa9434d7bd579898fcc1ea8058ed650dc6bb272b9fbe93a4a43e651cb934fe664f23a5cfc21f9fe78666 |
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 →
pbgc_industry_totals ~139
Aggregate counts across PBGC's registers: how many pension plans PBGC has trusteed (and total participants affected), and how many plans are currently paying premiums (single-employer vs multiemployer), optionally restricted to one US state. Answers "how many pension plans has PBGC taken over", "how many multiemployer plans pay PBGC premiums", "PBGC trusteeships in Texas". Example: pbgc_industry_totals({}); pbgc_industry_totals({ state: "TX" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Restrict to one US state, e.g. "TX" |
No output schema declared.
No examples provided.
pbgc_plan_status ~222
Look up a named pension plan sponsor's PBGC status: whether a pension plan was terminated and taken over by PBGC ("trusteed") because it was underfunded, or is still an active plan currently paying PBGC premiums (single-employer or multiemployer). Searches both PBGC registers by sponsor name, plan name, and/or employer EIN, and returns data_as_of so the caller knows how current each match is. Answers "did United Airlines' pension plan get taken over by PBGC", "is Acme Corp's pension plan still active", "what happened to the Enron pension plan". Example: pbgc_plan_status({ sponsor: "US Airways" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| ein | string | – | Employer EIN (9 digits, dashes optional) |
| limit | number | – | Max matches per register (default 10, max 50) |
| plan_name | string | – | Pension plan name (partial match ok) |
| sponsor | string | – | Plan sponsor / employer name, e.g. "US Airways" |
No output schema declared.
No examples provided.
pbgc_search_premium_filers ~250
Search plans currently paying PBGC premiums — active pension plans (NOT terminated/trusteed), single-employer or multiemployer. Returns plan name, sponsor, admin city/state, EIN, plan effective date, and participant count. Answers "pension plans sponsored by Delta Air Lines", "multiemployer plans paying PBGC premiums in New York", "how many participants in the Acme Corp pension plan". Example: pbgc_search_premium_filers({ sponsor: "Delta Air Lines" }); pbgc_search_premium_filers({ state: "NY", plan_type: "multiemployer", limit: 25 }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| ein | string | – | Employer EIN (9 digits, dashes optional) |
| limit | number | – | Max results (default 20, max 100) |
| plan_name | string | – | Pension plan name (fuzzy, partial ok) |
| plan_type | string | – | "single-employer" or "multiemployer" — omit for both |
| sponsor | string | – | Plan sponsor name (fuzzy, partial ok) |
| state | string | – | Two-letter US state code of the plan administrator |
No output schema declared.
No examples provided.
pbgc_search_trusteed_plans ~256
Search PBGC's register of single-employer pension plans PBGC has trusteed — i.e. taken over as trustee because the plan terminated underfunded. Returns case number, sponsor, plan name, EIN, termination date, date PBGC became trustee, and participant count at termination. Answers "pension plans PBGC has taken over in Illinois", "list trusteed plans for United Airlines", "biggest PBGC trusteeships by participants". Example: pbgc_search_trusteed_plans({ sponsor: "United Airlines" }); pbgc_search_trusteed_plans({ state: "IL", limit: 25 }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| ein | string | – | Employer EIN (9 digits, dashes optional) |
| limit | number | – | Max results (default 20, max 100) |
| plan_name | string | – | Pension plan name (fuzzy, partial ok) |
| sort | string | – | "trusteeship_date desc" (default), "trusteeship_date asc", or "participants desc" |
| sponsor | string | – | Plan sponsor name (fuzzy, partial ok) |
| state | string | – | Two-letter US state code of the sponsor |
No output schema declared.
No examples provided.
How do I install the Pbgc MCP server?
Pbgc runs locally as an npm package, launched with npx -y @pipeworx/mcp-pbgc. 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-pbgc
claude mcp add pipeworx-io-pbgc -- npx -y @pipeworx/mcp-pbgc
What is the Pbgc MCP server?
Pbgc is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pbgc. PBGC MCP, pension plan terminations and premium filings. This page covers its npm package (@pipeworx/mcp-pbgc).
Is the Pbgc MCP server safe to use?
Pbgc scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Pbgc MCP server expose?
Pbgc exposes 4 tools: pbgc_plan_status, pbgc_search_trusteed_plans, pbgc_search_premium_filers, pbgc_industry_totals. Their descriptions and schemas cost roughly 867 tokens of context every time the server is loaded.
Is the Pbgc MCP server still maintained?
Pbgc is still listed as active in the MCP registry. We last reached this channel on 5 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 Pbgc MCP server under?
Pbgc 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 Pbgc MCP server?
VerifyMCP ran 16 checks on Pbgc, 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.