Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

X3 Compliance

REMOTE · MCP.X3API.COM · 3 COMPONENTS

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

+3 this week 66 Trust /100

Last scanned (19 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3296 tokens (~164/item across 20 items; 20 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 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.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 63

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.x3api.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=x3api.com CN=WE1,O=Google Trust Services,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA256 a24ca721c69752f30e97f37eae942b8e
SANs: x3api.com, mcp.x3api.com, *.mcp.x3api.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.x3api.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
x3api.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.x3api.com/mcp Verified 200
http (plaintext) http://mcp.x3api.com/mcp Inconclusive 405
MCP tools · 20 exposed · ~3,179 tokens

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 →

Tool Tokens
cfr_changes ~123

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.

NameTypeReqDescription
compareTostring–With a section: compare the section as of `since` to this date (YYYY-MM-DD) or "latest"
partstring–Part
sectionstring–Section, e.g. 395.1 (optional)
sincestringyesYYYY-MM-DD
titlenumberyesCFR title

No output schema declared.

No examples provided.

cfr_lookup ~113

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.

NameTypeReqDescription
citationstringyesA section citation with a title, e.g. 49 CFR 192.605(b)
datestring–YYYY-MM-DD to read the rule as of that date (optional)

No output schema declared.

No examples provided.

cfr_search ~95

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.

NameTypeReqDescription
limitnumber–Results, default 10
partstring–Part number
querystringyesWords or a "quoted phrase"
titlenumber–CFR title number

No output schema declared.

No examples provided.

csa_explain ~139

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.

NameTypeReqDescription
asOfstring–YYYY-MM-DD (default today)
carrierTypestring–general, passenger or hazmat
inspectionsarrayyes[{ id?, date, level?, hazmatPlacarded?, violations: [{ basic: hos|vehicle|driverFitness|hazmat, severity, outOfService? }] }]

No output schema declared.

No examples provided.

dig_clock_811 ~191

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.

NameTypeReqDescription
holidaysarray–Notification-center holidays, YYYY-MM-DD
longProjectboolean–Work will outlast the normal ticket life
noticeAtstringyesWhen the locate request was made, ISO 8601 with offset
plannedStartstring–Planned start, ISO 8601 with offset (optional; checked for problems)
statestringyesTwo-letter state
timeZonestring–Override the state's time zone, e.g. America/Denver for far west Texas

No output schema declared.

No examples provided.

dot_random_testing ~189

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.

NameTypeReqDescription
alcoholTestsDonenumber–Alcohol tests completed in earlier periods
drugTestsDonenumber–Drug tests completed in earlier periods
periodsPerYearnumberyes4 for quarterly, 12 for monthly
poolIdsarray–Optional: driver IDs to draw from now
poolSizesarrayyesDrivers in the pool for each period so far this year, including the current one
seedstring–Optional seed to make the draw reproducible for an auditor

No output schema declared.

No examples provided.

dq_file_check ~190

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.

NameTypeReqDescription
asOfstring–Check as of YYYY-MM-DD (default today)
fileobjectyes{ driver, hireDate, cdl, application?, preEmploymentMvr?, safetyPerformanceHistory?, roadTest?: {date, kind}, annualMvr?: [dates], annualReview?: [dates], medicalCert?: {issued, expires}, cdlisMedica…

No output schema declared.

No examples provided.

hos_check ~249

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.

NameTypeReqDescription
asOfstring–When the log ends ("now"), ISO 8601. Default: the last event.
carrierstring–property (395.3, default) or passenger (395.5)
cyclestring–70/8 (default) or 60/7
eventsarrayyesDuty-status changes in time order.
homeTimeZonestring–IANA zone of the home terminal, default America/New_York
priorDailyOnDutyHoursarray–On-duty hours for the days before the log, most recent first
shortHaulboolean–150 air-mile short-haul driver (no 30-minute break rule)

No output schema declared.

No examples provided.

mariner_rest_check ~130

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.

NameTypeReqDescription
fromstring–Record start (ISO)
tostring–Record end (ISO)
towingboolean–Also apply the 12-hour towing limit
workarrayyesWork periods

No output schema declared.

No examples provided.

osha_coverage ~161

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.

NameTypeReqDescription
naicsstringyesThe establishment's NAICS code (6 digits best)
peakCompanyEmployeesnumberyesMost employees the whole company had at one time in the year
peakEstablishmentEmployeesnumberyesMost employees at this establishment at one time in the year
yearnumberyesCalendar year the records cover

No output schema declared.

No examples provided.

osha_hearing_shift ~151

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.

NameTypeReqDescription
ageCorrectSexstring–Apply Appendix F age correction using the male or female table
baselineobjectyes{ age?, left: {2000, 3000, 4000}, right: {2000, 3000, 4000} } in dB
currentobjectyesSame shape as baseline

No output schema declared.

No examples provided.

osha_is_recordable ~653

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.

NameTypeReqDescription
amputationboolean–Amputation
bloodborneIllnessDiagnosedboolean–A bloodborne illness was diagnosed
contaminatedSharpsboolean–Needlestick or cut from a sharp contaminated with another person's blood or OPIM
continuationOfRecordedCaseboolean–Same type of injury to the same body part, already recorded, not yet healed
daysAwaynumber–Calendar days away from work, not counting the day of injury
deathboolean–Death
diagnosisstring–Significant diagnosis
employeeRequestsPrivacyboolean–Employee asked that their name be left off (illnesses only)
exceptionstring–A 1904.5(b)(2) exception that applies, if any
hivHepatitisOrTbboolean–HIV, hepatitis or tuberculosis
hoursAfterIncidentnumber–Hours from the incident to the death, hospitalization, amputation or eye loss
inpatientHospitalizationboolean–In-patient hospitalization
intimateBodyPartboolean–Intimate body part or reproductive system
lossOfConsciousnessboolean–Lost consciousness
lossOfEyeboolean–Loss of an eye
medicalRemovalstring–Medical removal under an OSHA standard
mentalIllnessboolean–Mental illness
preExistingSignificantlyAggravatedboolean–For a pre-existing condition: did work significantly aggravate it?
restrictedDaysnumber–Calendar days of restricted work or job transfer
sexualAssaultboolean–Sexual assault
treatmentsarray–Treatments given: first-aid ids, medical-treatment ids, or plain text
tuberculosisAfterExposureboolean–TB infection after occupational exposure to a known active case
typestring–injury, skin, respiratory, poisoning, hearing or other (illness)

No output schema declared.

No examples provided.

osha_rates ~98

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

NameTypeReqDescription
daysAwayCasesnumberyesColumn H
deathsnumber–300A column G
hoursWorkednumberyesTotal hours worked by all employees
otherCasesnumberyesColumn J
restrictedCasesnumberyesColumn I

No output schema declared.

No examples provided.

osha_state_jurisdiction ~90

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.

NameTypeReqDescription
employerstringyesprivate, state-local or federal
statestringyesState name or two-letter code

No output schema declared.

No examples provided.

parse_811_ticket ~52

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

NameTypeReqDescription
textstringyesThe ticket text

No output schema declared.

No examples provided.

pipeline_design_and_maop ~219

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).

NameTypeReqDescription
buildingsnumber–Buildings intended for human occupancy in the class location unit
classLocationnumber–Class location 1-4 (overrides buildings)
gasTempFnumber–Gas temperature, °F
historicalPsignumber–Highest actual operating pressure in the look-back period
installedstring–Install date YYYY-MM-DD
odnumberyesOutside diameter, inches
smysnumberyesSpecified minimum yield strength, psi
testPsignumber–Post-construction test pressure, psig
wallnumberyesNominal wall thickness, inches

No output schema declared.

No examples provided.

sds_check ~83

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.

NameTypeReqDescription
textstringyesThe SDS text

No output schema declared.

No examples provided.

us_federal_holidays ~43

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

NameTypeReqDescription
yearnumberyesYear

No output schema declared.

No examples provided.

uscg_vessel_profile ~92

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.

NameTypeReqDescription
sincestring–Look at activities since YYYY-MM-DD (default 3 years)
vesselIdnumberyesPSIX vessel ID

No output schema declared.

No examples provided.

uscg_vessel_search ~118

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.

NameTypeReqDescription
callSignstring–Call sign
flagstring–Flag, e.g. UNITED STATES
namestring–Vessel name or part of it
officialNumberstring–Official number
servicestring–Service type, e.g. Towing Vessel

No output schema declared.

No examples provided.

Install

How do I install the X3 Compliance MCP server?

X3 Compliance is a hosted endpoint at https://mcp.x3api.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.x3api.com

# add to Claude Code
claude mcp add --transport http x3allamerican-x3-compliance-mcp 'https://mcp.x3api.com/mcp'
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 hosted endpoint (https://mcp.x3api.com/mcp).

Is the X3 Compliance MCP server safe to use?

X3 Compliance scores 66 out of 100 on VerifyMCP. 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,179 tokens of context every time the server is loaded.

Does the X3 Compliance MCP server require authentication?

No. We connected to X3 Compliance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the X3 Compliance MCP server still maintained?

X3 Compliance is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the X3 Compliance MCP server?

VerifyMCP ran 12 checks on X3 Compliance, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about X3 Compliance: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.