Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EU Trade Explorer

REMOTE · MCP.TRADEDASHBOARD.EU

EU customs-trade & industrial-production statistics (Eurostat Comext/PRODCOM)

0 this week 83 Trust /100

Last scanned (18 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

Trust breakdown (7 categories)

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 Security97
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability82
  • 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
  • Context-footprint check failed: tool/resource definitions use about 1346 tokens (~122/item across 11 items; 6 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management8
  • Stability check failed: schema churn in the 30 days we've observed: 34 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (83% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 0
    • Server version: 4.1.6 → 4.2.2 functional
  • 14 Nov 26 −9
    • A breaking change shipped without a version bump: still 4.1.6 ▼ security
    • Tool “get_autonomy_summary” was removed ▼ security
    • Tool “get_chapters” was removed ▼ security
    • Tool “get_concentration” was removed ▼ security
    • Tool “get_concentration_compare” was removed ▼ security
    • Tool “get_concentration_map” was removed ▼ security
    • Tool “get_countries” was removed ▼ security
    • Tool “get_customs_code_profile” was removed ▼ security
    • Tool “get_export_propensity” was removed ▼ security
    • Tool “get_full_report” was removed ▼ security
    • Tool “get_map_data” was removed ▼ security
    • Tool “get_market_structure_summary” was removed ▼ security
    • Tool “get_market_summary” was removed ▼ security
    • Tool “get_net_import_reliance” was removed ▼ security
    • Tool “get_partner_detail” was removed ▼ security
    • Tool “get_pattern_shift” was removed ▼ security
    • Tool “get_price_shocks” was removed ▼ security
    • Tool “get_production_concentration” was removed ▼ security
    • Tool “get_production_series” was removed ▼ security
    • Tool “get_reporter_benchmark” was removed ▼ security
    • Tool “get_reporter_detail” was removed ▼ security
    • Tool “get_specialisation” was removed ▼ security
    • Tool “get_subcode_compare” was removed ▼ security
    • Tool “get_subcontracting” was removed ▼ security
    • Tool “get_subcontracting_reporters” was removed ▼ security
    • Tool “get_subtree” was removed ▼ security
    • Tool “get_supply_shocks” was removed ▼ security
    • Tool “get_top_entities” was removed ▼ security
    • Tool “get_trade_intensity” was removed ▼ security
    • Tool “get_volatility” was removed ▼ security
    • Tool “get_volatility_summary” was removed ▼ security
    • Tool “guidelines_for_a_long_report” was removed ▼ security
    • Tool “guidelines_for_a_short_report” was removed ▼ security
    • Tool “search_customs_codes” was removed ▼ security
    • Tool “validate_customs_code” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 100% → 83% ▼ functional
    • Schema quality: 250 → 122 ▲ functional
    • Schema quality: excellent → good functional
    • New tool “call_tool” functional
    • New tool “search_tools” functional
  • 12 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +12
    • Stability: pass → fail ▼ security
    • Tool “get_product_compare” was removed ▼ security
    • Tool “get_product_profile” was removed ▼ security
    • Tool “get_subcontracting_members” was removed ▼ security
    • Tool “search_codes” was removed ▼ security
    • Tool “validate_code” was removed ▼ security
    • Authorization: unverified → pass ▲ security
    • First check of Authorization: partial security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_pattern_shift” rewrote its description, which is the text the model reads security
    • Tool “get_autonomy_summary” rewrote its description, which is the text the model reads security
    • Tool “get_concentration” rewrote its description, which is the text the model reads security
    • Tool “get_concentration_compare” rewrote its description, which is the text the model reads security
    • Tool “get_countries” rewrote its description, which is the text the model reads security
    • Tool “get_data_range” rewrote its description, which is the text the model reads security
    • Tool “get_full_report” rewrote its description, which is the text the model reads security
    • Tool “get_market_structure_summary” rewrote its description, which is the text the model reads security
    • Tool “get_market_summary” rewrote its description, which is the text the model reads security
    • Tool “get_net_import_reliance” rewrote its description, which is the text the model reads security
    • Tool “get_overview” rewrote its description, which is the text the model reads security
    • Tool “get_production_concentration” rewrote its description, which is the text the model reads security
    • Tool “get_production_series” rewrote its description, which is the text the model reads security
    • Tool “get_reporter_benchmark” rewrote its description, which is the text the model reads security
    • Tool “get_reporter_detail” rewrote its description, which is the text the model reads security
    • Tool “get_specialisation” rewrote its description, which is the text the model reads security
    • Tool “get_subcontracting” rewrote its description, which is the text the model reads security
    • Tool “get_subtree” rewrote its description, which is the text the model reads security
    • Tool “get_supply_shocks” rewrote its description, which is the text the model reads security
    • Tool “get_volatility” rewrote its description, which is the text the model reads security
    • Tool “get_volatility_summary” rewrote its description, which is the text the model reads security
    • Tool “resolve_product_code” rewrote its description, which is the text the model reads security
    • “get_subtree” added a required parameter “customs_code”, so existing callers break ▼ functional
    • “get_subtree” dropped the required parameter “code” ▼ functional
    • Schema quality: 277 → 249 ▲ functional
    • First check of Schema quality: 100 functional
    • MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
    • MCP protocol version: 2026-07-28 → 2025-11-25 functional
    • New resource “Customs-code selections” functional
    • New resource “PRODCOM interpretation” functional
    • New resource “Query model and access” functional
    • New resource “Report workflows” functional
    • New resource “Trade methodology” functional
    • Server version: 4.0.10 → 4.1.6 functional
    • New tool “get_customs_code_profile” functional
    • New tool “get_documentation” functional
    • New tool “get_subcode_compare” functional
    • New tool “get_subcontracting_reporters” functional
    • New tool “search_customs_codes” functional
    • New tool “validate_customs_code” functional
    • “get_data_range” added an optional parameter “customs_codes” cosmetic
    • “get_volatility” added an optional parameter “n_top_subcodes” cosmetic
    • “get_autonomy_summary” reworded the description of “query” cosmetic
    • “get_chapters” reworded the description of “lang” cosmetic
    • “get_concentration” reworded the description of “entity_level” cosmetic
    • “get_concentration” reworded the description of “query” cosmetic
    • “get_concentration_compare” reworded the description of “n_subcodes” cosmetic
    • “get_concentration_compare” reworded the description of “query” cosmetic
    • “get_concentration_map” reworded the description of “entity_level” cosmetic
    • “get_concentration_map” reworded the description of “query” cosmetic
    • “get_export_propensity” reworded the description of “query” cosmetic
    • “get_full_report” reworded the description of “query” cosmetic
    • “get_map_data” reworded the description of “query” cosmetic
    • “get_market_structure_summary” reworded the description of “query” cosmetic
    • “get_market_summary” reworded the description of “query” cosmetic
    • “get_net_import_reliance” reworded the description of “query” cosmetic
    • “get_overview” reworded the description of “query” cosmetic
    • “get_partner_detail” reworded the description of “query” cosmetic
    • “get_pattern_shift” reworded the description of “query” cosmetic
    • “get_price_shocks” reworded the description of “cumulative_share” cosmetic
    • “get_price_shocks” reworded the description of “entity_level” cosmetic
    • “get_price_shocks” reworded the description of “lookback_years” cosmetic
    • “get_price_shocks” reworded the description of “max_shocks_per_pair” cosmetic
    • “get_price_shocks” reworded the description of “min_abnormality” cosmetic
    • “get_price_shocks” reworded the description of “query” cosmetic
    • “get_production_concentration” reworded the description of “query” cosmetic
    • “get_production_series” reworded the description of “query” cosmetic
    • “get_reporter_benchmark” reworded the description of “query” cosmetic
    • “get_reporter_detail” reworded the description of “query” cosmetic
    • “get_specialisation” reworded the description of “query” cosmetic
    • “get_subcontracting” reworded the description of “query” cosmetic
    • “get_subtree” reworded the description of “lang” cosmetic
    • “get_supply_shocks” reworded the description of “cumulative_share” cosmetic
    • “get_supply_shocks” reworded the description of “entity_level” cosmetic
    • “get_supply_shocks” reworded the description of “max_tolerated_gap” cosmetic
    • “get_supply_shocks” reworded the description of “min_abnormality” cosmetic
    • “get_supply_shocks” reworded the description of “min_active_years” cosmetic
    • “get_supply_shocks” reworded the description of “query” cosmetic
    • “get_supply_shocks” reworded the description of “relative_threshold” cosmetic
    • “get_top_entities” reworded the description of “entity_level” cosmetic
    • “get_top_entities” reworded the description of “query” cosmetic
    • “get_trade_intensity” reworded the description of “query” cosmetic
    • “get_volatility” reworded the description of “entity_level” cosmetic
    • “get_volatility” reworded the description of “include_heatmap” cosmetic
    • “get_volatility” reworded the description of “indicator” cosmetic
    • “get_volatility” reworded the description of “query” cosmetic
    • “get_volatility_summary” reworded the description of “query” cosmetic
    • “resolve_product_code” reworded the description of “lang” cosmetic
    • “resolve_product_code” reworded the description of “query” cosmetic
    • “get_data_range” dropped the optional parameter “products” cosmetic
    • “get_full_report” dropped the optional parameter “lang” cosmetic
    • “get_volatility” dropped the optional parameter “n_top_products” cosmetic
  • 1 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “guidelines_for_a_short_report” rewrote its description, which is the text the model reads security
    • Server version: 4.0.0b3 → 4.0.10 functional
    • “get_concentration_map” reworded the description of “year” cosmetic
    • “get_reporter_benchmark” reworded the description of “year” cosmetic
    • “get_specialisation” reworded the description of “year” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.tradedashboard.eu/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.tradedashboard.eu CN=YE2,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA384 61cd9f6a6a5df2c7d7cc4945d5083e7aa72
SANs: mcp.tradedashboard.eu
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.tradedashboard.eu. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
eu. DS published 35926 8 Verified
tradedashboard.eu. DS published 44608 13 Verified
mcp.tradedashboard.eu. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.tradedashboard.eu/.well-known/oauth-protected-resource/mcp"

Bearer resource_metadata="https://mcp.tradedashboard.eu/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Protected resource metadata

Document https://mcp.tradedashboard.eu/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.tradedashboard.eu/mcp
Authorisation server https://tradedashboard.eu/

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.tradedashboard.eu/mcp Verified 200
http (plaintext) http://mcp.tradedashboard.eu/mcp HTTPS enforced 308 https://mcp.tradedashboard.eu/mcp
MCP tools · 6 exposed · ~930 tokens

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 →

Tool Tokens
call_tool ~53

Call a tool by name with the given arguments. Use this to execute tools discovered via search_tools.

NameTypeReqDescription
arguments––Arguments to pass to the tool
namestringyesThe name of the tool to call

No output schema declared.

No examples provided.

get_data_range ~80

Return the period coverage (`data_min`/`data_max`, 'YYYY-MM') actually cached for the given customs code(s) -- use before picking `period_start`/`period_end` so you don't request an empty window.

NameTypeReqDescription
customs_codes––Customs code(s) to check coverage for. Omit for the overall store range.
NameTypeReqDescription
resultobjectyesGET /api/reference/data-range — cached period coverage ('YYYY-MM').

No examples provided.

get_documentation ~121

Read one complete MCP guide: `query-model` (access, shared query fields, pieces and baskets), `customs-codes` (segments, residuals and historical selections), `prodcom` (production mappings, suppression and availability), `methodology` (indicator formulas and interpretation), or `reporting` (short/long workflows and dashboard navigation). The same canonical text is available as `eu-trade://docs/<topic>` resources.

NameTypeReqDescription
topicstringyesShort MCP guides with links to detailed website documentation.
NameTypeReqDescription
resultstringyes–

No examples provided.

get_overview ~281

Headline figures: total import/export quantities, values and weighted-average prices per period, the trade balance, and a top-partner breakdown. The best first call for any new customs-code/reporter slice. The figures sit under `total` / `partners` / `balance`, each panel carrying its own `periods` axis; the metadata (units, residual share, selection notes) is in `header`.

NameTypeReqDescription
compactboolean–If true, condense long numeric time series (more than ~6 points -- typically monthly/quarterly windows or wide multi-partner/multi-period breakdowns) into summary statistics (first, last, min, max, m…
queryobjectyesThe customs-code/reporter/partner-set/period/frequency slice to query -- the same request body every tradedashboard.eu analytical endpoint takes. See its own field descriptions (customs_code, baskets…
NameTypeReqDescription
result–yes–

No examples provided.

resolve_product_code ~350

Resolve a free-text query or CN code(s) into validated customs code(s) with descriptions -- the recommended first step before using a code as `customs_code` in any other tool's `query`. Saves the search -> validate -> (optional) subtree round-trip: a bare keyword runs a search, a single code (or comma-separated list) is validated and described directly. Tip: Comext/CN nomenclature is frequently coarser than a colloquial product name (e.g. there is no code for "glass jars" alone -- only heading 7010, which bundles jars with bottles, flasks and closures). Check `has_subcodes` and, if useful, set `include_children=true` to see whether a finer sub-code is actually a better match before committing to one code for a whole report. Returns `{mode, query, data}`: `data` is the typed validation or search response. A single-code validation also carries `subtree` when requested.

NameTypeReqDescription
include_childrenboolean–When resolving a single direct code, also fetch its immediate CN subtree so finer-grained alternatives are visible in one call.
langstring–Language for translated labels in the response; any other language is refused.
limitinteger–Max keyword-search results (ignored for direct code validation).
querystringyesFree-text keyword (e.g. 'glass jars') OR one or more CN codes, comma-separated (e.g. '7010' or '7010, 7013'), OR a single residual customs code (850440XX, 85SSS999, 85SSS).
NameTypeReqDescription
result–yes–

No examples provided.

search_tools ~45

Search for tools using natural language. Returns matching tool definitions ranked by relevance, in the same format as list_tools.

NameTypeReqDescription
querystringyesNatural language query to search for tools
NameTypeReqDescription
result–yes–

No examples provided.

Install

How do I install the EU Trade Explorer MCP server?

EU Trade Explorer is a hosted endpoint at https://mcp.tradedashboard.eu/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 · mcp.tradedashboard.eu

# add to Claude Code
claude mcp add --transport http eu-tradedashboard-eu-trade-explorer 'https://mcp.tradedashboard.eu/mcp'
Common questions

What is the EU Trade Explorer MCP server?

EU Trade Explorer is an MCP server listed in the public MCP registry as eu.tradedashboard/eu-trade-explorer. EU customs-trade & industrial-production statistics (Eurostat Comext/PRODCOM). This page covers its hosted endpoint (https://mcp.tradedashboard.eu/mcp).

Is the EU Trade Explorer MCP server safe to use?

EU Trade Explorer scores 83 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 EU Trade Explorer MCP server expose?

EU Trade Explorer exposes 6 tools: get_documentation, get_data_range, get_overview, resolve_product_code, search_tools, call_tool. Their descriptions and schemas cost roughly 930 tokens of context every time the server is loaded.

Does the EU Trade Explorer MCP server require authentication?

Yes. EU Trade Explorer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the EU Trade Explorer MCP server still maintained?

EU Trade Explorer 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 did VerifyMCP test on the EU Trade Explorer MCP server?

VerifyMCP ran 13 checks on EU Trade Explorer, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.