# io.github.CloudCorpRecords/comexscope (oci · ghcr.io/cloudcorprecords/comexscope)

Brazil foreign-trade data by HS code: exports, imports, partners, balances, climate, reports.

- Trust score: 41/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/comexscope`: 68/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-comexscope/reneturcios-comexscope.md), [page](https://verifymcp.io/servers/cloudcorprecords-comexscope/reneturcios-comexscope)
- oci · `ghcr.io/cloudcorprecords/comexscope`: 41/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-comexscope/ghcr-io-cloudcorprecords-comexscope.md), [page](https://verifymcp.io/servers/cloudcorprecords-comexscope/ghcr-io-cloudcorprecords-comexscope)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/comexscope`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4866 tokens (~324/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/comexscope MCP server?

io.github.CloudCorpRecords/comexscope runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/comexscope:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-comexscope -- docker run --rm -i ghcr.io/cloudcorprecords/comexscope:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-comexscope": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/comexscope:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-comexscope": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/comexscope:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-comexscope -- docker run --rm -i ghcr.io/cloudcorprecords/comexscope:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-comexscope": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/comexscope:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-comexscope:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/comexscope:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-comexscope": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/comexscope:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-comexscope": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/comexscope:0.1.0",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 39)

First indexed and scored.

## MCP tools (15)

### `kyrodata_compare_trade` (~497 tokens)

Compare exports/imports between equal windows

Compares Brazil's exports or imports between two equal-length windows (like-for-like), in value (USD FOB) and in volume (kg). `mode` changes the reading: quarterly, semestral, annual, ytd and rolling_3m/6m/12m look a year back and hold the season constant, while monthly and semestral_sequential compare against the period immediately before and cross one. `codes` and `countryIds` filter both windows alike and combine: together they isolate one product to one partner (1201 soybean to 160 China); omitted, every product and partner counts. The result carries both windows, the % change of each metric, the window label, whether it crosses a season, and the monthly series spanning both, capped at 24 months. This returns the FIGURES of a comparison — kyrodata_resolve_comparison_window only names the window, and kyrodata_list_trade_series hands over raw monthly points without comparing them. Credit class: comex (up to 2 comex tools per 60-second session = 1 credit).

Input parameters:

- `codes` (array): Products to filter by, as HS codes — 4 digits (heading), 6 (subheading) or 8 (Brazilian NCM), up to 10. Omit for every product. kyrodata_resolve_entity turns a product name into its code.
- `countryIds` (array): Partner countries to filter by, as ids from kyrodata_resolve_entity. Omit for every partner.
- `flow` (string, required): Direction of the trade flow, from Brazil’s side: `export` leaves the country, `import` enters it.
- `mode` (string, required): Which pair of equal-length windows to compare. Against the same period a year earlier: `quarterly`, `semestral`, `annual`, `ytd` (January to the last published month) and `rolling_3m`/`6m`/`12m`. Aga…
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_explain_pyramid_level` (~297 tokens)

Explain one level of the forecast pyramid

Explains the pyramid's arithmetic for one commodity and horizon: the seven levels side by side (label, push %, weight share, confidence, contribution %) and, for the levels that did not enter, the reason with its ruler (hit rate vs base rate, number of origins). `horizon` fixes the month and shows the seven levels; `levelKey` flips the cut, following one level across all four horizons instead. This is the drill-down of kyrodata_get_hub_summary — the 'por quê?' behind a verdict that tool already gave. A question about the physical harvest rather than the arithmetic belongs to kyrodata_get_climate_reading. Credit class: level (any level tool in a 60-second session = 2 credits; a session is capped at 3).

Input parameters:

- `horizon` (string, required): How far ahead the forecast looks: 1, 3, 6 or 12 months from the last published month.
- `hub` (string, required): Which commodity hub to read.
- `levelKey` (string): One level of the pyramid. Given, the answer follows that level across all four horizons instead of showing the seven side by side.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_fetch` (~277 tokens)

Open one public trade document by id

Opens ONE public foreign-trade document by id and returns it as prose to quote: title, body text and a public URL for citation. `id` is not free text — it is an id kyrodata_search returned, shaped `heading:1201` (an HS heading) or `country:160` (a partner country); anything else is refused rather than guessed. The body carries the measured figures of the latest published year, Brazilian exports and imports in USD FOB and kg, plus the window, the source and its caveats. Public government trade data only. The output here is a citable DOCUMENT with a URL, and this is the only tool that returns one. A heading as structured figures and a monthly series to reason over is kyrodata_get_heading_overview; free text to find an id in the first place is kyrodata_search. Credit class: comex (up to 2 comex tools per 60-second session = 1 credit).

Input parameters:

- `id` (string, required): Identifier of a document returned by kyrodata_search. Not a free-text query.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_get_climate_reading` (~342 tokens)

Climate reading and physical crop loss

Current climate reading for a commodity: risk level, the measured production shock in % of the harvest, and the projected physical loss in tonnes per horizon (1, 3, 6 and 12 months) with its range. `scope` sets the geographic cut — 'br' (the default) reads the country, 'region:SE' a macro-region (N, NE, CW, SE, S), 'uf:MG' a single state — and moves only the risk level and the shock: the loss in tonnes stays national at any scope. A commodity without a validated model returns a descriptive reading with no verdict, and a season not yet measurable returns the previous one, each flagged in the caveats. Climate here predicts PRODUCTION. The price question for the same hub is kyrodata_get_hub_summary, and the published season-by-season balance sheet is kyrodata_get_supply_demand_balance. Credit class: level (any level tool in a 60-second session = 2 credits; a session is capped at 3).

Input parameters:

- `hub` (string, required): Which commodity hub to read. Climate forecasts PRODUCTION, never price.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.
- `scope` (string): Geographic cut: `br` for the whole country, `region:<N|NE|CW|SE|S>` for a macro-region, or `uf:<XX>` for a state. Defaults to the country.

### `kyrodata_get_credit_balance` (~187 tokens)

Credit balance and limits for this key

Reports the credit balance and the limits of the API key making the request: credits left in the current cycle and when it resets, the daily credit and daily call ceilings of the key, and which tools the key reaches. `response_format` is the only input and it changes verbosity, not scope — there is no argument that selects another key, since the answer describes whichever key authenticated this call. It reads no market data, so it answers a question about the ACCOUNT, never about trade, climate or a commodity. A question about how far the data itself goes is kyrodata_get_data_coverage. Credit class: free (0 credits).

Input parameters:

- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_get_data_coverage` (~189 tokens)

Data coverage and latest closed month

Returns the calendar of the trade data: first and last published month (YYYYMM), whether the current year is partial, the last fully closed month, and when the aggregates were last refreshed. `response_format` is the only input; the answer covers the whole dataset, so there is no window or product to narrow it with. This answers 'até quando tem dado?' and 'qual o último mês?' — the CALENDAR, never figures. Turning that calendar into a like-for-like window is kyrodata_resolve_comparison_window; reading the figures inside it is kyrodata_get_heading_overview. Credit class: free (0 credits).

Input parameters:

- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_get_heading_overview` (~372 tokens)

Overview of an HS heading (SH4)

Structured read of ONE HS heading (SH4, 4 digits) for exports or imports: totals of the published year (USD FOB, kg), the last closed month against the previous one (average price per kg and volume), and a monthly price-by-volume series. `year` centres the overview and defaults to the most recent published year, with coverage starting in 2000; `months` sets only how far the series reaches back from the last published month, and leaves the totals untouched. A caveat states that US$/kg is an average unit value, not a quoted price. Public data. The output here is FIGURES and a series to reason over. The same heading as a citable document with a URL is kyrodata_fetch, and a comparison between two windows is kyrodata_compare_trade. Credit class: comex (up to 2 comex tools per 60-second session = 1 credit).

Input parameters:

- `flow` (string, required): Direction of the trade flow, from Brazil’s side: `export` leaves the country, `import` enters it.
- `months` (integer): Length of the monthly series returned, counting back from the last published month.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.
- `sh4` (string, required): The 4-digit HS heading to describe.
- `year` (integer): Calendar year of the TOTALS (USD FOB, kg). Omit for the most recent published year; coverage starts in 2000. The month-over-month figures and the price-by-volume series always describe the latest pub…

### `kyrodata_get_hub_summary` (~367 tokens)

Commodity hub summary and forecast verdict

Reads the Kyrodata pyramid verdict for a commodity hub: direction of the leading horizon, expected move in % per horizon (1, 3, 6 and 12 months), the 80% band as a half-width in percentage points, which levels drive the verdict and the measured accuracy. A horizon without an arrow names the reason, and an empty one means no level passed the confidence gate: no signal, not a stable price. `horizon` re-centres the verdict on the month given; omitted, it centres on the horizon the model leads with, and all four come back either way. It also carries the month-over-month and year-over-year % change of the reference price and its kind (doméstico, mundial or paridade de exportação), never the price level. This is the tool for where a hub's price is heading. The arithmetic behind the verdict is kyrodata_explain_pyramid_level, and the physical harvest of the same hub is kyrodata_get_climate_reading. Credit class: level (any level tool in a 60-second session = 2 credits; a session is capped at 3).

Input parameters:

- `horizon` (string): How far ahead the forecast looks: 1, 3, 6 or 12 months from the last published month. Omitted, the verdict centres on the horizon the model leads with; given, it re-centres on that one — either way a…
- `hub` (string, required): Which commodity hub to read.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_get_supply_demand_balance` (~281 tokens)

Supply and demand balance sheet

Published supply and demand balance (physical, in tonnes) for one agricultural hub, season by season: production, imports, exports, consumption, initial and final stock, whether the season is still an estimate, and how many months a partial season measures. `hub` accepts only the hubs that have a published balance sheet, which is fewer than the hubs the forecast tools cover; `closedOnly` drops the current season, which is a projection and still moves. The source is a Brazilian government body and is named in the result. This is the physical BALANCE of a season. The price verdict for the same hub is kyrodata_get_hub_summary, and the weather risk behind production is kyrodata_get_climate_reading. Credit class: level (any level tool in a 60-second session = 2 credits; a session is capped at 3).

Input parameters:

- `closedOnly` (boolean): Restrict to seasons already closed. The current season is a projection and still moves.
- `hub` (string, required): Which commodity hub to read. Only hubs with a published balance sheet appear here.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_list_trade_partners` (~466 tokens)

Top partner countries with growth

Ranks Brazil's partner countries for exports or imports, one row per country with value (USD FOB), volume (kg), price per kg and share of the window. `from`/`to` are YYYYMM and default to the last 12 published months; `codes` narrows to HS codes (4, 6 or 8 digits) so the ranking answers 'who buys THIS product'; `withGrowth` adds the last 12 months against the previous 12, which is the only way growth enters the answer. The country is the OUTPUT of this tool, so it takes no country filter — a question about one known country is a filter on kyrodata_compare_trade or kyrodata_list_trade_series instead. This ranks partners inside one window; comparing two windows is kyrodata_compare_trade. Credit class: comex (up to 2 comex tools per 60-second session = 1 credit).

Input parameters:

- `codes` (array): Products to filter by, as HS codes — 4 digits (heading), 6 (subheading) or 8 (Brazilian NCM), up to 10. Omit for every product. kyrodata_resolve_entity turns a product name into its code.
- `flow` (string, required): Direction of the trade flow, from Brazil’s side: `export` leaves the country, `import` enters it.
- `from` (integer): First month of the window, as YYYYMM (200403 = March 2004). Omit for the last twelve published months.
- `limit` (integer): How many partner countries to return, largest first by value.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.
- `to` (integer): Last month of the window, as YYYYMM. Omit for the last published month.
- `withGrowth` (boolean): Also return each partner’s growth: the twelve months ending at `to` against the twelve before them. It does NOT follow `from` — with a window of any other length, the ranking and the growth describe…

### `kyrodata_list_trade_series` (~428 tokens)

Raw monthly trade series as rows

Returns Brazil's monthly export or import series as rows — one row per month, with value (USD FOB), volume (kg) and the implied price per kg. `from`/`to` are YYYYMM and default to the last 24 published months; the span is capped at 200 months and a wider one is refused rather than silently truncated. A month with nothing published is ABSENT from the series rather than present as zero, so gaps stay visible instead of reading as collapse. `codes` and `countryIds` narrow the same series and can combine, which is how a single product-and-partner line is drawn. This hands over the POINTS. A question about them — two equal windows compared — is kyrodata_compare_trade, and a ranking of partners inside one window is kyrodata_list_trade_partners. Credit class: comex (up to 2 comex tools per 60-second session = 1 credit).

Input parameters:

- `codes` (array): Products to filter by, as HS codes — 4 digits (heading), 6 (subheading) or 8 (Brazilian NCM), up to 10. Omit for every product. kyrodata_resolve_entity turns a product name into its code.
- `countryIds` (array): Partner countries to filter by, as ids from kyrodata_resolve_entity. Omit for every partner.
- `flow` (string, required): Direction of the trade flow, from Brazil’s side: `export` leaves the country, `import` enters it.
- `from` (integer): First month of the window, as YYYYMM (200403 = March 2004). Omit for the last twenty-four published months.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.
- `to` (integer): Last month of the window, as YYYYMM. Omit for the last published month.

### `kyrodata_resolve_comparison_window` (~334 tokens)

Build a like-for-like comparison window

Resolves an equal-length comparison window (like-for-like) for the trade data, anchored on the last fully published month, and returns ONLY the window metadata — from, to, label, months and whether it crosses a season. No figures. `mode` splits into two families, and the split is what matters: quarterly, semestral, annual, ytd and rolling_3m/6m/12m compare against the same period a year earlier and hold the season constant, while monthly and semestral_sequential compare against the period immediately before and therefore cross one. `ytd` runs January to the last published month, in both years. This exists to NAME a window in prose before it is described. The same window resolved internally and answered with value and volume in one call is kyrodata_compare_trade. Credit class: free (0 credits).

Input parameters:

- `mode` (string, required): Which pair of equal-length windows to compare. Against the same period a year earlier: `quarterly`, `semestral`, `annual`, `ytd` (January to the last published month) and `rolling_3m`/`6m`/`12m`. Aga…
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_resolve_entity` (~273 tokens)

Resolve country, HS code or commodity

Resolves a free-text name into platform identifiers for FILTERING other tools: commodity hubs (slug plus anchor SH4), HS headings (SH4), NCM codes (8 digits) and partner countries (country id). 'soja' resolves to the soybean hub and SH4 1201; 'China' to country id 160. `query` takes a name already known rather than a topic to explore, and up to 10 matches per kind come back — an ambiguous term returns the candidates instead of one guess, so the caller picks. The output is an ID to pass to another tool, and it carries no document and no URL. Finding what exists in the public catalog, and getting a citable document back, is kyrodata_search. Credit class: free (0 credits).

Input parameters:

- `kinds` (array): Narrow the search to these kinds of entity. Omit to search all of them.
- `q` (string, required): What to look up, in plain words: a country, a product, or a code. Portuguese and English both work.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_run_report` (~339 tokens)

Run one of the catalog reports

Runs one of the product's pre-built catalogue reports by id and returns its rows, up to 50. `reportId` is an enum of the catalogue's ids, so the whole catalogue travels in this schema and no lookup call is needed; `params` carries the values the chosen report declares, and `columnIds` narrows the projection — omitted, the report's default columns come back, and the columns that identify each row are included either way. Columns locked behind a paid plan are declared, with a header stating what an upgrade unlocks, while their values stay out. Rows count against the account's export quota. This serves a report that already exists as a product. An ad-hoc question about trade is kyrodata_compare_trade or kyrodata_list_trade_series, and a citable public document is kyrodata_fetch. Credit class: comex (up to 2 comex tools per 60-second session = 1 credit).

Input parameters:

- `columnIds` (array): Only these columns, by id. Omit for the report’s default set; the columns that identify a row are always returned.
- `limit` (integer): Maximum rows to return.
- `params` (object): Values for the parameters the chosen report declares.
- `reportId` (string, required): Which catalogue report to run, by id. Each report declares its own parameters, which go in `params`.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

### `kyrodata_search` (~217 tokens)

Search the public trade catalog

Searches the public Brazilian foreign-trade catalogue and returns document ids for kyrodata_fetch — HS headings (SH4, 4 digits) and partner countries — each with a public URL. `query` is free text in Portuguese or a code, and both reach the same place: 'soja' and '1201' land on the soybean heading, 'China' on the partner country. This is DISCOVERY: it finds what exists when the caller has words rather than an id. Turning a name already known into an id for filtering another tool is kyrodata_resolve_entity, which returns no document and no URL. Credit class: free (0 credits).

Input parameters:

- `query` (string, required): What to look for, in plain words. Returns document ids to pass to kyrodata_fetch.
- `response_format` (string): How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-comexscope/ghcr-io-cloudcorprecords-comexscope#diagnostics

## Score history

- 2026-11-21: 41
- 2026-11-20: 41
- 2026-11-19: 40
- 2026-11-18: 40
- 2026-11-17: 40
- 2026-11-16: 39
- 2026-11-15: 39

## Common questions

### What is the io.github.CloudCorpRecords/comexscope MCP server?

io.github.CloudCorpRecords/comexscope is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/comexscope. Brazil foreign-trade data by HS code: exports, imports, partners, balances, climate, reports. This page covers its container image (ghcr.io/cloudcorprecords/comexscope).

### Is the io.github.CloudCorpRecords/comexscope MCP server safe to use?

io.github.CloudCorpRecords/comexscope scores 41 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.CloudCorpRecords/comexscope MCP server expose?

io.github.CloudCorpRecords/comexscope exposes 15 tools: kyrodata_compare_trade, kyrodata_explain_pyramid_level, kyrodata_fetch, kyrodata_get_climate_reading, kyrodata_get_credit_balance, and 10 more. Their descriptions and schemas cost roughly 4,866 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/comexscope MCP server still maintained?

io.github.CloudCorpRecords/comexscope is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/comexscope MCP server under?

io.github.CloudCorpRecords/comexscope declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/comexscope MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/comexscope, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/comexscope: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/comexscope
- Repository: https://github.com/CloudCorpRecords/comexscope
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-comexscope/ghcr-io-cloudcorprecords-comexscope.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-comexscope/ghcr-io-cloudcorprecords-comexscope/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-comexscope/ghcr-io-cloudcorprecords-comexscope.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-comexscope/ghcr-io-cloudcorprecords-comexscope
