osha-recordkeeping-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| osha_check_recordkeeping_obligationA | The threshold question every other Part 1904 determination assumes: is this employer required to keep OSHA injury and illness records at all? Run this FIRST for any small employer or any establishment that may be in a partially exempt industry — otherwise the chain will confidently instruct them to make 300-Log entries for a log they need not keep. Two things are commonly got backwards: the size exemption is measured across the ENTIRE COMPANY, not one establishment (1904.1(b)(1)), and it uses PEAK employment during the last calendar year, not an average or year-end figure (1904.1(b)(2)). A written request from OSHA or BLS under 1904.41/1904.42 defeats the exemption. CRITICALLY, the exemption is PARTIAL: 1904.39 severe-injury reporting binds every employer covered by the OSH Act regardless — an exempt employer still owes OSHA the 8-hour fatality call. Supply establishment_naics_code and the tool resolves the 1904.2 industry question itself against the closed Appendix A list, matching on the first four digits. Reference and triage only. |
| osha_determine_recording_employerA | Decide WHOSE OSHA 300 Log a case belongs on when the injured person is not a straightforward payroll employee — a temp, a leased or supplied worker, a contractor's employee, someone self-employed, or an owner. Run this FIRST whenever the injured person is not on the employer's payroll: if the answer is 'the other employer' or 'no one', the rest of the chain is not this employer's obligation. The controlling test is DAY-TO-DAY SUPERVISION, not who issues the paycheck (1904.31(b)(2)-(b)(3)): a temp on an agency's payroll whose work you direct daily is your case to record. Self-employed people are not covered by the OSH Act at all (b)(1)), and owners or partners of a sole proprietorship or partnership are not employees for recordkeeping (a)). Every payroll category counts — part-time, seasonal and migrant workers included. 1904.31(b)(4) requires the case be recorded exactly once, never on both employers' logs. Reference and triage only — not legal advice. |
| osha_assess_work_relatednessA | Determine whether an injury or illness is work-related — the gate every other Part 1904 determination depends on. 1904.5(a) presumes work-relatedness for anything arising from the work environment unless one of the nine closed exceptions in 1904.5(b)(2) applies. Run this BEFORE osha_assess_recordability and pass its |
| osha_assess_new_caseA | Determine whether an injury or illness is a NEW case or a continuation of one already on the 300 Log — the second condition of the 1904.4(a) conjunction. Run this after osha_assess_work_relatedness and before osha_assess_recordability, and pass its |
| osha_evaluate_restricted_workA | Decide whether a work restriction or job transfer actually counts as restricted work — not every restriction does. Run this BEFORE passing 'restricted_work_or_transfer' as an outcome to osha_assess_recordability, because getting it wrong moves cases onto or off the 300 Log. The rules it applies: a restriction confined to the day of injury does not count (b)(4)(iii); reduced output while still doing all routine functions does not count (b)(4)(vi); a restriction that misses every routine function does not count (b)(4)(iv), where routine functions are activities performed at least once per week (b)(4)(ii); a partial shift does count (b)(4)(v); and a job transfer is recorded in the same column (b)(4)(ix)-(x)). Critically, when a vague recommendation such as 'light duty' cannot be clarified with the PLHCP, the case MUST be recorded as restricted work (b)(4)(vii)) — the regulation resolves that doubt toward recording. Reference and triage only — not legal advice. |
| osha_evaluate_hearing_lossA | Compute whether an audiogram produces a recordable hearing loss. Two tests must BOTH be met and, critically, in the SAME ear: a Standard Threshold Shift of 10 dB or more averaged at 2000, 3000 and 4000 Hz against the employee's baseline (1904.10(b)(1)), and a total hearing level of 25 dB or more above audiometric zero on the current audiogram (1904.10(a)). An STS in one ear and a 25 dB level in the other does not record. Pass raw audiogram values and the tool does the arithmetic — do not compute averages yourself. If the employee has had a prior recordable hearing loss, pass the REVISED baseline (b)(2)(i)). Age adjustment from Tables F-1/F-2 of 1910.95 appendix F applies to the STS test only, never to the 25 dB test (b)(3)). A retest within 30 days that does not confirm the STS defeats the case; one that confirms it starts a 7-day recording clock (b)(4)). A PLHCP determination of no work-relatedness ends it entirely (b)(6)). Reference and triage only — not legal advice. |
| osha_assess_recordabilityA | Determine whether a work-related injury or illness is OSHA recordable under the 1904.4 decision tree: work-related AND a new case AND meeting either the general recording criteria of 1904.7 OR a specific-case criterion of 1904.8-1904.12 (needlestick, medical removal, hearing loss, tuberculosis). Map the incident narrative to the controlled inputs. The tool applies the closed first-aid list in 1904.7(b)(5)(ii) deterministically and returns a cited determination. Reference and triage only — not legal advice or a medical determination. If the result has determination_final=false, it is provisional: follow the clarification_required instruction, ask the user, and call this tool again with their answer. |
| osha_check_severe_injury_reportingA | Determine whether a fatality, in-patient hospitalization, amputation, or loss of an eye must be reported to OSHA, and compute the actual reporting deadline (8 hours for a fatality, 24 hours for the others) from when the employer learned of it. Also checks the eligibility window from the incident. Datetimes must be full ISO 8601. Applies the 1904.39(b)(11) amputation definition (a severed ear, avulsion, degloving or chipped tooth is NOT an amputation), the (b)(10) rule that a hospitalization for observation or diagnostics alone is not reportable, and the (b)(3)-(b)(4) exclusions for public-road motor vehicle accidents outside construction work zones and events on commercial or public transport. Every one of those still leaves the case RECORDABLE. Reference and triage only — not legal advice. |
| osha_classify_300_log_entryA | For a recordable case, determine the correct OSHA 300 Log outcome column (G death, H days away, I job transfer/restriction, J other recordable) using the most-serious-outcome rule, the injury/illness type column, and the day counts capped at 180. Check |
| osha_check_privacy_caseA | Determine whether a recordable case is a privacy concern case, meaning the employee's name must NOT be entered on the OSHA 300 Log. 1904.29(b)(7) is a closed list — injury to an intimate body part or the reproductive system, sexual assault, mental illness, HIV/hepatitis/tuberculosis, a contaminated needlestick or sharps cut, and other illnesses where the employee voluntarily asks to be left off. 1904.29(b)(8) forbids treating anything else as a privacy case. Returns the required log entry and the confidential-list and redaction obligations that follow, plus the only three recipients who may receive the forms with identifying information intact (1904.29(b)(10)). Run this after a case is determined recordable. |
| osha_route_to_establishment_logA | Decide WHICH establishment's OSHA 300 Log a recordable case belongs on — the last question about an individual incident, and one multi-site employers routinely get backwards. Under 1904.30(b)(4) the case follows the PLACE, not the person: an injury occurring at one of the employer's establishments is recorded on THAT establishment's log even when the employee normally works elsewhere, while an injury away from all of them (a customer site, in transit, remote work) goes on the log of the establishment where the employee normally works. Also reports whether the destination needs its own log — required for establishments expected to operate a year or longer (1904.30(a)), optional for short-term sites which may share a combined log (b)(1) — and, when records are kept centrally, the 7-calendar-day transmission deadline and the two conditions central recordkeeping depends on (b)(2)). Reference and triage only — not legal advice. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_incident | Walk an injury or illness through the full OSHA chain: whether recordkeeping applies at all (1904.1), which employer records it (1904.31), work-relatedness (1904.5), new case (1904.6), restricted work (1904.7(b)(4)), hearing loss (1904.10), recordability (1904.4), severe-injury reporting (1904.39), 300-Log classification (1904.29), whether the employee's name may appear on the log (1904.29(b)(6)-(9)), and which establishment's log it belongs on (1904.30). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| first-aid-treatments | Provenance-backed reference data: Closed first-aid list (1904.7(b)(5)(ii)). Every record carries a CFR cite, source URL, and last-verified date. |
| work-relatedness | Provenance-backed reference data: Work-relatedness presumption and exceptions (1904.5). Every record carries a CFR cite, source URL, and last-verified date. |
| new-case | Provenance-backed reference data: New case vs. continuation (1904.6). Every record carries a CFR cite, source URL, and last-verified date. |
| general-criteria | Provenance-backed reference data: General recording criteria implementation (1904.7(b)). Every record carries a CFR cite, source URL, and last-verified date. |
| specific-case-criteria | Provenance-backed reference data: Specific-case recording criteria (1904.8-1904.12). Every record carries a CFR cite, source URL, and last-verified date. |
| hearing-loss | Provenance-backed reference data: Occupational hearing loss criteria (1904.10). Every record carries a CFR cite, source URL, and last-verified date. |
| severe-injury-reporting | Provenance-backed reference data: Severe-injury reporting rules (1904.39). Every record carries a CFR cite, source URL, and last-verified date. |
| log300-classification | Provenance-backed reference data: OSHA 300 Log classification (1904.29). Every record carries a CFR cite, source URL, and last-verified date. |
| recordkeeping-obligation | Provenance-backed reference data: Scope — partial exemptions (1904.1). Every record carries a CFR cite, source URL, and last-verified date. |
| partially-exempt-industries | Provenance-backed reference data: Partially exempt industries (Appendix A to Subpart B). Every record carries a CFR cite, source URL, and last-verified date. |
| definitions | Provenance-backed reference data: Part 1904 definitions (1904.46). Every record carries a CFR cite, source URL, and last-verified date. |
| covered-employees | Provenance-backed reference data: Covered employees and recording responsibility (1904.31). Every record carries a CFR cite, source URL, and last-verified date. |
| establishments | Provenance-backed reference data: Multiple business establishments (1904.30). Every record carries a CFR cite, source URL, and last-verified date. |
| recording-forms | Provenance-backed reference data: Recording forms and the 7-day deadline (1904.29(a)-(b)(5)). Every record carries a CFR cite, source URL, and last-verified date. |
| privacy-cases | Provenance-backed reference data: Privacy concern cases (1904.29(b)(6)-(9)). Every record carries a CFR cite, source URL, and last-verified date. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/srhtdmrkl/osha-recordkeeping-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server