Hazmat Cfr MCP vs Vortex
A side-by-side look at the Hazmat Cfr MCP and Vortex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
V
VortexDeveloper ToolsWhich stores can actually ship to your destination, at what real landed cost.12EmergingAuth: not declaredVerdict: choose Hazmat Cfr MCP for developer tools work as a local process; choose Vortex for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hazmat Cfr MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
lookup_hazmat_entry, classify_shipping_description, validate_basic_hazmat_description.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Vortex | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 61/100 · Good | 12/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Hazmat Cfr MCP tools 11
lookup_hazmat_entryLook 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.classify_shipping_descriptionParse a basic DOT shipping description into UN/NA number, proper shipping name, hazard class, and packing group.validate_basic_hazmat_descriptionValidate a structured DOT hazmat description against the complete 49 CFR 172.101 Hazardous Materials Table.get_label_requirementsReturn hazard label codes for a UN/NA number or proper shipping name from the complete 49 CFR 172.101 Hazardous Materials Table.check_basic_segregationRun conservative pairwise segregation warnings for supplied hazard classes using a small encoded subset of 49 CFR 177.848 logic.check_limited_quantity_eligibilityConservative helper for common Class 3/Class 8 limited quantity candidate screening. Does not certify shipment compliance.get_shipping_requirementsOne-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.get_placardReturn the 49 CFR 172.504 placard name and quantity threshold for a hazard class/division.decode_special_provisionDecode one or more Column 7 special-provision codes (e.g. IB2, T8, A3, 148) into their 49 CFR 172.102 text.decode_packaging_referenceResolve a Column 8A/8B/8C packaging value (e.g. '150', '202', 'None') to the 49 CFR part 173 section it references.explain_cfr_source
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Hazmat Cfr MCP
{
"mcpServers": {
"hazmat-cfr-mcp": {
"command": "npx",
"args": [
"-y",
"hazmat-cfr-mcp"
]
}
}
}
Vortex
No confirmed install command for Vortex yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Hazmat Cfr MCP is categorized under Developer Tools and uses a local stdio subprocess. Vortex belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Hazmat Cfr MCP for developer tools work and Vortex for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Vortex has no confirmed install command yet — follow its own setup instructions.
Hazmat Cfr MCP has no declared pricing — check the project's own site. Vortex has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hazmat-cfr-mcp and vortex as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hazmat Cfr MCP has a quality signal of 61/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Vortex has 12/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars.