Skip to main content
Glama

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

A3.6/5.0

Scored across 40 tools

Disambiguation3/5

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 Consistency2/5

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.

Tool Count1/5

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.

Completeness2/5

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.

  1. 40 tool updates
    • First observedadcvd_case
    • First observedadcvd_orders
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observedcross_ruling
    • First observedcross_search
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides 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 npm
    2
    MIT
  • F
    license
    A
    quality
    B
    maintenance
    Enables 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
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides access to US import tariff rates via the USITC Harmonized Tariff Schedule, enabling natural language queries for tariff data.
    78 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP 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 npm
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.