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.

Trade Evidence

REMOTE · STANDARDTRADE.AI

All 36,524 Canton Fair 2026 exhibitors: find factories, flag traders, MOQs, prices, US import rules.

Available components

+4 this week 74 Trust /100

Last scanned (19 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 4 Nov 2026.

Category E-commerce

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 Security74
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 641 tokens (~128/item across 5 items; 5 tools + 0 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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 27 Oct 26 +1
    • Tool “check_fit” changed its title: Check fit → Check paperwork fit cosmetic
    • Tool “get_exhibitors” changed its title: Get exhibitors → Get exhibitor profiles cosmetic
    • Tool “price_bands” changed its title: Price bands → Listed price bands cosmetic
    • Tool “search_listings” changed its title: Search listings → Search exhibitor listings cosmetic
    • Tool “us_requirements” changed its title: Us requirements → US import requirements cosmetic

    5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 24 Oct 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.

  • 22 Oct 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.

  • 20 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ 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 4 Nov 2026 · Probed https://standardtrade.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=standardtrade.ai CN=WE1,O=Google Trust Services,C=US 4 Oct 2026 2 Jan 2027 ECDSA 256 ECDSA-SHA256 425418b6b922da0d0e19d5e922ac4409
SANs: standardtrade.ai
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 standardtrade.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
standardtrade.ai. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://standardtrade.ai/mcp Verified 200
http (plaintext) http://standardtrade.ai/mcp HTTPS enforced 301 https://standardtrade.ai/mcp
MCP tools · 5 exposed · ~458 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
check_fit ~144

Who lists the paperwork each US rule for a product asks for. Checks every exhibitor selling the product (counts per rule), plus up to 10 named exhibitors and the others that list the most, in detail: which list a matching certificate, which only claim it in a product listing, which have only a foreign mark or a lab name; and which rules are the importer's own job. Spends one search.

NameTypeReqDescription
productstringyesProduct words, e.g. 'bamboo cutting board'
refsarray–Exhibitor refs (E1234) from search_listings to check in detail. Leave out to check the ones that list the most.

No output schema declared.

No examples provided.

get_exhibitors ~65

Full profiles for up to 5 exhibitors by ref (E1234): booths, self-declared type, founding year, certificates, staff, export markets, payment terms, and listings with prices and MOQs. Spends one search.

NameTypeReqDescription
refsarrayyes–

No output schema declared.

No examples provided.

price_bands ~54

Going prices for a product: median, middle half and median MOQ across all priced listings in matching fair categories, with the US import duty where known. Free; does not spend a search.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

search_listings ~131

Search exhibitors' product listings and profiles across the whole fair. Returns totals and the best-matching exhibitors with their matching listings. Use product words only (e.g. 'bamboo cutting board'). Optional filters apply to the exhibitors returned. Spends one search.

NameTypeReqDescription
certificatestring–A certificate the exhibitor must list, e.g. BSCI, FDA, LFGB, UL/ETL, OEKO-TEX, FSC
limitinteger––
phasestring–Fair phase
querystringyesProduct words only
typestring––

No output schema declared.

No examples provided.

us_requirements ~64

What a US seller must check before importing and selling a product: laws, marketplace (Amazon) rules and common buyer requests, each with its source and the certificate or test report a factory can show. Free; does not spend a search.

NameTypeReqDescription
productstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Trade Evidence MCP server?

Trade Evidence is a hosted endpoint at https://standardtrade.ai/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 · standardtrade.ai

# add to Claude Code
claude mcp add --transport http standard-trade-trade-evidence 'https://standardtrade.ai/mcp'
Common questions

What is the Trade Evidence MCP server?

Trade Evidence is an MCP server listed in the public MCP registry as io.github.Standard-Trade/trade-evidence. All 36,524 Canton Fair 2026 exhibitors: find factories, flag traders, MOQs, prices, US import rules. This page covers its hosted endpoint (https://standardtrade.ai/mcp).

Is the Trade Evidence MCP server safe to use?

Trade Evidence scores 74 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 Trade Evidence MCP server expose?

Trade Evidence exposes 5 tools: search_listings, get_exhibitors, price_bands, check_fit, us_requirements. Their descriptions and schemas cost roughly 458 tokens of context every time the server is loaded.

Does the Trade Evidence MCP server require authentication?

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

Is the Trade Evidence MCP server still maintained?

Trade Evidence is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.