# Fracfocus (npm · @pipeworx/mcp-fracfocus)

fracfocus -- U.S. hydraulic fracturing chemical disclosures (fleet #2982).

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-fracfocus`
- 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-fracfocus).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 823 tokens (~274/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 Fracfocus MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 82, +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-03 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 65, −14)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `frac_wells` (~279 tokens)

Hydraulic fracturing job disclosures (wells) from FracFocus, the national frac-chemical disclosure registry -- filter by state, county, and/or operator name (operator matches as a substring, case-insensitive). Returns each well's API number, operator, well name, location, job dates, and base fluid volumes, newest job first. Covers FracFocus's full disclosure history (back to its earliest submissions, most of it from 2011 on). Pass the API number from a result into frac_chemicals to get that job's chemical ingredient list. At least one of state, county, or operator is required -- an unscoped scan of ~250k disclosures is not supported.

Input parameters:

- `county` (string): County name, e.g. "Martin". Case-insensitive exact match.
- `limit` (number): Max rows, 1-200. Default 50. A truncated response carries truncated:true, total_matching, and a hint for narrowing.
- `offset` (number): Pagination offset. Default 0.
- `operator` (string): Operator name, substring match, case-insensitive, e.g. "Pioneer".
- `state` (string): US state name, e.g. "Texas" (full name, case-insensitive; FracFocus stores state as a name, not a postal code).

### `frac_chemicals` (~268 tokens)

Chemical ingredient list disclosed for one well, by API number (the American Petroleum Institute well identifier, e.g. "42-317-37262-00-00" or "4231737262" -- dashes optional). Returns, per disclosed job on that well: trade name, supplier, purpose (e.g. "Surfactant", "Biocide", "Proppant"), CAS number, ingredient name, percent of the hydraulic fracturing job by mass, and mass in pounds; trade-secret ingredients carry no CAS number and the claimant company instead. Ingredient-level detail is only loaded for jobs on or after this pack's coverage cutoff (see data_as_of/ingredients_since in the response) -- a well found in frac_wells but outside that window returns found:false with reason "outside_ingredients_coverage", distinct from reason "unknown_api_number" when the well itself does not exist in FracFocus at all.

Input parameters:

- `api_number` (string, required): API well number, with or without dashes, e.g. "42-317-37262-00-00" or "4231737262".
- `limit` (number): Max ingredient rows, 1-500. Default 100.
- `offset` (number): Pagination offset. Default 0.

### `chemical_usage` (~223 tokens)

Where a chemical has been used in hydraulic fracturing jobs, by CAS number (e.g. "7732-18-5" for water, dashes optional) -- optionally scoped to one state. Returns a summary (total ingredient-disclosure rows, distinct wells, distinct states) plus a sample of matching usage records: well, operator, state/county, trade name, purpose, and mass. Only searches this pack's ingredients coverage window (see ingredients_since in the response), not FracFocus's full history. A CAS number that is valid but never appears in the loaded window returns found:false, not an empty success.

Input parameters:

- `cas_number` (string, required): CAS Registry Number, with or without dashes, e.g. "7732-18-5" or "7732185".
- `limit` (number): Max sample rows, 1-200. Default 50.
- `offset` (number): Pagination offset. Default 0.
- `state` (string): US state name to scope the search, e.g. "Texas". Optional.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 65
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Fracfocus MCP server?

Fracfocus is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fracfocus. fracfocus -- U.S. hydraulic fracturing chemical disclosures (fleet #2982). This page covers its npm package (@pipeworx/mcp-fracfocus).

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

Fracfocus 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 Fracfocus MCP server expose?

Fracfocus exposes 3 tools: frac_wells, frac_chemicals, chemical_usage. Their descriptions and schemas cost roughly 770 tokens of context every time the server is loaded.

### Is the Fracfocus MCP server still maintained?

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

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

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