Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
X3 Compliance is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
20
tools declared
local
or remote
—
downloads a day
What it does
FMCSA, OSHA, PHMSA, 811, eCFR and Coast Guard compliance tools. Every answer cites the rule.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user x3-compliance-mcp '--' npx -y x3-compliance-mcp
# 2 — ask your agent for something these tools do
# hos_check, osha_is_recordable, osha_coverage and 17 more
X3 Compliance costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
X3All 1 server
x3allamerican1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user x3-compliance-mcp '--' npx -y x3-compliance-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://mcp.x3api.com/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http x3-compliance-mcp https://mcp.x3api.com/mcpFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
20 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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…
No parameter schema on file.
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: …. Medical-treatment ids (any other text…
No parameter schema on file.
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.
No parameter schema on file.
Compute the total recordable case rate (TRIR), DART rate and days-away case rate per 200,000 hours, the way BLS does.
No parameter schema on file.
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.
No parameter schema on file.
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: …. Holidays default to U.S. federal holidays; pass the one-call center's posted…
No parameter schema on file.
Pull the ticket number, type, dates, excavator, address, work area, coordinates and member utilities out of the plain text of a one-call ticket.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Search the U.S. Coast Guard Port State Information Exchange by vessel name (partial match), call sign, official number, flag or service. Returns each vessel's PSIX ID, name, service, flag and status.
No parameter schema on file.
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.
No parameter schema on file.
The 11 U.S. federal holidays for a year, as observed (weekend holidays moved to Friday or Monday).
No parameter schema on file.
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…
No parameter schema on file.
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…
No parameter schema on file.
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.
No parameter schema on file.
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).
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install X3 Compliance or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 1.1.2 · scanned 15 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest20334991ea1d21b5cc15f92389f271dde2962f488d1ec49a151b5d931b922103
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest20334991ea1d21b5
Scanned2026-11-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.2. Pin a release below and the command asks for exactly that one.
1.1.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish X3 Compliance can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.