Yugalinks Commerce Intelligence
REMOTE · WWW.YUGALINKS.COM · SCANNED SEP 24
Read-only OECD trade research for countries, products, corridors, lane risk, and opportunities.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 904 tokens (~69/item across 13 items; 11 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 66% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · www.yugalinks.com
claude mcp add --transport http nibinglobal-yugalinks-commerce 'https://www.yugalinks.com/mcp'
{
"mcpServers": {
"nibinglobal-yugalinks-commerce": {
"url": "https://www.yugalinks.com/mcp"
}
}
} {
"servers": {
"nibinglobal-yugalinks-commerce": {
"type": "http",
"url": "https://www.yugalinks.com/mcp"
}
}
} [mcp_servers.nibinglobal-yugalinks-commerce] url = "https://www.yugalinks.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nibinglobal-yugalinks-commerce": {
"type": "remote",
"url": "https://www.yugalinks.com/mcp",
"enabled": true
}
}
} openclaw mcp add nibinglobal-yugalinks-commerce --url 'https://www.yugalinks.com/mcp' --transport streamable-http
mcp_servers:
nibinglobal-yugalinks-commerce:
url: "https://www.yugalinks.com/mcp" {
"McpServers": {
"nibinglobal-yugalinks-commerce": {
"Transport": "http",
"Url": "https://www.yugalinks.com/mcp"
}
}
} assistant mcp add nibinglobal-yugalinks-commerce -t streamable-http -u 'https://www.yugalinks.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Sept 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://www.yugalinks.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yugalinks.com | CN=WE1,O=Google Trust Services,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 2a2e1232071f9b510e9734a022572fc8 |
| SANs: yugalinks.com, *.yugalinks.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.yugalinks.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| yugalinks.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.yugalinks.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.yugalinks.com/mcp | HTTPS enforced | 301 | https://www.yugalinks.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_corridor_trade ~76
Return reported yearly goods-flow values between exporter and importer countries.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
get_country_trade ~85
Return reported yearly imports, exports, balance, and growth for a country.
| Name | Type | Req | Description |
|---|---|---|---|
| country_iso3 | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
get_export_opportunities ~82
Return bounded export-opportunity indicators for country and product filters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
get_global_trade ~59
Return reported global merchandise-flow totals for a year.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of rows to return. |
| offset | integer | – | Number of rows to skip. |
| year | – | – | Reporting year from 1995 through 2024. |
Structured output declared, but exposes no named fields.
No examples provided.
get_lane_page ~80
Read the public machine-readable page for one exporter-importer HS6 lane-risk record.
| Name | Type | Req | Description |
|---|---|---|---|
| exporter_iso3 | string | yes | Three-letter ISO country code, for example IND or DEU. |
| hs_code | string | yes | Six-digit HS code. |
| importer_iso3 | string | yes | Three-letter ISO country code, for example IND or DEU. |
Structured output declared, but exposes no named fields.
No examples provided.
get_lane_risk ~113
Return reported lane-risk observations for country and product filters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_product_trade ~89
Return reported yearly global merchandise flows and growth for an HS2, HS4, or HS6 product.
| Name | Type | Req | Description |
|---|---|---|---|
| hs_code | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
list_trade_datasets ~23
List every approved commerce-data dataset available through the public MCP surface.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
lookup_countries ~52
Find country names and ISO3 codes used in Yugalinks commerce data.
| Name | Type | Req | Description |
|---|---|---|---|
| country_iso3 | – | – | – |
| limit | integer | – | Maximum number of rows to return. |
| q | – | – | Optional text filter. |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_products ~61
Find HS product codes and descriptions used in Yugalinks commerce data.
| Name | Type | Req | Description |
|---|---|---|---|
| hs_code | – | – | – |
| limit | integer | – | Maximum number of rows to return. |
| offset | integer | – | Number of rows to skip. |
| q | – | – | Optional text filter. |
Structured output declared, but exposes no named fields.
No examples provided.
search_trade_datasets ~123
Search selected approved commerce datasets without exposing storage details.
| Name | Type | Req | Description |
|---|---|---|---|
| country_iso3 | – | – | – |
| dataset_keys | array | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
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.