
Fracfocus MCP server
online · 100% uptimefracfocus -- U.S. hydraulic fracturing chemical disclosures (fleet #2982).
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Fracfocus yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Fracfocus tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Fracfocus compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 234 ms
- faster than 58% of 30,031 servers
Release history: 3 versions in the registry since 2026-10-15, latest 2026-11-02, typically one every 14 days.
Install Fracfocus in Claude Code, Cursor or VS Code
claude mcp add --transport http fracfocus https://gateway.pipeworx.io/fracfocus/mcp
What the publisher says
From the Fracfocus repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/fracfocus
U.S. hydraulic fracturing chemical disclosures -- well-level frac job records (operator, API number, location, dates, base fluid volumes) and the chemical additives/ingredients disclosed for each job (trade name, supplier, purpose, CAS number, mass, percent of job). Fleet #2982.
Part of Pipeworx — an MCP gateway connecting AI agents to 1807+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
FracFocus well-level disclosures by state, county, and/or operator name (operator matches as a substring). At least one of the three is required. Covers FracFocus's full disclosure history. Returns each well's API number, operator, well name, location, job dates, and base fluid volumes, newest job first.
- frac_wells(state?, county?, operator?, limit?, offset?) -- search
list disclosed for one well, by API number (dashes optional). Returns trade name, supplier, purpose, CAS number, ingredient name, percent of the job by mass, and mass in pounds per ingredient; trade-secret ingredients carry no CAS number and a claimant company instead. Ingredient-level detail is only loaded for jobs on or after this pack's coverage cutoff -- a well that exists in fracwells but predates that cutoff returns found:false, reason:"outsideingredientscoverage", distinct from reason:"unknownapi_number" when the well itself is not in FracFocus at all.
- fracchemicals(apinumber, limit?, offset?) -- the chemical ingredient
chemical has been used, by CAS number (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. Only searches the ingredients coverage window, same caveat as frac_chemicals.
- chemicalusage(casnumber, state?, limit?, offset?) -- where a
Every response carries source, sourceurl, license, and the ingredients coverage window (ingredientssince / disclosures_through), so a caller can tell "this well disclosed no chemicals" apart from "this well's job predates what we've loaded."
Auth
Keyless. The tools answer only through the Pipeworx gateway, which holds the data; a standalone npm install has no data to read, and every tool throws a clear "not bound in this runtime" error there instead of returning an empty list.
Data sources
Compact Commission) -- the national hydraulic fracturing chemical disclosure registry. FracFocus publishes only a bulk CSV download, no per-request API, so this pack builds a copy into D1 (scripts/fracfocus/load-data.mjs) rather than proxying per request. Licence (quoted verbatim, checked live 2026-10-14): "Downloaded data may be aggregated or combined with other datasets, but the FracFocus data may not be altered in any way." Also: "Data submitted appears as it was submitted by the operator or operator's authorized agent. FracFocus does not warrant the data in any way." This pack reformats CSV rows into SQL rows and scopes the ingredients table to a recent date window (below) -- it does not change any retained value.
- FracFocus (Ground Water Protection Council / Interstate Oil and Gas
Known gaps -- read before extending this pack
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Fracfocus: common questions
- Is Fracfocus MCP server safe?
- Mostly: it is graded B (77/100). Read the Fracfocus safety report
- How do I install Fracfocus?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Fracfocus need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Fracfocus maintained?
- The last commit was 20 days ago (2026-10-15). The latest release is v0.2.1.
- Is Fracfocus up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Fracfocus compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 234 ms (faster than 58% of 30,031 servers). Full comparison.