# Yugalinks Commerce Intelligence (remote · www.yugalinks.com)

Read-only OECD trade research for countries, products, corridors, lane risk, and opportunities.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `www.yugalinks.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/nibinglobal-yugalinks-commerce/www.md), [page](https://verifymcp.io/servers/nibinglobal-yugalinks-commerce/www)

## Channel facts

- Endpoint: `https://www.yugalinks.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 904 tokens (~69/item across 13 items; 11 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 66% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Yugalinks Commerce Intelligence MCP server?

Yugalinks Commerce Intelligence is a hosted endpoint at https://www.yugalinks.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http nibinglobal-yugalinks-commerce 'https://www.yugalinks.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nibinglobal-yugalinks-commerce": {
      "url": "https://www.yugalinks.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nibinglobal-yugalinks-commerce": {
      "type": "http",
      "url": "https://www.yugalinks.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nibinglobal-yugalinks-commerce]
url = "https://www.yugalinks.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nibinglobal-yugalinks-commerce": {
      "type": "remote",
      "url": "https://www.yugalinks.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nibinglobal-yugalinks-commerce --url 'https://www.yugalinks.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nibinglobal-yugalinks-commerce:
    url: "https://www.yugalinks.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nibinglobal-yugalinks-commerce": {
      "Transport": "http",
      "Url": "https://www.yugalinks.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nibinglobal-yugalinks-commerce -t streamable-http -u 'https://www.yugalinks.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nibinglobal-yugalinks-commerce": {
      "type": "http",
      "url": "https://www.yugalinks.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-24 (score 78, +1)

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

### 2026-09-21 (score 77, +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-09-19 (score 76, +1)

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

### 2026-09-17 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-16 (score 74)

First indexed and scored.

## MCP tools (11)

### `lookup_countries` (~52 tokens)

Find country names and ISO3 codes used in Yugalinks commerce data.

Input parameters:

- `country_iso3`
- `limit` (integer): Maximum number of rows to return.
- `q`: Optional text filter.

### `lookup_products` (~61 tokens)

Find HS product codes and descriptions used in Yugalinks commerce data.

Input parameters:

- `hs_code`
- `limit` (integer): Maximum number of rows to return.
- `offset` (integer): Number of rows to skip.
- `q`: Optional text filter.

### `list_trade_datasets` (~23 tokens)

List every approved commerce-data dataset available through the public MCP surface.

### `search_trade_datasets` (~123 tokens)

Search selected approved commerce datasets without exposing storage details.

Input parameters:

- `country_iso3`
- `dataset_keys` (array, required): One to eight dataset keys returned by list_trade_datasets.
- `exporter_iso3`
- `hs_code`
- `importer_iso3`
- `limit` (integer): Maximum rows returned for each selected dataset.
- `offset` (integer): Number of rows to skip.
- `q`: Optional text filter.
- `scope`: Optional text filter.
- `year`: Reporting year from 1995 through 2024.

### `get_global_trade` (~59 tokens)

Return reported global merchandise-flow totals for a year.

Input parameters:

- `limit` (integer): Maximum number of rows to return.
- `offset` (integer): Number of rows to skip.
- `year`: Reporting year from 1995 through 2024.

### `get_country_trade` (~85 tokens)

Return reported yearly imports, exports, balance, and growth for a country.

Input parameters:

- `country_iso3` (string, required): Three-letter ISO country code, for example IND or DEU.
- `limit` (integer): Maximum number of rows to return.
- `offset` (integer): Number of rows to skip.
- `year`: Reporting year from 1995 through 2024.

### `get_product_trade` (~89 tokens)

Return reported yearly global merchandise flows and growth for an HS2, HS4, or HS6 product.

Input parameters:

- `hs_code` (string, required): HS2, HS4, or HS6 product code.
- `limit` (integer): Maximum number of rows to return.
- `offset` (integer): Number of rows to skip.
- `year`: Reporting year from 1995 through 2024.

### `get_corridor_trade` (~76 tokens)

Return reported yearly goods-flow values between exporter and importer countries.

Input parameters:

- `exporter_iso3`
- `importer_iso3`
- `limit` (integer): Maximum number of rows to return.
- `offset` (integer): Number of rows to skip.
- `year`: Reporting year from 1995 through 2024.

### `get_lane_risk` (~113 tokens)

Return reported lane-risk observations for country and product filters.

Input parameters:

- `attention_level`
- `current_only` (boolean)
- `exporter_iso3`
- `hs_chapter`: Two-digit HS chapter.
- `hs_code`
- `importer_iso3`
- `limit` (integer): Maximum number of rows to return.
- `min_trade_usd`
- `offset` (integer): Number of rows to skip.
- `q`: Optional text filter.
- `risk_driver`

### `get_export_opportunities` (~82 tokens)

Return bounded export-opportunity indicators for country and product filters.

Input parameters:

- `exporter_iso3`
- `hs_code`
- `importer_iso3`
- `limit` (integer): Maximum number of rows to return.
- `offset` (integer): Number of rows to skip.
- `year`: Reporting year from 1995 through 2024.

### `get_lane_page` (~80 tokens)

Read the public machine-readable page for one exporter-importer HS6 lane-risk record.

Input parameters:

- `exporter_iso3` (string, required): Three-letter ISO country code, for example IND or DEU.
- `hs_code` (string, required): Six-digit HS code.
- `importer_iso3` (string, required): Three-letter ISO country code, for example IND or DEU.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nibinglobal-yugalinks-commerce/www#diagnostics

## Score history

- 2026-09-24: 78
- 2026-09-23: 77
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74

## Common questions

### What is the Yugalinks Commerce Intelligence MCP server?

Yugalinks Commerce Intelligence is an MCP server listed in the public MCP registry as io.github.nibinglobal/yugalinks-commerce. Read-only OECD trade research for countries, products, corridors, lane risk, and opportunities. This page covers its hosted endpoint (https://www.yugalinks.com/mcp).

### Is the Yugalinks Commerce Intelligence MCP server safe to use?

Yugalinks Commerce Intelligence scores 78 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 Yugalinks Commerce Intelligence MCP server expose?

Yugalinks Commerce Intelligence exposes 11 tools: lookup_countries, lookup_products, list_trade_datasets, search_trade_datasets, get_global_trade, and 6 more. Their descriptions and schemas cost roughly 843 tokens of context every time the server is loaded.

### Does the Yugalinks Commerce Intelligence MCP server require authentication?

No. We connected to Yugalinks Commerce Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Yugalinks Commerce Intelligence MCP server still maintained?

Yugalinks Commerce Intelligence is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.yugalinks.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/nibinglobal-yugalinks-commerce/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/nibinglobal-yugalinks-commerce/www.json
- HTML version of this page: https://verifymcp.io/servers/nibinglobal-yugalinks-commerce/www