Pl Firmy: Polish company check vs Hazmat Cfr MCP

In-depth architectural comparison of the Pl Firmy: Polish company check and Hazmat Cfr MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

P

Choose Pl Firmy: Polish company check when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: PLF_API_KEY.
• Primary tools included: check_vat_whitelist, get_krs_extract, find_company.

Explore Pl Firmy: Polish company check Details

Choose Hazmat Cfr MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: lookup_hazmat_entry, classify_shipping_description, validate_basic_hazmat_description.

Feature & Specification Comparison

Specification	P Pl Firmy: Polish company check Developer Tools	Hazmat Cfr MCP Developer Tools
Summary	Verify Polish companies: VAT white list (MF), KRS, VIES, payment audit PDF, monitoring.	Complete 49 CFR 172.101 hazmat table lookup with special-provision decoding, cited to eCFR.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "pl-firmy-polish-company-check": {
      "url": "https://api.almmity.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "hazmat-cfr-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hazmat-cfr-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons