Side-by-Side Model Context Protocol Comparison
Tariff Resolver vs Cms
In-depth architectural comparison of the Tariff Resolver and Cms 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.
At a Glance & Executive Verdict
Tariff Resolver
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Cms
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Tariff Resolver if you need specialized Developer Tools tools running via a local process. Choose Cms if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
T
Choose Tariff Resolver 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: search_hs_candidates, calculate_tariff_scenario, watch_tariff_changes.
C
Choose Cms 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).
- Primary tools included: search_datasets, get_dataset, dataset_info.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Tariff Resolver Tools (5)
search_hs_candidates
Product description → top HTS candidates with rates + CBP CROSS ruling links
calculate_tariff_scenario
HTS code + origin + value (+ weight) → structured JSON: base MFN/FTA rate, candidate Chapter 99 layers with per-layer match/confidence, sourced possibly_expired bucket, MPF/HMF
watch_tariff_changes
Register HTS codes to a local watchlist
check_tariff_updates
Diff current vs previous HTS revision — see exactly which rates changed
dataset_info
Data revision date, row counts, source, license
Cms Tools (3)
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).
Tariff Resolver Configuration
Cms Configuration
Frequently Asked Questions
More alternatives to Tariff ResolverMore alternatives to CmsDeveloper Tools category hubCanonical compare URL