Osha
NPM · @PIPEWORX/MCP-OSHA · 2 COMPONENTS
OSHA MCP — US workplace-safety standards (29 CFR Chapter XVII, parts 1900–1990) AND OSHA…
Available components
Last scanned (13 hours ago)
Scores higher than 72% of npm servers
Category Health and Science
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-osha). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1433 tokens (~286/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-osha@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-osha |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-osha/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685196419 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5e1463c3814f3a04f8a0ebe8c8c131dfc96cf8cd5c640b2562142d7bec08a9fca97f8694f603904c8294dc35ea2c448ea0a048de3d9269e292e39bf50 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
osha_establishment_summary ~220
Rolled-up OSHA enforcement history for an establishment: how many inspections, how many violations, total initial and current penalty amounts across all of them, the most recent inspection date, and the distinct establishment names OSHA has on file matching the search (chains and renamed sites often appear under several). Answers "has OSHA fined X", "total OSHA penalties for X", "how many times has OSHA inspected X", "OSHA enforcement summary for X". Narrower and faster to read than paging through osha_inspections yourself. Example: osha_establishment_summary({ name: "Walmart", state: "AR" }). Live US Dept. of Labor data, refreshed daily; capped at the 50 most recent inspections per establishment — narrow with state for a complete count on a national chain.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Establishment / company name, or a fragment of it. Matched as an upper-cased substring. |
| state | string | – | 2-letter US state postal code to narrow to one state, e.g. "AR". |
No output schema declared.
No examples provided.
osha_inspection ~179
One OSHA inspection by its activity number (from osha_inspections or osha_establishment_summary): the inspection record plus every violation cited — standard cited, violation type (Serious/Willful/Repeat/Other-than-Serious), issuance and abatement dates, instances, employees exposed, and BOTH the initial and current (post-contest/settlement) penalty amounts, plus the summed totals. Answers "what violations came out of inspection X", "what did OSHA fine them for this inspection", "penalty amounts for activity number X". Example: osha_inspection({ activity_nr: 348458035 }). Live US Dept. of Labor data.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_nr | number | yes | The numeric OSHA inspection activity number, e.g. 348458035. Get it from osha_inspections or osha_establishment_summary. |
No output schema declared.
No examples provided.
osha_inspections ~351
OSHA inspections for a named establishment and/or state — the enforcement record OSHA actually took, not the standards. Answers "has OSHA inspected X", "list OSHA inspections for X", "OSHA inspections in state X since date Y". Returns each inspection's address, NAICS code, whether it was a safety or health inspection, the inspection type (Accident / Complaint / Programmed / Referral / Fatality-Catastrophe / etc.), scope, open/close dates, and open-vs-closed status. Establishment matching is a substring match against OSHA's name on file (case-insensitive on input, matched upper-case) — a shorter fragment of the name finds more. Requires establishment or state (or both); `since` narrows to inspections opened after that date. Example: osha_inspections({ establishment: "Walmart", state: "TX" }); osha_inspections({ establishment: "Moran Towing", since: "2020-01-01" }). Live US Dept. of Labor data, refreshed daily. Use osha_inspection with the returned activity_nr for violations and penalties.
| Name | Type | Req | Description |
|---|---|---|---|
| establishment | string | – | Establishment / company name, or a fragment of it, e.g. "Walmart", "Moran Towing". Matched as an upper-cased substring. |
| limit | number | – | Max inspections to return, 1–25 (default 10). |
| since | string | – | Only inspections opened after this date, YYYY-MM-DD, e.g. "2020-01-01". |
| state | string | – | 2-letter US state postal code of the inspected site, e.g. "TX", "NY". |
No output schema declared.
No examples provided.
osha_search ~293
Keyword search across OSHA standards — the US workplace-safety / occupational safety and health regulations in 29 CFR (parts 1900–1990). Answers "what OSHA standards cover X", "OSHA regulation / workplace safety requirement for X", "find the OSHA rule about X". Great for topics: fall protection, hazard communication (HazCom / GHS), lockout tagout (LOTO), respiratory protection, personal protective equipment (PPE), confined space, bloodborne pathogens, machine guarding, scaffolding, excavation, permissible exposure limits, recordkeeping. Returns matching OSHA standards with citation, heading, excerpt, and source URL. Results are filtered to OSHA parts only (1910 general industry, 1926 construction, 1915/1917/1918 maritime, 1928 agriculture, 1904 recordkeeping, etc.) — Title-29 wage/hour parts are excluded. Example: osha_search({ query: "fall protection" }); osha_search({ query: "lockout tagout", limit: 15 }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return, 1–20 (default 10). |
| query | string | yes | Workplace-safety topic or phrase, e.g. "fall protection", "hazard communication", "lockout tagout", "respiratory protection", "PPE", "confined space", "bloodborne pathogens". |
No output schema declared.
No examples provided.
osha_standard ~338
Get the full text of one OSHA standard (US workplace-safety / occupational safety and health regulation) by its citation. OSHA standards are 29 CFR — this returns the exact regulatory wording currently in force. Answers "what is the OSHA standard for X", "does OSHA require X", "read the text of 1910.132", "the OSHA fall protection rule". Forgiving citation input: "1910.132", "29 CFR 1910.132", "§1910.132", "1926.501", even "1910.132(a)" (paragraph is stripped to the section). Covers 29 CFR 1910 general industry, 1926 construction, 1915/1917/1918 maritime, 1928 agriculture, plus recordkeeping (1904) and PPE / hazard communication / lockout tagout / respiratory protection / confined space / bloodborne pathogens standards. Pass a whole part (e.g. "1910" or "1926") to get that part's section list instead. Example: osha_standard({ citation: "1910.132" }) → PPE general requirements; osha_standard({ citation: "1926.501" }) → construction fall protection. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | OSHA standard citation. A section: "1910.132", "29 CFR 1910.1200", "§1910.147", "1926.501", "1910.132(a)". Or a whole part: "1910", "1926", "1926 subpart M" → returns the part's section list. |
No output schema declared.
No examples provided.
How do I install the Osha MCP server?
Osha runs locally as an npm package, launched with npx -y @pipeworx/mcp-osha. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-osha
claude mcp add pipeworx-io-osha -- npx -y @pipeworx/mcp-osha
What is the Osha MCP server?
Osha is an MCP server listed in the public MCP registry as io.github.pipeworx-io/osha. OSHA MCP, US workplace-safety standards (29 CFR Chapter XVII, parts 1900–1990) AND OSHA… This page covers its npm package (@pipeworx/mcp-osha).
Is the Osha MCP server safe to use?
Osha 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 Osha MCP server expose?
Osha exposes 5 tools: osha_standard, osha_search, osha_inspections, osha_inspection, osha_establishment_summary. Their descriptions and schemas cost roughly 1,381 tokens of context every time the server is loaded.
Is the Osha MCP server still maintained?
Osha 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 Osha MCP server under?
Osha 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 Osha MCP server?
VerifyMCP ran 16 checks on Osha, 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.