Trade Compliance
Server Details
Trade Compliance MCP — the two questions an importer asks that the tariff
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.2% over 22 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-trade-compliance
- GitHub Stars
- 0
- Server Listing
- mcp-trade-compliance
TDQS
Scored across 40 tools
The server mixes several distinct domains (trade compliance, prediction markets, general data lookup, memory, feedback). Within the prediction market cluster, tools like bet_research, polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, resolution_audit, resolution_diff, release_calendar_markets overlap heavily on 'find and evaluate prediction market opportunities', requiring careful reading to pick the right one. Outside that cluster, trade compliance tools (adcvd_orders, adcvd_case, cross_search, cross_ruling) are clearly distinct.
Naming is highly inconsistent. Some tools follow verb_noun (adcvd_orders, adcvd_case, cross_search, cross_ruling, resolve_entity, compare_entities, scan_dependency), but many use brand prefixes (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, pipeworx_feedback, pipeworx_trending, polymarket_*), and several have non-pattern names like bet_research, company_facts, entity_profile, deep_research, discover_tools, generate_llms_txt, kalshi_weather_edge, release_calendar_markets. The mix of snake_case, camelCase (generate_llms_txt vs company_facts), and varied verb styles makes it hard to predict tool names.
40 tools is far too many for a coherent server. The server claims to be 'Trade Compliance' but the majority of tools are unrelated to trade compliance (prediction markets, general data lookup, memory, feedback, AI visibility, npm dependency scanning). This is a grab bag of unrelated utilities, not a focused tool set. The count itself is excessive and the scope is unclear, making it hard for an agent to navigate.
For the stated trade compliance purpose, the surface is reasonably complete for AD/CVD (orders, case lookup) and customs rulings (search, full ruling), but lacks obvious operations like a tariff schedule lookup, country-specific trade remedy lists, or a way to list all active orders. For the broader Pipeworx data platform, the surface is sprawling but still has gaps (no direct SEC filing retrieval, no direct FRED series fetch, no direct market order placement — only research tools). The domain is so broad that completeness is impossible to assess, and the trade compliance core is only partially covered.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
40 tool updates
- First observed
adcvd_case - First observed
adcvd_orders - First observed
ai_visibility_check - First observed
ask_pipeworx - First observed
ask_pipeworx_beta - First observed
ask_pipeworx_grounded - First observed
bet_research - First observed
company_facts - First observed
compare_entities - First observed
cross_ruling - First observed
cross_search - First observed
deep_research - First observed
discover_tools - First observed
entity_profile - First observed
forget - First observed
generate_llms_txt - First observed
kalshi_weather_edge - First observed
list_subscriptions - First observed
pipeworx_feedback - First observed
pipeworx_trending - First observed
polymarket_arbitrage - First observed
polymarket_edge_tracker - First observed
polymarket_edges - First observed
polymarket_fill_risk - First observed
polymarket_kalshi_spread - First observed
recall - First observed
recent_alerts - First observed
recent_changes - First observed
release_calendar_markets - First observed
remember - First observed
resolution_audit - First observed
resolution_diff - First observed
resolve_entity - First observed
scan_competitor_ai_presence - First observed
scan_dependency - First observed
search_within - First observed
subscribe - First observed
suggest_questions - First observed
unsubscribe - First observed
validate_claim
Related MCP Connectors
Trade Intel MCP — Compound tools that chain Comtrade, Census, Treasury,
Census Trade MCP — US Census Bureau International Trade data
Classify, validate & verify HS codes and access tariff compliance data for cross-border trade
HTS MCP — US import tariff rates via the USITC Harmonized Tariff Schedule.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides 14 customs and trade operations as MCP tools, enabling AI agents to query tariff, track declarations, screen dual-use items, and generate AI-powered declarations.19 npm2MIT
- FlicenseAqualityBmaintenanceEnables querying Brazilian foreign trade data through MCP tools for trade flows, freight costs, code resolution, and dataset caveats, with known data defects corrected in responses.4-
- AlicenseNot gradedqualityBmaintenanceProvides access to US import tariff rates via the USITC Harmonized Tariff Schedule, enabling natural language queries for tariff data.78 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for international trade operations focused on Kazakhstan/EAEU/Central Asia routes, providing tools for landed cost calculation, HS classification, Incoterms guidance, logistics estimation, and currency conversion.19 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.