# Regulatory Catalysts (npm · @pipeworx/mcp-regulatory-catalysts)

Regulatory Catalysts MCP — high-value biotech regulatory calendar events (keyless).

- Trust score: 81/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`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-regulatory-catalysts/regulatory-catalysts-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-regulatory-catalysts/regulatory-catalysts-mcp)
- npm · `@pipeworx/mcp-regulatory-catalysts`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-regulatory-catalysts/pipeworx-mcp-regulatory-catalysts.md), [page](https://verifymcp.io/servers/pipeworx-io-regulatory-catalysts/pipeworx-mcp-regulatory-catalysts)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-regulatory-catalysts`
- 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-regulatory-catalysts).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1359 tokens (~453/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Regulatory Catalysts MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 80, 0)

- [security regression] Stability: 0.17 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 79, +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-30 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `fda_adcom_calendar` (~259 tokens)

Upcoming FDA advisory committee (AdCom) meeting calendar — a leading biotech regulatory catalyst. Lists FDA panel meetings announced in the Federal Register (keyless), extracting the scheduled meeting date from each notice. Covers oncology (ODAC), cellular/tissue & gene therapy (CTGTAC), and every other FDA advisory committee; captures panel-vote meetings that precede or accompany drug/biologic approval decisions (PDUFA-adjacent). Returns each meeting with committee, meeting date (ISO when parseable) plus raw date text, topic, publication date, Federal Register URL, and document number, sorted soonest-first. Use for AdCom, advisory committee, panel vote, drug approval catalyst, FDA meeting calendar, upcoming biotech panels.

Input parameters:

- `committee` (string): Case-insensitive substring filter on the committee / notice title, e.g. "oncologic", "gene therapy", "cardiovascular". Omit for all committees.
- `limit` (number|string): Number of meetings to return (1–20). Default 10.
- `upcoming_only` (boolean|string): Keep only meetings whose extracted date is today or later. Default true. If every recent notice describes a past meeting, the found rows are returned with a note.

### `pdufa_catalysts` (~501 tokens)

Companies with disclosed PDUFA dates — the highest-signal binary biotech catalyst. Searches recent SEC EDGAR 8-K filings (keyless) for PDUFA target / goal / action dates and extracts the date and surrounding context. A PDUFA date is the FDA decision date for an NDA or BLA; it is a scheduled binary event that moves biotech stocks. Returns each disclosure with company, ticker, CIK, filing date, form, PDUFA date (ISO when the filing gives a specific day), pdufa_period when the filing discloses only a coarser grain such as "Q1 2027" or "March 2027", a short context snippet, the SEC filing URL, and accession number. A row may carry a period without a date — that is the filing being vague, not a lookup failure. Use for PDUFA date, PDUFA goal date, FDA decision date, upcoming FDA decisions, drug approval catalyst, NDA/BLA decision date, biotech binary event, catalyst by ticker. ALSO the REGULATORY-STATUS reading of the same data, which is what most callers actually ask: which drugs are currently UNDER FDA REVIEW, which medicines ENTERED FDA REVIEW or were ACCEPTED FOR REVIEW recently, new NDA/BLA SUBMISSIONS and FILINGS ACCEPTED by the FDA, drugs AWAITING FDA APPROVAL, what is in the FDA review queue. A company announces acceptance in an 8-K at the moment review begins, so filing_date is when the drug ENTERED review and pdufa_date is when the decision is due — bounding filing_date with since/until answers "what entered FDA review last week". Note this is REGULATORY review of a marketing application, not clinical trials: for drugs entering or moving through TRIALS use the clinicaltrials tools instead.

Input parameters:

- `limit` (number|string): Number of disclosures to return (1–10). Default 8.
- `query` (string): Optional extra term ANDed into the search — a drug or company name, e.g. "obecabtagene" or "Capricor". Omit to search all PDUFA disclosures in the window.
- `since` (string): Start of the filing-date window (YYYY-MM-DD). Default: 120 days before today.
- `until` (string): End of the filing-date window (YYYY-MM-DD). Default: today.

### `fda_adcom_materials` (~542 tokens)

What evidence is an FDA advisory committee reviewing? For one FDA advisory committee (AdCom) meeting — picked by committee (ODAC, VRBPAC, CTGTAC, or any name fragment), by date, and/or by drug, sponsor or topic — returns the meeting page's posted materials: FDA and sponsor briefing documents, the agenda, questions to the committee, rosters, presentation slides, minutes and transcripts, each with a document type, party (FDA / sponsor / combined), file type and size, and URL. Also extracts the agenda text, the applications under review (NDA/BLA number, product, sponsor, proposed indication), the public docket number, the webcast link, and — when a Questions document is posted — the VOTING QUESTIONS text itself. Reads FDA's own advisory-committee calendar (fda.gov, keyless), which lists meetings from 2016 to the next scheduled one; when a meeting has nothing posted yet it says so with the meeting date and FDA's posting timeline instead of returning an empty list. Use for AdCom briefing document, FDA briefing book, advisory committee materials, ODAC questions, what is the panel voting on, sponsor briefing package, panel agenda, FDA presentation slides, AdCom transcript or minutes. Pair with fda_adcom_calendar (which meetings are coming) and pdufa_catalysts (the decision date that follows the panel).

Input parameters:

- `committee` (string): Committee acronym or name fragment, case-insensitive: "ODAC", "VRBPAC", "CTGTAC", "oncologic", "vaccines", "gene therap", "cardiovascular", "psychopharmacologic", "medical devices"... Omit to search…
- `date` (string): Meeting date filter: a day "2026-04-30", a month "2026-04", or a year "2026". Omit to pick the meeting nearest to today (upcoming or just past).
- `include_questions_text` (boolean|string): When a "Questions" document is posted, fetch it and return the voting-question text (default true). Set false to skip the extra PDF fetch.
- `limit` (number|string): Number of meetings to return with their materials (1–3). Default 1 — the single best match.
- `query` (string): Drug, sponsor, application or topic to find the meeting by, e.g. "camizestrant", "AstraZeneca", "NDA 220359", "COVID-19 vaccine". Matched against meeting titles first, then against the agenda text of…

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Regulatory Catalysts MCP server?

Regulatory Catalysts is an MCP server listed in the public MCP registry as io.github.pipeworx-io/regulatory-catalysts. Regulatory Catalysts MCP, high-value biotech regulatory calendar events (keyless). This page covers its npm package (@pipeworx/mcp-regulatory-catalysts).

### Is the Regulatory Catalysts MCP server safe to use?

Regulatory Catalysts scores 81 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 Regulatory Catalysts MCP server expose?

Regulatory Catalysts exposes 3 tools: fda_adcom_calendar, pdufa_catalysts, fda_adcom_materials. Their descriptions and schemas cost roughly 1,302 tokens of context every time the server is loaded.

### Is the Regulatory Catalysts MCP server still maintained?

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

Regulatory Catalysts 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 Regulatory Catalysts MCP server?

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