# X3 Compliance (mcpb · x3-compliance.mcpb)

FMCSA, OSHA, PHMSA, 811, eCFR and Coast Guard compliance tools. Every answer cites the rule.

- Trust score: 44/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.x3api.com`: 66/100, [markdown](https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/mcp.md), [page](https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/mcp)
- mcpb · `x3-compliance.mcpb`: 44/100 (this document), [markdown](https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/x3-compliance.md), [page](https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/x3-compliance)
- npm · `x3-compliance-mcp`: 67/100, [markdown](https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/x3-compliance-mcp.md), [page](https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/x3-compliance-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/x3allamerican/x3-compliance-mcp/releases/download/v1.1.0/x3-compliance.mcpb`
- Transport: `stdio`
- SHA-256: `6a2f78159ddcf035753226e672ba7b7ecdbc77e13aee29804e9f9932742ddabf`

## 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-21.

- **Supply Chain Security**: 13/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - No install/post-install scripts declared.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3337 tokens (~166/item across 20 items; 20 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the X3 Compliance MCP server?

X3 Compliance ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 6a2f78159ddcf035753226e672ba7b7ecdbc77e13aee29804e9f9932742ddabf; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/x3allamerican/x3-compliance-mcp/releases/download/v1.1.0/x3-compliance.mcpb`
- SHA-256: `6a2f78159ddcf035753226e672ba7b7ecdbc77e13aee29804e9f9932742ddabf`

### Verify on macOS / Linux

```bash
echo "6a2f78159ddcf035753226e672ba7b7ecdbc77e13aee29804e9f9932742ddabf  x3-compliance.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\x3-compliance.mcpb).Hash -eq "6a2f78159ddcf035753226e672ba7b7ecdbc77e13aee29804e9f9932742ddabf"
```

## 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-21 (score 44, +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-19 (score 43, +2)

- [functional improvement] Stability: unverified → 0.17

### 2026-11-14 (score 41)

First indexed and scored.

## MCP tools (20)

### `hos_check` (~249 tokens)

Check a driver log against FMCSA hours of service

Find every hours-of-service violation in a commercial driver's duty-status log under 49 CFR Part 395 (11/10-hour driving, 14/15-hour window, 30-minute break, 60/70-hour cycle with 34-hour restart, split sleeper berth, adverse conditions, short-haul, 16-hour exception) and how much time the driver has left. Give status changes in time order with ISO 8601 times that include an offset.

Input parameters:

- `asOf` (string): When the log ends ("now"), ISO 8601. Default: the last event.
- `carrier` (string): property (395.3, default) or passenger (395.5)
- `cycle` (string): 70/8 (default) or 60/7
- `events` (array, required): Duty-status changes in time order.
- `homeTimeZone` (string): IANA zone of the home terminal, default America/New_York
- `priorDailyOnDutyHours` (array): On-duty hours for the days before the log, most recent first
- `shortHaul` (boolean): 150 air-mile short-haul driver (no 30-minute break rule)

### `osha_is_recordable` (~653 tokens)

Is this injury or illness OSHA recordable?

Decide under 29 CFR 1904.4-1904.11, 1904.29 and 1904.39 whether a case goes on the OSHA 300 Log, its column (death, days away, restricted, other) and type, whether it is a privacy case, and whether OSHA must be called within 8 or 24 hours. First-aid ids: otcMedicationAtOtcStrength, tetanusImmunization, cleaningWounds, woundCoverings, hotColdTherapy, nonRigidSupport, temporaryImmobilizationForTransport, nailDrillingBlisterDraining, eyePatch, eyeForeignBodyIrrigationOrSwab, splinterRemovalSimple, fingerGuards, massage, drinkingFluidsHeatStress. Medical-treatment ids (any other text also counts as medical treatment): prescriptionMedication, sutures, rigidSplintOrCast, physicalTherapy, otherImmunization, eyeForeignBodyOtherMeans, woundClosingDevice, respiratoryTherapy, surgery. Work-relatedness exceptions: generalPublic, symptomsOnly, voluntaryWellness, eatingDrinking, personalTasks, personalGrooming, commuteParkingLot, coldOrFlu, mentalIllnessNoOpinion.

Input parameters:

- `amputation` (boolean): Amputation
- `bloodborneIllnessDiagnosed` (boolean): A bloodborne illness was diagnosed
- `contaminatedSharps` (boolean): Needlestick or cut from a sharp contaminated with another person's blood or OPIM
- `continuationOfRecordedCase` (boolean): Same type of injury to the same body part, already recorded, not yet healed
- `daysAway` (number): Calendar days away from work, not counting the day of injury
- `death` (boolean): Death
- `diagnosis` (string): Significant diagnosis
- `employeeRequestsPrivacy` (boolean): Employee asked that their name be left off (illnesses only)
- `exception` (string): A 1904.5(b)(2) exception that applies, if any
- `hivHepatitisOrTb` (boolean): HIV, hepatitis or tuberculosis
- `hoursAfterIncident` (number): Hours from the incident to the death, hospitalization, amputation or eye loss
- `inpatientHospitalization` (boolean): In-patient hospitalization
- `intimateBodyPart` (boolean): Intimate body part or reproductive system
- `lossOfConsciousness` (boolean): Lost consciousness
- `lossOfEye` (boolean): Loss of an eye
- `medicalRemoval` (string): Medical removal under an OSHA standard
- `mentalIllness` (boolean): Mental illness
- `preExistingSignificantlyAggravated` (boolean): For a pre-existing condition: did work significantly aggravate it?
- `restrictedDays` (number): Calendar days of restricted work or job transfer
- `sexualAssault` (boolean): Sexual assault
- `treatments` (array): Treatments given: first-aid ids, medical-treatment ids, or plain text
- `tuberculosisAfterExposure` (boolean): TB infection after occupational exposure to a known active case
- `type` (string): injury, skin, respiratory, poisoning, hearing or other (illness)

### `osha_coverage` (~161 tokens)

Must an employer keep OSHA records and file them electronically?

Check 29 CFR 1904.1, 1904.2 and 1904.41: whether a company must keep OSHA 300/300A/301 records (size and partially exempt NAICS industries) and whether an establishment must submit Form 300A, and Forms 300 and 301, to OSHA's Injury Tracking Application, with the due date and posting calendar.

Input parameters:

- `naics` (string, required): The establishment's NAICS code (6 digits best)
- `peakCompanyEmployees` (number, required): Most employees the whole company had at one time in the year
- `peakEstablishmentEmployees` (number, required): Most employees at this establishment at one time in the year
- `year` (number, required): Calendar year the records cover

### `osha_rates` (~98 tokens)

TRIR and DART rates

Compute the total recordable case rate (TRIR), DART rate and days-away case rate per 200,000 hours, the way BLS does.

Input parameters:

- `daysAwayCases` (number, required): Column H
- `deaths` (number): 300A column G
- `hoursWorked` (number, required): Total hours worked by all employees
- `otherCases` (number, required): Column J
- `restrictedCases` (number, required): Column I

### `osha_hearing_shift` (~151 tokens)

Is a hearing loss OSHA recordable (Standard Threshold Shift)?

Compare a baseline and current audiogram at 2000, 3000 and 4000 Hz under 29 CFR 1904.10: Standard Threshold Shift of 10 dB average plus a 25 dB hearing level in the same ear. Optional age correction from 29 CFR 1910.95 Appendix F.

Input parameters:

- `ageCorrectSex` (string): Apply Appendix F age correction using the male or female table
- `baseline` (object, required): { age?, left: {2000, 3000, 4000}, right: {2000, 3000, 4000} } in dB
- `current` (object, required): Same shape as baseline

### `dig_clock_811` (~191 tokens)

811 call-before-you-dig clock

When may an excavator legally start digging after an 811 locate request, when must utilities mark, what is the latest start, and when does the ticket expire, under state one-call law with the statute cited. States: MI, OH, TX. Holidays default to U.S. federal holidays; pass the one-call center's posted list when you have it.

Input parameters:

- `holidays` (array): Notification-center holidays, YYYY-MM-DD
- `longProject` (boolean): Work will outlast the normal ticket life
- `noticeAt` (string, required): When the locate request was made, ISO 8601 with offset
- `plannedStart` (string): Planned start, ISO 8601 with offset (optional; checked for problems)
- `state` (string, required): Two-letter state
- `timeZone` (string): Override the state's time zone, e.g. America/Denver for far west Texas

### `parse_811_ticket` (~52 tokens)

Read an 811 ticket email

Pull the ticket number, type, dates, excavator, address, work area, coordinates and member utilities out of the plain text of a one-call ticket.

Input parameters:

- `text` (string, required): The ticket text

### `cfr_lookup` (~113 tokens)

Read a federal regulation (eCFR)

Get the current (or dated) text of a Code of Federal Regulations citation such as "49 CFR 395.3(a)(2)" or "29 CFR 1910.147(c)(4)" from the official eCFR, paragraph by paragraph with a citation and link for each.

Input parameters:

- `citation` (string, required): A section citation with a title, e.g. 49 CFR 192.605(b)
- `date` (string): YYYY-MM-DD to read the rule as of that date (optional)

### `cfr_search` (~95 tokens)

Search federal regulations (eCFR)

Full-text search of the Code of Federal Regulations. Narrow by title (29 OSHA, 49 DOT/FMCSA/PHMSA, 46 and 33 Coast Guard, 40 EPA) and part.

Input parameters:

- `limit` (number): Results, default 10
- `part` (string): Part number
- `query` (string, required): Words or a "quoted phrase"
- `title` (number): CFR title number

### `cfr_changes` (~123 tokens)

What changed in a federal regulation?

List the substantive amendments to a CFR part (or section) since a date, newest first, from the official eCFR. Optionally compare one section between two dates paragraph by paragraph.

Input parameters:

- `compareTo` (string): With a section: compare the section as of `since` to this date (YYYY-MM-DD) or "latest"
- `part` (string): Part
- `section` (string): Section, e.g. 395.1 (optional)
- `since` (string, required): YYYY-MM-DD
- `title` (number, required): CFR title

### `uscg_vessel_search` (~114 tokens)

Find a vessel in Coast Guard records (PSIX)

Search the U.S. Coast Guard Port State Information Exchange by vessel name (partial match), call sign, official number, flag or service. Returns PSIX vessel IDs for uscg_vessel_profile.

Input parameters:

- `callSign` (string): Call sign
- `flag` (string): Flag, e.g. UNITED STATES
- `name` (string): Vessel name or part of it
- `officialNumber` (string): Official number
- `service` (string): Service type, e.g. Towing Vessel

### `uscg_vessel_profile` (~98 tokens)

Coast Guard compliance snapshot for a vessel

For a PSIX vessel ID: particulars, current certificates (Certificate of Inspection, documentation, load line, class) with days left, recent inspections and incident investigations, deficiencies found and whether they are open, and flags for anything expiring or overdue.

Input parameters:

- `since` (string): Look at activities since YYYY-MM-DD (default 3 years)
- `vesselId` (number, required): PSIX vessel ID from uscg_vessel_search

### `us_federal_holidays` (~43 tokens)

U.S. federal holidays

The 11 U.S. federal holidays for a year, as observed (weekend holidays moved to Friday or Monday).

Input parameters:

- `year` (number, required): Year

### `dq_file_check` (~190 tokens)

Check a driver qualification file (49 CFR 391.51)

Check a driver qualification file: application, pre-employment MVR and safety performance history within 30 days of hire, road test or equivalent, annual MVR and review, medical certificate, CDLIS medical status or National Registry note, Clearinghouse queries. Says what is missing, late, expiring or overdue, whether the driver is qualified to drive today, and retention dates. Dates are YYYY-MM-DD.

Input parameters:

- `asOf` (string): Check as of YYYY-MM-DD (default today)
- `file` (object, required): { driver, hireDate, cdl, application?, preEmploymentMvr?, safetyPerformanceHistory?, roadTest?: {date, kind}, annualMvr?: [dates], annualReview?: [dates], medicalCert?: {issued, expires}, cdlisMedica…

### `dot_random_testing` (~189 tokens)

DOT random drug and alcohol testing: how many, and a fair draw

FMCSA random testing under 49 CFR 382.305: the year's minimum tests from the average pool (50% drug, 10% alcohol for 2026), how many to select this period to stay on pace, and optionally an unbiased random selection from a list of driver IDs (use employee numbers, never names or SSNs), with a pool fingerprint.

Input parameters:

- `alcoholTestsDone` (number): Alcohol tests completed in earlier periods
- `drugTestsDone` (number): Drug tests completed in earlier periods
- `periodsPerYear` (number, required): 4 for quarterly, 12 for monthly
- `poolIds` (array): Optional: driver IDs to draw from now
- `poolSizes` (array, required): Drivers in the pool for each period so far this year, including the current one
- `seed` (string): Optional seed to make the draw reproducible for an auditor

### `mariner_rest_check` (~130 tokens)

Check mariner hours of rest (STCW, 46 CFR 15.1111)

Check work periods against STCW hours of rest (10 in any 24 hours, 77 in any 7 days, no more than two rest periods with one of 6 hours, no more than 14 hours between rests) and optionally the 12-hour towing work limit in 46 U.S.C. 8104(h). Every sliding window is checked.

Input parameters:

- `from` (string): Record start (ISO)
- `to` (string): Record end (ISO)
- `towing` (boolean): Also apply the 12-hour towing limit
- `work` (array, required): Work periods

### `pipeline_design_and_maop` (~219 tokens)

Gas pipeline design pressure, MAOP and impact radius (49 CFR 192)

Steel gas pipeline arithmetic with citations: class location from building count (192.5), design pressure P = (2St/D) x F x E x T (192.105-192.115), test-pressure factor and MAOP as the lowest limit (192.619(a)), hoop stress as % SMYS, and potential impact radius (192.903).

Input parameters:

- `buildings` (number): Buildings intended for human occupancy in the class location unit
- `classLocation` (number): Class location 1-4 (overrides buildings)
- `gasTempF` (number): Gas temperature, °F
- `historicalPsig` (number): Highest actual operating pressure in the look-back period
- `installed` (string): Install date YYYY-MM-DD
- `od` (number, required): Outside diameter, inches
- `smys` (number, required): Specified minimum yield strength, psi
- `testPsig` (number): Post-construction test pressure, psig
- `wall` (number, required): Nominal wall thickness, inches

### `osha_state_jurisdiction` (~90 tokens)

Who enforces workplace safety in a state (OSHA State Plans)

For a state and employer type (private, state-local, federal), say whether federal OSHA or a State Plan (like MIOSHA or Cal/OSHA) has jurisdiction, with the plan's agency, website and 29 CFR 1952 citation.

Input parameters:

- `employer` (string, required): private, state-local or federal
- `state` (string, required): State name or two-letter code

### `sds_check` (~83 tokens)

Read and check a safety data sheet (OSHA HazCom)

Parse the text of a GHS safety data sheet into signal word, hazard and precautionary statements, pictograms, ingredients (CAS numbers with check digits verified), exposure limits, flash point, PPE and revision date; check it against 29 CFR 1910.1200 Appendix D; and build a workplace label.

Input parameters:

- `text` (string, required): The SDS text

### `csa_explain` (~139 tokens)

Explain CSA BASIC measures from roadside inspections

Compute FMCSA SMS measures for HOS Compliance, Vehicle Maintenance, Driver Fitness and HM Compliance from inspections (date, level, violations with basic, severity 1-10 and outOfService), show which inspections drive each measure and when they step down and drop off. Percentiles are not computed.

Input parameters:

- `asOf` (string): YYYY-MM-DD (default today)
- `carrierType` (string): general, passenger or hazmat
- `inspections` (array, required): [{ id?, date, level?, hazmatPlacarded?, violations: [{ basic: hos|vehicle|driverFitness|hazmat, severity, outOfService? }] }]

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/x3-compliance#diagnostics

## Score history

- 2026-11-21: 44
- 2026-11-20: 43
- 2026-11-19: 43
- 2026-11-18: 41
- 2026-11-17: 41
- 2026-11-16: 41
- 2026-11-15: 41
- 2026-11-14: 41

## Common questions

### What is the X3 Compliance MCP server?

X3 Compliance is an MCP server listed in the public MCP registry as io.github.x3allamerican/x3-compliance-mcp. FMCSA, OSHA, PHMSA, 811, eCFR and Coast Guard compliance tools. Every answer cites the rule. This page covers its MCPB bundle (https://github.com/x3allamerican/x3-compliance-mcp/releases/download/v1.1.0/x3-compliance.mcpb).

### Is the X3 Compliance MCP server safe to use?

X3 Compliance scores 44 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 X3 Compliance MCP server expose?

X3 Compliance exposes 20 tools: hos_check, osha_is_recordable, osha_coverage, osha_rates, osha_hearing_shift, and 15 more. Their descriptions and schemas cost roughly 3,181 tokens of context every time the server is loaded.

### What licence is the X3 Compliance MCP server under?

X3 Compliance 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 X3 Compliance MCP server?

VerifyMCP ran 13 checks on X3 Compliance, covering Install scripts, Source repository, Provenance, License and 9 more. 3 items could not be completed, a gap on our side rather than a finding about X3 Compliance: Malware scan, Known CVEs and Dependency health. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/x3allamerican/x3-compliance-mcp
- Website: https://x3allamerican.github.io/x3-compliance-mcp/
- Changelog RSS feed: https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/x3-compliance.xml
- Changelog JSON feed: https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/x3-compliance/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/x3-compliance.json
- HTML version of this page: https://verifymcp.io/servers/x3allamerican-x3-compliance-mcp/x3-compliance
