Pbgc MCP server

PBGC — pension plan terminations and premium filings

Whether a named pension plan was terminated and taken over by the federal pension insurer (trusteed), or is still an active plan currently paying its premiums — single-employer and multiemployer, from the regulator's own registers.

Part of Pipeworx — an MCP gateway connecting AI agents to 1837+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Why this exists alongside form5500

form5500 shows what a plan FILED with the Department of Labor each year — sponsor, participants, assets. It does not say what happened to the plan afterward. This pack answers that: did PBGC take it over because it terminated underfunded, or is it still active and paying premiums. The two registers (trusteed vs. premium-filer) are disjoint by construction — a plan is in exactly one of PBGC's own rosters, never both at once.

Tools

Auth

Keyless.

Data sources

pension plans PBGC has taken over as trustee because the plan terminated underfunded.

• Pension Benefit Guaranty Corporation (PBGC), trusteed-plan register — single-employer

multiemployer pension plans currently paying PBGC premiums (not terminated).

• Pension Benefit Guaranty Corporation (PBGC), premium-filer rosters — single-employer and

PBGC publishes these as periodically-updated open-government downloads rather than through a query API — its own plan-search page is server-rendered HTML with no JSON backend behind it. Routes live only in scripts/ingest-pbgc.mjs.

Why this is a mirror, and the replace semantics that matter

PBGC distributes each register as a complete current snapshot, not a delta — there is no "what changed since" feed. scripts/ingest-pbgc.mjs (scheduled weekly by .github/workflows/pbgc-refresh.yml) stamps every row it writes with that run's dataasof and then deletes any row in the same table left over from a previous run. That matters specifically for premium filers: a plan that stops paying premiums (because it terminated, merged, or PBGC took it over) has to actually disappear from pbgcsearchpremiumfilers and pbgcplan_status, not linger reading as still-active forever.

Every tool response carries dataasof for exactly this reason — the two registers refresh on different clocks (the trusteed register roughly quarterly, the premium-filer rosters roughly monthly), so a caller comparing a plan's status across both should know which snapshot each half came from.

Schema

supabase/migrations/262pbgc.sql — pbgctrusteedplans (one row per trusteed case; this table only grows, since PBGC's own register does) and pbgcpremiumfilers (one row per currently-filing plan, plantype + plan_id as the key, replaced wholesale on each refresh).

Scale (verified against the live source, 2026-10-17)

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "pbgc": {
      "url": "https://gateway.pipeworx.io/pbgc/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.