Comtrade

Name: Comtrade
Author: pipeworx-io

Server Details

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.

Status: Unhealthy
Uptime: 19.4% over 62 days
Last Tested: 2026-10-18 10:03
Transport: Streamable HTTP
URL
Repository: pipeworx-io/mcp-comtrade
GitHub Stars: 0
Server Listing: mcp-comtrade

TDQS

A3.8/5.0

Scored 2026-10-06 00:10 across 40 tools

Disambiguation3/5

The set has several overlapping tool families: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research all route natural-language questions, discover_tools/suggest_questions/pipeworx_trending all serve meta-discovery, and bet_research/polymarket_edges/polymarket_arbitrage overlap on prediction-market scanning. The long descriptions help differentiate them, but an agent can still easily misselect among the router and market-analysis variants.

Naming Consistency4/5

Nearly all names are snake_case, with readable domain prefixes (comtrade_, polymarket_, pipeworx_) that group related tools. However, the set mixes verb_noun names (resolve_entity, validate_claim, scan_dependency) with noun phrases (entity_profile, company_facts, release_calendar_markets) and uses beta/grounded suffix variants, so the pattern is not fully predictable.

Tool Count2/5

At 40 tools, this is well above the 3-15 well-scoped range and includes many overlapping meta-routers, memory helpers, subscription tools, and prediction-market variants. Even for a broad data gateway, the surface feels bloated rather than curated; several tools earn their place, but too many are alternate entry points to the same underlying capability.

Completeness3/5

For a broad Pipeworx-style gateway, the surface covers company research, prediction markets, memory, subscriptions, and basic Comtrade trade data. But several advertised domains (weather, real estate, clinical trials, general stock quotes) lack direct tools and depend on router fallbacks, and the Comtrade side itself is thin relative to the overall 40-tool surface.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateOct 6, 2026

Changedrelease_calendar_markets2 fields changed

addedOutput schema / properties / empty_reason

Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}

addedOutput schema / properties / hint

Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}

9 tool updatesSep 29, 2026

Changedask_pipeworx3 fields changed

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Changedask_pipeworx_beta3 fields changed

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Changedask_pipeworx_grounded3 fields changed

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Changedcomtrade_top_partners6 fields changed

changedInput schema / examples

Previous 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"
-  }
-]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"
+  },
+  {
+    "commodity_code": "2603",
+    "flow": "M",
+    "limit": 5,
+    "reporter_code": "China",
+    "year": "2024"
+  }
+]

addedInput schema / properties / cmd_code

Added value: +{
+  "description": "Alias for hs_code — HS commodity code. Use this OR hs_code, not both.",
+  "type": "string"
+}

addedInput schema / properties / commodity

Added value: +{
+  "description": "Alias for hs_code — HS commodity code. Use this OR hs_code, not both.",
+  "type": "string"
+}

addedInput schema / properties / commodity_code

Added value: +{
+  "description": "Alias for hs_code — HS commodity code (e.g. \"2603\" for copper ores). Use this OR hs_code, not both.",
+  "type": "string"
+}

addedInput schema / properties / hs

Added value: +{
+  "description": "Alias for hs_code — HS commodity code. Use this OR hs_code, not both.",
+  "type": "string"
+}

changedInput schema / properties / hs_code / description

Previous value: -"Optional HS commodity code to filter by specific product"New value: +"Optional HS commodity code to filter by specific product (e.g. \"2603\" for copper ores) — omit for all commodities (TOTAL). Aliases accepted: commodity_code, commodity, hs, cmd_code (pass exactly one)."

Changedcomtrade_trade_data5 fields changed

addedInput schema / properties / cmd_code

Added value: +{
+  "description": "Alias for hs_code — HS commodity code. Use this OR hs_code, not both.",
+  "type": "string"
+}

addedInput schema / properties / commodity

Added value: +{
+  "description": "Alias for hs_code — HS commodity code. Use this OR hs_code, not both.",
+  "type": "string"
+}

addedInput schema / properties / commodity_code

Added value: +{
+  "description": "Alias for hs_code — HS commodity code (e.g. \"2603\" for copper ores). Use this OR hs_code, not both.",
+  "type": "string"
+}

addedInput schema / properties / hs

Added value: +{
+  "description": "Alias for hs_code — HS commodity code. Use this OR hs_code, not both.",
+  "type": "string"
+}

changedInput schema / properties / hs_code / description

Previous value: -"HS commodity code at 2/4/6 digit level (e.g., \"8471\" for computers). Optional — omit for all commodities."New value: +"HS commodity code at 2/4/6 digit level (e.g., \"8471\" for computers, \"2603\" for copper ores). Optional — omit for all commodities. Aliases accepted: commodity_code, commodity, hs, cmd_code (pass exactly one of hs_code/commodity_code/commodity/hs/cmd_code — do not need hs_code as well)."

Changeddeep_research8 fields changed

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / input

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / prompt

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"The research question, in natural language. Broad/multi-part is fine — decomposition is the point."New value: +"The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases."

addedInput schema / properties / text

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Changedforget4 fields changed

addedInput schema / properties / k

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

changedInput schema / properties / key / description

Previous value: -"Memory key to delete"New value: +"Memory key to delete. Accepts name, k, label as aliases."

addedInput schema / properties / label

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Changedrecall4 fields changed

addedInput schema / properties / k

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

changedInput schema / properties / key / description

Previous value: -"Memory key to retrieve (omit to list all keys)"New value: +"Memory key to retrieve (omit to list all keys). Accepts name, k, label as aliases."

addedInput schema / properties / label

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Changedremember9 fields changed

addedInput schema / properties / content

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

addedInput schema / properties / data

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

addedInput schema / properties / k

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

changedInput schema / properties / key / description

Previous value: -"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\")"New value: +"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\"). Accepts name, k, label as aliases."

addedInput schema / properties / label

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / text

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

addedInput schema / properties / v

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

changedInput schema / properties / value / description

Previous value: -"Value to store (any text — findings, addresses, preferences, notes)"New value: +"Value to store (any text — findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON."

26 tool updatesSep 20, 2026

Changedai_visibility_check1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "entity": "Tesla"
+  }
+]
```

Changedask_pipeworx_beta1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "question": "What is the current US unemployment rate?"
+  }
+]

Changedask_pipeworx_grounded1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "question": "What was Apple's fiscal 2023 revenue?"
+  }
+]

Addedcompany_facts

Changedcompare_entities1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "type": "company",
+    "values": [
+      "AAPL",
+      "MSFT"
+    ]
+  }
+]

Changeddeep_research1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "depth": "quick",
+    "question": "What is the current US unemployment rate and how has it changed over the past year?"
+  }
+]

Changedentity_profile1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Changedgenerate_llms_txt1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "url": "https://pipeworx.io"
+  }
+]

Addedkalshi_weather_edge

Changedpipeworx_feedback1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "message": "Fleet #2184 smoke test: verifying pipeworx_feedback example call returns non-empty.",
+    "type": "other"
+  }
+]

Changedpipeworx_trending1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "window": "7d"
+  }
+]
```
Changedpolymarket_arbitrage1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "topic": "Fed rate decision"
+  }
+]
```
Changedpolymarket_edge_tracker1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "days": 14,
+    "window": "1wk"
+  }
+]
```

Changedpolymarket_edges3 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "limit": 5,
+    "window": "1wk"
+  }
+]

changedInput schema / properties / min_edge_pp / description

Previous 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."

changedInput schema / properties / slippage_pp / description

Previous 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."

Changedpolymarket_fill_risk1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "market": "will-the-fed-increase-interest-rates-by-25-bps-after-the-december-2026-meeting-20260729232808636",
+    "side": "buy_yes",
+    "size_usd": 1000
+  }
+]

Changedrecent_changes1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "since": "30d",
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Addedrelease_calendar_markets

Changedremember1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "key": "target_ticker",
+    "value": "AAPL"
+  }
+]

Addedresolution_audit
Addedresolution_diff

Changedresolve_entity1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Changedscan_competitor_ai_presence1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "entities": [
+      "Pipeworx",
+      "Zapier"
+    ]
+  }
+]

Changedscan_dependency1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "package": "left-pad"
+  }
+]
```

Changedsearch_within1 field changed

addedInput schema / examples

Added 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."
+  }
+]

Changedsuggest_questions1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "topic": "finance"
+  }
+]
```

Changedvalidate_claim1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "claim": "Apple's fiscal 2023 revenue was $383 billion"
+  }
+]

1 tool updateSep 12, 2026

Changedbet_research2 fields changed

changedInput schema / examples

Previous 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"
+  }
+]

changedInput schema / properties / market / description

Previous 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."

2 tool updatesSep 11, 2026

Changedbet_research2 fields changed

changedInput schema / examples

Previous 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"
+  }
+]

changedInput schema / properties / market / description

Previous 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."

Changedpolymarket_kalshi_spread2 fields changed

changedInput schema / examples

Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]

changedInput schema / properties / topic / description

Previous 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."

3 tool updatesSep 8, 2026

Changedcomtrade_top_commodities2 fields changed

addedInput schema / properties / frequency

Added 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"
+}

changedInput schema / properties / year / description

Previous 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\"."

Changedcomtrade_top_partners3 fields changed

changedInput schema / examples

Previous 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"
+  }
+]

addedInput schema / properties / frequency

Added 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"
+}

changedInput schema / properties / year / description

Previous 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\"."

Changedcomtrade_trade_data3 fields changed

changedInput schema / examples

Previous 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"
+  }
+]

addedInput schema / properties / frequency

Added 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"
+}

changedInput schema / properties / year / description

Previous 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."

1 tool updateSep 3, 2026

Changedentity_profile3 fields changed

changedInput schema / properties / type / description

Previous 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."

changedInput schema / properties / type / enum

Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]

changedInput schema / properties / value / description

Previous 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."

Related MCP Connectors

un-comtrade-mcp-server A
io.github.cyanheads
UN Comtrade international trade statistics via MCP. Country/HS lookups, flows, balances, rankings.
Open Data Government Data
913
Trade Intel A
io.github.pipeworx-io
Trade Intel MCP — Compound tools that chain Comtrade, Census, Treasury,
Government Data Open Data Research & Data
432
Census Trade A
io.github.pipeworx-io
Census Trade MCP — US Census Bureau International Trade data
Government Data Open Data Research & Data
2
Brazil Comex Stat
io.github.pipeworx-io
Brazil Comex Stat MCP — Brazilian foreign trade statistics from MDIC
Government Data Open Data
1

Related MCP Servers

@cyanheads/un-comtrade-mcp
Open Data Research & Data
cyanheads
A
license
Not graded
quality
A
maintenance
Access UN Comtrade international merchandise and services trade statistics via MCP tools for country lookups, HS commodity search, bilateral trade flows, balances, rankings, and data availability.
Updated a day ago (2026-10-17 23:13 UTC)
92 npm
3
Apache 2.0
mcp-comexstat
Databases Search
luizzzvictor
A
license
D
quality
D
maintenance
Servidor MCP para a API do ComexStat, ferramenta de acesso às estatísticas de comércio exterior do Brasil.
Updated 3 months ago (2026-07-24 16:47 UTC)
20
3 npm
2
MIT
census-trade-mcp-server
Government Data Open Data Research & Data
jslagle9
A
license
A
quality
C
maintenance
An MCP server for the U.S. Census Bureau's International Trade Data API, enabling queries of monthly export and import statistics by HS, NAICS, end-use, and other classifications, with tools for trade balance, top partners, and country code lookup.
Updated 2 months ago (2026-09-03 07:31 UTC)
7
Creative Commons Zero v1.0 Universal
mcp-comex-brasil
Open Data Government Data Research & Data
PHIAI-IO
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.
Updated 24 days ago (2026-09-24 15:40 UTC)
4
-