compliance_checkLABSCO SUMMARY
Answers with a section number, which is the part you can check.
A compliance answer without a citation is an opinion; naming 1910.253(b) gives you something to verify and something to put in a corrective-action record. That is what makes this usable in a walkthrough where the question comes up in front of the equipment. Read it as a first pass, not a ruling — the project itself is explicit that this is AI-generated guidance and no substitute for official OSHA publications or a certified inspection.
What it is
A compliance lookup service for OSHA General Industry standards, reached through one MCP tool. You describe a scenario in plain language; it answers with a verdict, the regulation section it rests on, and what to do about it — rather than handing back a document to read.
What you get
- A single tool taking one
scenariostring — the workplace situation or safety question, however you would phrase it out loud —compliance_check - A verdict rather than a summary: yes or no, followed by the cited section, three bullet points of specific requirements, and corrective actions where they apply
- Coverage across 29 CFR 1910 General Industry: guardrails and fall protection, portable ladders, exit routes, noise and hearing conservation, eye, face and head protection, lockout/tagout, fire extinguishers, forklifts, machine guarding, grinders, compressed air, oxygen and fuel cylinders, electrical safety, hazard communication, and the General Duty Clause
- Citations precise enough to look up — answers name sections such as 1910.23 for guardrails, 1910.147 for lockout/tagout or 1910.1200 for hazard communication, not the standard as a whole
Requirements
An API key from the vendor, passed as OSHA_API_KEY in your client config. There is a free Sandbox tier at 10 calls a day with no credit card, and paid tiers above it — Developer at 500 a day, Team at 2,000, Enterprise at 10,000. Python 3.10+, with mcp and httpx installed via pip; clone the repository and point your client at server.py with python. The project is osha-compliance-assistant (version 1.0.0).
Setup effort
Build from source
USE CASES
01
Settling a question during a floor walkthrough
Describe what you are looking at — the platform height, the cylinder placement, the guard that is missing — and get a verdict with the section to check.
02
Writing up a corrective action
Get the specific requirements and recommended actions alongside the verdict, so the finding and the fix are drafted together.
03
Preparing for an inspection
Run the scenarios you know are marginal — lockout procedure, forklift rules, PPE for a given task — and see which ones come back with a no.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
OSHA_API_KEY in your environment
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
Clone the repository and install its dependencies
Needs Python 3.10 or newer.
CLAUDE DESKTOP · TERMINAL
git clone https://github.com/contextkits/osha-compliance-assistant.git
cd osha-compliance-assistant
pip install mcp httpxAdd this to claude_desktop_config.json
<YOUR_PATH_TO_OSHA_COMPLIANCE_ASSISTANT> is the full path of the clone. For the key, message https://t.me/osha_saas_v2_bot or email gcsmst at gmail.com with the subject "MCP API Key"; the free Sandbox tier allows 10 calls a day.
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"osha-compliance": {
"command": "python",
"args": [
"<YOUR_PATH_TO_OSHA_COMPLIANCE_ASSISTANT>/server.py"
],
"env": {
"OSHA_API_KEY": "<YOUR_OSHA_API_KEY>"
}
}
}
}
