The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Pcaob listing page.
PCAOB Form AP auditor↔issuer engagements and firm inspection reports — hosted, keyless to the caller. Fleet #624: "who audits Company X and which engagement partner signed", "every issuer audited by Firm Y", and "has PCAOB found deficiencies at Firm Y" had no surface before this pack.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
pcaob_auditor_of(company) — which firm audits a company and who the engagement partner is.
Resolves a ticker/company name to SEC CIK first (resolveSecEntity, the same universe edgar
and sec key on); falls back to an issuer-name search across Form AP filings for issuers without a
clean SEC ticker (funds, broker-dealers).pcaob_firm_engagements(firm, fiscal_year?, limit?) — every issuer a firm reported auditing,
optionally scoped to one fiscal year. firm matches a numeric PCAOB Firm ID exactly, otherwise
an ILIKE name search.pcaob_partner_engagements(partner, limit?) — every issuer one named engagement partner signed
for.pcaob_auditor_changes(days?, limit?) — issuers whose most recent Form AP filing names a
different firm than their prior filing, where the change landed in the last N days. Scans up to
1,500 issuers with a filing in the window (response says so if capped).pcaob_inspection_reports(firm, limit?) — PCAOB inspection history for a firm: report year,
Part I.A deficiency rate, audits reviewed, PDF link.Two tables, mirrored by workers/data-pipeline (workers/data-pipeline/src/datasets/pcaob.ts),
migration supabase/migrations/107_pcaob_form_ap_inspections.sql:
pcaob_form_ap — PCAOB's own bulk download of the entire AuditorSearch dataset
(assets.pcaobus.org/firm-filings/FirmFilings.zip), ~156k rows as of 2026-08. Refreshed weekly;
quoted CSV with embedded commas in issuer names, so ingest rides the slow parser and drains over
several cron ticks via the resume-offset protocol (same pattern as USAspending).pcaob_inspection_reports — the Firm Inspection Reports downloadable dataset PCAOB publishes at
pcaobus.org/oversight/inspections/firm-inspection-reports, ~4.3k rows (one per firm per
inspection report). Uses the JSON variant of the dataset, not the CSV — PCAOB's CSV file is
UTF-16LE encoded and this pipeline's parser is fixed at UTF-8; the JSON export of the identical
data is plain UTF-8 and small enough to parse whole-body (format: 'json' in the data-pipeline
runner, added for this pack — see the runner's comment for why).issuer_name only, never dropped.pcaob_auditor_changes compares each issuer's own filing history, not a table-wide diff —
PostgREST has no window functions, so this pulls a bounded recent history per issuer batch and
picks the two most recent filings client-side. It is a real scan (not an aggregate query), hence
the 1,500-issuer cap per call.Form AP covers US issuer audits only, self-reported by the audit firm. Firm inspection findings are Part I.A summary counts from PCAOB's published dataset, not the full report text — the PDF link is provided for that.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/pcaob/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/pcaob_auditor_of. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
Or run it directly to confirm it starts:
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
The gateway picks the right tool and fills the arguments automatically.
MIT