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.

China Trade & Market Data

REMOTE · MCP.AGENTDATACORE.COM

Look up investment statistics by year or country and region.

−78 this week 0 Trust /100

Last scanned (28 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 17 Oct 2026.

Category Finance and Payments

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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.

  • 24 Oct 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 23 Oct 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 22 Oct 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 21 Oct 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 20 Oct 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 18 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HTTPS: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

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

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 24 Oct 2026 · Probed https://mcp.agentdatacore.com/mcp/products/trade

TLS unreached
DNSSEC insecure

Validation of mcp.agentdatacore.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
agentdatacore.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.agentdatacore.com/mcp/products/trade Unreachable
http (plaintext) http://mcp.agentdatacore.com/mcp/products/trade HTTPS enforced
MCP tools · 5 exposed · ~1,578 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
get_customs_commodity_trade ~404

Query China import or export observations by recorded major-commodity label. Inputs: period, commodity, flow and optional metric. Selected exact Chinese aliases and normalized existing names are supported; this is not general translation or HS-code classification. Returns trade_value or quantity observations with original commodity labels, units, scope, source_class, provenance, snapshot, pagination and limits. No category merging or conversion. No match returns an empty data array. Required: period, commodity, flow. Missing required or invalid input produces an argument error.

NameTypeReqDescription
commoditystringyesRecorded major-commodity name or a selected exact Chinese alias. Existing literal substring matching remains; known aliases resolve only to their exact canonical label. NFKC, leading/trailing spaces…
flowstringyesChina trade direction: IMPORT or EXPORT. Required.
limitinteger–Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
metricstring–Recorded metric trade_value or quantity. trade_value currently uses 1000USD; quantity units vary by commodity and are returned unchanged. Optional; omission includes both collected metrics.
offsetinteger–Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
periodstringyesRecorded statistical period: YYYY-MM for a single month, or YYYY-01/YYYY-MM for January-to-month cumulative observations. Exact collected period; these periods are not interchangeable. A snapshot ide…
snapshotstring–Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

No output schema declared.

No examples provided.

get_customs_country_trade ~353

Query China merchandise trade by partner country/region, including all-partner totals using country TOTAL. Inputs: period, country and optional flow. IMPORT and EXPORT are China imports and exports; BOTH is recorded combined trade. Returns recorded trade values and units (currently 1000USD), scope, source_class, provenance, snapshot, pagination and limits. No commodity filter or currency conversion. No match returns an empty data array. Required: period, country. Missing required or invalid input produces an argument error.

NameTypeReqDescription
countrystringyesChina trade partner country/region, or TOTAL for all partners. TOTAL is an aggregate, not an alias for China. Exact recorded name or selected one-to-one alias; original labels remain in output. Requi…
flowstring–China trade direction: IMPORT or EXPORT or BOTH (recorded combined total). Optional; omission includes collected directions.
limitinteger–Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
offsetinteger–Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
periodstringyesRecorded statistical period: YYYY-MM for a single month, or YYYY-01/YYYY-MM for January-to-month cumulative observations. Exact collected period; these periods are not interchangeable. A snapshot ide…
snapshotstring–Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

No output schema declared.

No examples provided.

get_foreign_investment_stats ~365

Find foreign-investment observations for a statistical year, optionally filtered by country or measure. Inputs: year, country, metric. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: year. Missing required or invalid input produces an argument error.

NameTypeReqDescription
countrystring–Country or region label exactly as recorded; no country-code or alias conversion. Exact match. Non-empty string, at most 256 characters; control characters are not accepted. Optional; omitted means n…
limitinteger–Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
metricstring–Statistical measure label exactly as recorded; no unit conversion or aggregation. Exact match. Non-empty string, at most 256 characters; control characters are not accepted. Optional; omitted means n…
offsetinteger–Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
snapshotstring–Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…
yearintegeryesRecorded statistical year as an integer; this is not the publication year. Exact match. Non-negative integer within the server integer range. Required. Supplied filters are combined with AND.

No output schema declared.

No examples provided.

get_information_standard ~42

Retrieve definitions of information formation classes, provenance fields and snapshot/version metadata. Takes no arguments. Returns the information-standard document, not business records or an assessment of facts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_mofcom_trade_stats ~414

Query collected country-workbook trade observations (flows relative to the named reporting country) or China–Portuguese-speaking-country bilateral year-to-date observations. Inputs: period and optional country, flow and metric. This collection is not China national all-partner monthly totals. Returns original structured observations, units, scope, source_class, provenance, snapshot, pagination and limits. No conversion, aggregation or cross-period calculation. No match returns an empty data array. Required: period. Missing required or invalid input produces an argument error.

NameTypeReqDescription
countrystring–Reporting country in country workbooks, or China bilateral partner in Portuguese-speaking-country observations; returned scope distinguishes them. Exact recorded name or a documented one-to-one alias…
flowstring–Flow relative to the named reporting country for COUNTRY_WORKBOOK_AS_REPORTED; China flow relative to the named partner for CHINA_PORTUGUESE_COUNTRIES_YTD. Recorded values IMPORT, EXPORT or BOTH; sco…
limitinteger–Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
metricstring–Recorded metric trade_value; country workbook unit is 亿美元, China–Portuguese-speaking-partner unit is 万美元. No unit conversion. Optional.
offsetinteger–Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
periodstringyesRecorded statistical period: YYYY-MM for a single month, or YYYY-01/YYYY-MM for January-to-month cumulative observations. Exact collected period; these periods are not interchangeable. A snapshot ide…
snapshotstring–Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

No output schema declared.

No examples provided.

Install

How do I install the China Trade & Market Data MCP server?

China Trade & Market Data is a hosted endpoint at https://mcp.agentdatacore.com/mcp/products/trade, 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.agentdatacore.com

# add to Claude Code
claude mcp add --transport http huangjunsong404-crypto-china-trade-market-data 'https://mcp.agentdatacore.com/mcp/products/trade'
Common questions

What is the China Trade & Market Data MCP server?

China Trade & Market Data is an MCP server listed in the public MCP registry as io.github.huangjunsong404-crypto/china-trade-market-data. Look up investment statistics by year or country and region. This page covers its hosted endpoint (https://mcp.agentdatacore.com/mcp/products/trade).

Is the China Trade & Market Data MCP server safe to use?

China Trade & Market Data scores 0 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 China Trade & Market Data MCP server expose?

China Trade & Market Data exposes 5 tools: get_foreign_investment_stats, get_mofcom_trade_stats, get_customs_country_trade, get_customs_commodity_trade, get_information_standard. Their descriptions and schemas cost roughly 1,578 tokens of context every time the server is loaded.

Does the China Trade & Market Data MCP server require authentication?

Its publisher declares no required credentials for China Trade & Market Data. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the China Trade & Market Data MCP server still maintained?

China Trade & Market Data has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 17 October 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 China Trade & Market Data MCP server?

VerifyMCP ran 3 checks on China Trade & Market Data, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about China Trade & Market Data: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.