# Pcaob (npm · @pipeworx/mcp-pcaob)

PCAOB — Form AP auditor<->issuer engagements + firm inspection reports. Fleet #624: 'who audits…

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-pcaob`
- 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-05.

- **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-pcaob).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 669 tokens (~133/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Pcaob MCP server?

Pcaob runs locally as an npm package, launched with npx -y @pipeworx/mcp-pcaob. 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-pcaob -- npx -y @pipeworx/mcp-pcaob
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 84, +1)

- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 83, +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.

### 2026-10-31 (score 82, +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.

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (5)

### `pcaob_auditor_of` (~129 tokens)

Which PCAOB-registered firm audits a company, and which engagement partner signed the most recent audit report — resolves a ticker or company name to SEC CIK first, then falls back to a name search in our own PCAOB Form AP index if the company has no clean SEC ticker (funds, broker-dealers). Returns firm name/id, engagement partner, audit report date and fiscal period end. Use for "who audits Apple", "Tesla's audit engagement partner".

Input parameters:

- `company` (string, required): Ticker (e.g. "AAPL") or company/issuer name.

### `pcaob_firm_engagements` (~149 tokens)

Every issuer a PCAOB-registered audit firm reported auditing via Form AP, optionally scoped to one fiscal year. Give a firm name ("Ernst & Young", "Deloitte") or its numeric PCAOB Firm ID. Use for "every issuer audited by Deloitte in 2025", "how many public companies does BDO audit".

Input parameters:

- `firm` (string, required): Firm name (partial match ok) or numeric PCAOB Firm ID.
- `fiscal_year` (number): Restrict to engagements whose fiscal period end falls in this year, e.g. 2025.
- `limit` (number): Max issuers to return, 1-500 (default 100).

### `pcaob_partner_engagements` (~93 tokens)

Every issuer a named engagement partner signed for, per Form AP. Give a last name (and optionally first name) — matches are partial. Use for "what companies has [partner name] audited".

Input parameters:

- `limit` (number): Max engagements to return, 1-200 (default 50).
- `partner` (string, required): Engagement partner name — last name alone works, or "First Last".

### `pcaob_auditor_changes` (~135 tokens)

Issuers whose most recent Form AP filing names a DIFFERENT audit firm than their prior filing, where the new filing landed in the last N days — the "who switched auditors recently" aggregation, which no upstream PCAOB page offers directly. Scans issuers with a Form AP filing in the window (capped at 1500 issuers per call) and compares each against its own filing history.

Input parameters:

- `days` (number): Lookback window in days for the most recent filing (default 90).
- `limit` (number): Max changes to return, 1-200 (default 50).

### `pcaob_inspection_reports` (~109 tokens)

PCAOB inspection history for an audit firm: report year, Part I.A deficiency rate, audits reviewed, and a link to the PDF report. Give a firm name (partial match ok). Use for "has PCAOB found deficiencies at Deloitte", "KPMG PCAOB inspection history".

Input parameters:

- `firm` (string, required): Firm name, partial match ok, e.g. "Deloitte".
- `limit` (number): Max reports to return, 1-100 (default 25).

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Pcaob MCP server?

Pcaob is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pcaob. PCAOB, Form AP auditor<->issuer engagements + firm inspection reports. Fleet #624: 'who audits… This page covers its npm package (@pipeworx/mcp-pcaob).

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

Pcaob scores 84 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 Pcaob MCP server expose?

Pcaob exposes 5 tools: pcaob_auditor_of, pcaob_firm_engagements, pcaob_partner_engagements, pcaob_auditor_changes, pcaob_inspection_reports. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.

### Is the Pcaob MCP server still maintained?

Pcaob 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 Pcaob MCP server under?

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

VerifyMCP ran 16 checks on Pcaob, 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-pcaob
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-pcaob
- Repository: https://github.com/pipeworx-io/mcp-pcaob
- Website: https://pipeworx.io/packs/pcaob
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-pcaob/pipeworx-mcp-pcaob.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-pcaob/pipeworx-mcp-pcaob/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-pcaob/pipeworx-mcp-pcaob.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-pcaob/pipeworx-mcp-pcaob