Comtrade MCP — UN Comtrade API for international bilateral trade data
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.
Scored across 40 tools
Multiple tools have unclear boundaries: ask_pipeworx_beta currently matches ask_pipeworx exactly, and bet_research, polymarket_edges, and polymarket_arbitrage all scan for prediction-market edge. scan_competitor_ai_presence simply wraps ai_visibility_check, and discover_tools, suggest_questions, and pipeworx_trending occupy overlapping discovery territory.
All names are snake_case and readable, but conventions are mixed: verb-first (ask_pipeworx, resolve_entity, validate_claim) coexists with noun-first (entity_profile, company_facts, bet_research), and the ask_pipeworx_* / pipeworx_* / polymarket_* prefixes are applied inconsistently. The pattern is not chaotic but is not predictable either.
40 tools is well past the heavy range, and the sprawl is severe relative to the server name 'Comtrade': only 4 tools are trade-data related, while the rest cover prediction markets, npm scanning, AI visibility, llms.txt generation, and memory. A platform of this breadth cannot justify the count under a specialized name.
For the apparent broad data-access purpose, the surface covers a lot: universal routing, grounded answers, deep research, entity resolution, comparisons, claim validation, subscriptions, and memory. However, there are notable gaps such as no subscription update (only create/list/delete) and no direct citation/record fetch tool in the set, and the server's actual domain is unclear.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
ai_visibility_check1 field changedInput schema / examplesAdded value: +[
+ {
+ "entity": "Tesla"
+ }
+]ask_pipeworx_beta1 field changedInput schema / examplesAdded value: +[
+ {
+ "question": "What is the current US unemployment rate?"
+ }
+]ask_pipeworx_grounded1 field changedInput schema / examplesAdded value: +[
+ {
+ "question": "What was Apple's fiscal 2023 revenue?"
+ }
+]company_factscompare_entities1 field changedInput schema / examplesAdded value: +[
+ {
+ "type": "company",
+ "values": [
+ "AAPL",
+ "MSFT"
+ ]
+ }
+]deep_research1 field changedInput schema / examplesAdded value: +[
+ {
+ "depth": "quick",
+ "question": "What is the current US unemployment rate and how has it changed over the past year?"
+ }
+]entity_profile1 field changedInput schema / examplesAdded value: +[
+ {
+ "type": "company",
+ "value": "AAPL"
+ }
+]generate_llms_txt1 field changedInput schema / examplesAdded value: +[
+ {
+ "url": "https://pipeworx.io"
+ }
+]kalshi_weather_edgepipeworx_feedback1 field changedInput schema / examplesAdded value: +[
+ {
+ "message": "Fleet #2184 smoke test: verifying pipeworx_feedback example call returns non-empty.",
+ "type": "other"
+ }
+]pipeworx_trending1 field changedInput schema / examplesAdded value: +[
+ {
+ "window": "7d"
+ }
+]polymarket_arbitrage1 field changedInput schema / examplesAdded value: +[
+ {
+ "topic": "Fed rate decision"
+ }
+]polymarket_edge_tracker1 field changedInput schema / examplesAdded value: +[
+ {
+ "days": 14,
+ "window": "1wk"
+ }
+]polymarket_edges3 fields changedInput schema / examplesAdded value: +[
+ {
+ "limit": 5,
+ "window": "1wk"
+ }
+]Input schema / properties / min_edge_pp / descriptionPrevious value: -"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage."New value: +"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage and Polymarket's own taker fee."Input schema / properties / slippage_pp / descriptionPrevious value: -"Assumed execution slippage in percentage points per leg (default 0.3). Subtracted from raw |edge| before ranking and Kelly sizing. Polymarket has zero trading fees as of 2024 but bid/ask + thin depth typically eats 20-50bp per trade. Bump for very thin partitions; drop to 0 if you have a smarter fill model."New value: +"Assumed execution slippage in percentage points per leg (default 0.3), for bid/ask + thin depth cost that a last-trade price does not show. Subtracted from raw |edge| before ranking and Kelly sizing, ON TOP OF Polymarket's own taker fee — which is NOT zero (rate 0.04-0.07 depending on category, read off each market's own published fee schedule; see fees_pp_applied on every row and fees.ts for the full schedule). Bump slippage for very thin partitions; drop to 0 if you have a smarter fill model — the fee still applies regardless."polymarket_fill_risk1 field changedInput schema / examplesAdded value: +[
+ {
+ "market": "will-the-fed-increase-interest-rates-by-25-bps-after-the-december-2026-meeting-20260729232808636",
+ "side": "buy_yes",
+ "size_usd": 1000
+ }
+]recent_changes1 field changedInput schema / examplesAdded value: +[
+ {
+ "since": "30d",
+ "type": "company",
+ "value": "AAPL"
+ }
+]release_calendar_marketsremember1 field changedInput schema / examplesAdded value: +[
+ {
+ "key": "target_ticker",
+ "value": "AAPL"
+ }
+]resolution_auditresolution_diffresolve_entity1 field changedInput schema / examplesAdded value: +[
+ {
+ "type": "company",
+ "value": "AAPL"
+ }
+]scan_competitor_ai_presence1 field changedInput schema / examplesAdded value: +[
+ {
+ "entities": [
+ "Pipeworx",
+ "Zapier"
+ ]
+ }
+]scan_dependency1 field changedInput schema / examplesAdded value: +[
+ {
+ "package": "left-pad"
+ }
+]search_within1 field changedInput schema / examplesAdded value: +[
+ {
+ "query": "supply-chain risk",
+ "text": "Apple Inc. reported fiscal 2023 revenue of $383.285 billion, driven by strong iPhone and Services growth. Net income was $96.995 billion. The company faced supply-chain risk in China during the quarter."
+ }
+]suggest_questions1 field changedInput schema / examplesAdded value: +[
+ {
+ "topic": "finance"
+ }
+]validate_claim1 field changedInput schema / examplesAdded value: +[
+ {
+ "claim": "Apple's fiscal 2023 revenue was $383 billion"
+ }
+]bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "when-will-bitcoin-hit-150k"
- },
- {
- "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "when-will-bitcoin-hit-150k"
+ },
+ {
+ "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."comtrade_top_commodities2 fields changedInput schema / properties / frequencyAdded value: +{
+ "description": "Data frequency: \"annual\" (default) or \"monthly\". Monthly coverage is thinner — not every reporter files monthly, and recent months lag. When \"monthly\", pass `year` as YYYYMM.",
+ "type": "string"
+}Input schema / properties / year / descriptionPrevious value: -"Trade year (e.g., \"2024\")"New value: +"Trade period. For frequency=\"annual\" (default): a year, e.g. \"2024\". For frequency=\"monthly\": year+month as YYYYMM, e.g. \"202401\"."comtrade_top_partners3 fields changedInput schema / examplesPrevious value: -[
- {
- "flow": "X",
- "limit": 10,
- "reporter_code": "842",
- "year": "2024"
- },
- {
- "flow": "M",
- "reporter_code": "156",
- "year": "2023"
- }
-]New value: +[
+ {
+ "flow": "X",
+ "limit": 10,
+ "reporter_code": "842",
+ "year": "2024"
+ },
+ {
+ "flow": "M",
+ "reporter_code": "156",
+ "year": "2023"
+ },
+ {
+ "flow": "X",
+ "frequency": "monthly",
+ "limit": 5,
+ "reporter_code": "682",
+ "year": "202401"
+ }
+]Input schema / properties / frequencyAdded value: +{
+ "description": "Data frequency: \"annual\" (default) or \"monthly\". Monthly coverage is thinner — not every reporter files monthly, and recent months lag; a reporter with no filing for the requested month is absent from the ranking, not shown at zero. When \"monthly\", pass `year` as YYYYMM.",
+ "type": "string"
+}Input schema / properties / year / descriptionPrevious value: -"Trade year (e.g., \"2024\")"New value: +"Trade period. For frequency=\"annual\" (default): a year, e.g. \"2024\". For frequency=\"monthly\": year+month as YYYYMM, e.g. \"202401\"."comtrade_trade_data3 fields changedInput schema / examplesPrevious value: -[
- {
- "partner_code": "156",
- "reporter_code": "842",
- "year": "2024"
- },
- {
- "flow": "M",
- "hs_code": "8471",
- "partner_code": "156",
- "reporter_code": "842",
- "year": "2023"
- }
-]New value: +[
+ {
+ "partner_code": "156",
+ "reporter_code": "842",
+ "year": "2024"
+ },
+ {
+ "flow": "M",
+ "hs_code": "8471",
+ "partner_code": "156",
+ "reporter_code": "842",
+ "year": "2023"
+ },
+ {
+ "frequency": "monthly",
+ "partner_code": "818",
+ "reporter_code": "682",
+ "year": "202401"
+ }
+]Input schema / properties / frequencyAdded value: +{
+ "description": "Data frequency: \"annual\" (default) for yearly totals, or \"monthly\" for month-level data. Monthly coverage is thinner than annual — not every reporter files monthly, and recent months lag by reporter; a country-month with no filing is simply omitted from the results, not returned as zero. When \"monthly\", pass `year` as YYYYMM.",
+ "type": "string"
+}Input schema / properties / year / descriptionPrevious value: -"Trade year (e.g., \"2024\")"New value: +"Trade period. For frequency=\"annual\" (default): a year, e.g. \"2024\". For frequency=\"monthly\": year+month as YYYYMM, e.g. \"202401\" for January 2024."entity_profile3 fields changedInput schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."Input schema / properties / type / enumPrevious value: -[
- "company"
-]New value: +[
+ "company",
+ "ticker"
+]Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."Trade Intel MCP — Compound tools that chain Comtrade, Census, Treasury,
Census Trade MCP — US Census Bureau International Trade data
Alpha Vantage MCP — Stock market data, fundamentals, and earnings
DBnomics MCP — meta-aggregator over 80+ stats providers
Add one secure layer between your agents and this server.