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.

io.github.andretaki/hazmat-cfr-mcp

NPM · HAZMAT-CFR-MCP

Complete 49 CFR 172.101 hazmat table lookup with special-provision decoding, cited to eCFR.

Available components

0 this week 85 Trust /100

Last scanned (20 hours ago)

Scores higher than 84% of npm servers

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 135 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 918 tokens (~83/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 0
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 0
    • Stability: pass → 0.97 functional
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 15 Oct 26 +1

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

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 6 Nov 2026 · Analysed npm/hazmat-cfr-mcp@0.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~918 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
check_basic_segregation ~63

Run conservative pairwise segregation warnings for supplied hazard classes using a small encoded subset of 49 CFR 177.848 logic.

NameTypeReqDescription
hazardClassesarrayyesHazard classes/divisions, e.g. ['3', '8', '5.1'].

No output schema declared.

No examples provided.

check_limited_quantity_eligibility ~154

Conservative helper for common Class 3/Class 8 limited quantity candidate screening. Does not certify shipment compliance.

NameTypeReqDescription
hazardClassstringyesPrimary hazard class/division, currently scoped to Class 3 and Class 8.
innerPackageKgnumber–Inner package mass in kilograms; used as an approximate liter-equivalent fallback.
innerPackageMlnumber–Inner package liquid volume in milliliters.
isCombinationPackagingboolean–Whether reviewed packaging is a combination package.
outerGrossKgnumber–Gross outer package weight in kilograms.
packingGroupstring–Packing group I, II, III, 1, 2, or 3.

No output schema declared.

No examples provided.

classify_shipping_description ~57

Parse a basic DOT shipping description into UN/NA number, proper shipping name, hazard class, and packing group.

NameTypeReqDescription
textstringyesFree text such as 'UN1090, Acetone, 3, PG II'.

No output schema declared.

No examples provided.

decode_packaging_reference ~101

Resolve a Column 8A/8B/8C packaging value (e.g. '150', '202', 'None') to the 49 CFR part 173 section it references.

NameTypeReqDescription
codestring–The column value, e.g. '150', '202', '242', or 'None'.
columnstringyesWhich packaging column: exceptions (8A), nonBulk (8B), bulk (8C).

No output schema declared.

No examples provided.

decode_special_provision ~75

Decode one or more Column 7 special-provision codes (e.g. IB2, T8, A3, 148) into their 49 CFR 172.102 text.

NameTypeReqDescription
codesarrayyesSpecial-provision codes, e.g. ['IB2', 'T8', 'A3'].

No output schema declared.

No examples provided.

explain_cfr_source ~54

Explain which public CFR source backs a field or rule in this server.

NameTypeReqDescription
topicstringyesA field/rule such as 'proper shipping name', 'label', 'segregation', or 'shipping papers'.

No output schema declared.

No examples provided.

get_label_requirements ~54

Return hazard label codes for a UN/NA number or proper shipping name from the complete 49 CFR 172.101 Hazardous Materials Table.

NameTypeReqDescription
querystringyesUN/NA number or proper shipping name.

No output schema declared.

No examples provided.

get_placard ~58

Return the 49 CFR 172.504 placard name and quantity threshold for a hazard class/division.

NameTypeReqDescription
hazardClassstringyesHazard class or division, e.g. 3, 2.3, 8.

No output schema declared.

No examples provided.

get_shipping_requirements ~86

One-call summary of what it takes to ship a material: identity, labels, decoded packaging references, special provisions, vessel stowage, and placarding — with citations. Looks up by UN/NA number or proper shipping name.

NameTypeReqDescription
querystringyesUN/NA number or proper shipping name, e.g. UN1830 or 'sulfuric acid'.

No output schema declared.

No examples provided.

lookup_hazmat_entry ~83

Look up a hazardous material by UN/NA number or proper shipping name in the complete 49 CFR 172.101 Hazardous Materials Table (pinned eCFR snapshot). Returns matching entries with decoded symbols and special provisions.

NameTypeReqDescription
querystringyesUN/NA number or proper shipping name, e.g. UN1090 or Acetone.

No output schema declared.

No examples provided.

validate_basic_hazmat_description ~133

Validate a structured DOT hazmat description against the complete 49 CFR 172.101 Hazardous Materials Table.

NameTypeReqDescription
hazardClassstring–Primary hazard class/division, e.g. 3, 5.1, 8.
idNumberstring–UN/NA number, e.g. UN1830.
packingGroupstring–Packing group I, II, III, 1, 2, or 3.
properShippingNamestring–Proper shipping name.
subsidiaryRisksarray–Subsidiary hazard classes/divisions.

No output schema declared.

No examples provided.

Install

How do I install the io.github.andretaki/hazmat-cfr-mcp server?

io.github.andretaki/hazmat-cfr-mcp runs locally as an npm package, launched with npx -y hazmat-cfr-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · hazmat-cfr-mcp

# add to Claude Code
claude mcp add andretaki-hazmat-cfr-mcp -- npx -y hazmat-cfr-mcp
Common questions

What is the io.github.andretaki/hazmat-cfr-mcp server?

io.github.andretaki/hazmat-cfr-mcp is listed in the public MCP registry as io.github.andretaki/hazmat-cfr-mcp. Complete 49 CFR 172.101 hazmat table lookup with special-provision decoding, cited to eCFR. This page covers its npm package (hazmat-cfr-mcp).

Is the io.github.andretaki/hazmat-cfr-mcp server safe to use?

io.github.andretaki/hazmat-cfr-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. 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 io.github.andretaki/hazmat-cfr-mcp server expose?

io.github.andretaki/hazmat-cfr-mcp exposes 11 tools: lookup_hazmat_entry, classify_shipping_description, validate_basic_hazmat_description, get_label_requirements, check_basic_segregation, and 6 more. Their descriptions and schemas cost roughly 918 tokens of context every time the server is loaded.

Is the io.github.andretaki/hazmat-cfr-mcp server still maintained?

io.github.andretaki/hazmat-cfr-mcp is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.andretaki/hazmat-cfr-mcp server under?

io.github.andretaki/hazmat-cfr-mcp 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 io.github.andretaki/hazmat-cfr-mcp server?

VerifyMCP ran 16 checks on io.github.andretaki/hazmat-cfr-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.