TradeGraph
REMOTE · TRADEGRAPH.RINDA.AI
An export sales team for consumer brands, inside your AI: markets, buyers, emails and pricing.
Available components
Last scanned (9 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Usability69
- 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 12109 tokens (~712/item across 17 items; 16 tools + 1 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “gtm_plan” rewrote its description, which is the text the model reads security
- Tool “market_picks” rewrote its description, which is the text the model reads security
- Schema quality: 646 → 712 ▼ functional
- Server version: 1.8.0 → 1.9.0 functional
- “gtm_plan” added an optional parameter “concepts” cosmetic
- “gtm_plan” added an optional parameter “price_tier” cosmetic
- “gtm_plan” added an optional parameter “selling_in” cosmetic
- “market_picks” added an optional parameter “concepts” cosmetic
- “market_picks” added an optional parameter “description” cosmetic
- “market_picks” added an optional parameter “price_tier” cosmetic
- “market_picks” added an optional parameter “selling_in” cosmetic
- “market_picks” added an optional parameter “traits” cosmetic
- “reply_pace” added an optional parameter “concepts” cosmetic
- “reply_pace” added an optional parameter “description” cosmetic
- “reply_pace” added an optional parameter “price_tier” cosmetic
- “reply_pace” added an optional parameter “selling_in” cosmetic
- “blind_spots” reworded the description of “description” cosmetic
- “channel_plan” reworded the description of “description” cosmetic
- “country_brief” reworded the description of “description” cosmetic
- “gtm_plan” reworded the description of “description” cosmetic
- “image_studio” reworded the description of “description” cosmetic
- “video_studio” reworded the description of “description” cosmetic
- 4 Nov 26 0
- Resource “plan-card” now points somewhere else: ui://tradegraph/plan-card-10e70078.html → ui://tradegraph/plan-card-da82b6d3.html security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “image_studio” rewrote its description, which is the text the model reads security
- Tool “video_studio” rewrote its description, which is the text the model reads security
- Server version: 1.7.0 → 1.8.0 functional
- “image_studio” added an optional parameter “copy” cosmetic
- “image_studio” added an optional parameter “description” cosmetic
- “image_studio” added an optional parameter “traits” cosmetic
- “video_studio” added an optional parameter “copy” cosmetic
- “video_studio” added an optional parameter “description” cosmetic
- “video_studio” added an optional parameter “traits” cosmetic
- 3 Nov 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.
- 2 Nov 26 0
- Resource “plan-card” now points somewhere else: ui://tradegraph/plan-card-18265f1b.html → ui://tradegraph/plan-card-10e70078.html security
- The server rewrote its instructions, which are the text every model session reads security
- 31 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “blind_spots” rewrote its description, which is the text the model reads security
- Tool “country_brief” rewrote its description, which is the text the model reads security
- Tool “gtm_plan” rewrote its description, which is the text the model reads security
- Tool “price_ladder” rewrote its description, which is the text the model reads security
- Tool “reply_pace” rewrote its description, which is the text the model reads security
- Schema quality: 8413 → 10100 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- New resource “plan-card” functional
- Server version: 1.5.0 → 1.7.0 functional
- New tool “export_workflow” functional
- “gtm_plan” added an optional parameter “strengths” cosmetic
- “price_ladder” added an optional parameter “fob_krw” cosmetic
- “reply_pace” added an optional parameter “bounced” cosmetic
- “reply_pace” added an optional parameter “last_replies” cosmetic
- “reply_pace” added an optional parameter “last_sent” cosmetic
- “reply_pace” added an optional parameter “meetings” cosmetic
- “reply_pace” added an optional parameter “opened” cosmetic
- “reply_pace” added an optional parameter “orders” cosmetic
- “reply_pace” added an optional parameter “quotes” cosmetic
- “reply_pace” added an optional parameter “samples” cosmetic
- “blind_spots” reworded the description of “traits” cosmetic
- “channel_plan” reworded the description of “traits” cosmetic
- “country_brief” reworded the description of “traits” cosmetic
- “gtm_plan” reworded the description of “traits” cosmetic
- “price_ladder” reworded the description of “fob_usd” cosmetic
- 29 Oct 26 73
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 5 Nov 2026 · Probed https://tradegraph.rinda.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rinda.ai | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 951b22dd47e8263e0ed506a0c584d789 |
| SANs: rinda.ai, *.rinda.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 tradegraph.rinda.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| rinda.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| 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://tradegraph.rinda.ai/mcp | Verified | 200 | |
| http (plaintext) | http://tradegraph.rinda.ai/mcp | HTTPS enforced | 301 | https://tradegraph.rinda.ai/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 →
blind_spots What exporters miss: blockers, approvals, extra duties ~906
What a Korean exporter of this product is likely to miss in a market — the unknown unknowns beyond the product category's usual compliance: rules that can stop the sale (e.g. UV filters not allowed in US sunscreen, meat ingredients from countries the EU has not listed), approvals needed before import or sale (radio certification such as FCC, EU RED, Japan's Giteki or Canada's ISED; India BIS; registration of special-use cosmetics in China), extra duties or charges that change the quote (US Section 232 on steel and aluminium content, EU CBAM), and filings or labels (EU deforestation due diligence, producer registration (EPR) for batteries and electronics, and packaging EPR such as Germany's LUCID register in packaging_epr, EU ban on generic green claims), plus Korea-side checks (strategic items, dangerous goods in shipping). Each rule is triggered by the exact HS code or a product trait (pass description or traits) and comes with kind, gate (true = clear it before anything else: the plan's before-you-sell gate), who must act (you or the importer), the date it applies from (upcoming rules too), the official source and the date it was checked; stale marks rules not re-checked for 180 days. The category compliance pointer and its official source are included per market. Each market also says how much TradeGraph knows there (rules_coverage: national, bloc, pointers or none, where none is not a clearance and how_to_check lists where to look); where it has no rule note, rule_pointers gives official-source starting points for blocs and countries such as the EAEU (Kazakhstan, Russia, Belarus, Armenia, Kyrgyzstan), the Andean Community, Mexico, Chile, Argentina, Türkiye, Egypt, Israel, South Africa, Nigeria, Kenya, Pakistan, Bangladesh, New Zealand, Uzbekistan and Mongolia, gate marking what must be met before import or sale. Omit country to check every market in the plan's table. Starting points, not legal advice. Free, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Target country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. Optional: omit to check the markets of the plan's table. |
| description | string | – | Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the ru… |
| item | string | yes | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
| product | string | – | Optional: the product's own name in English (e.g. 'vegan sunscreen'). |
| traits | string | – | Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), co… |
No output schema declared.
No examples provided.
buyer_targets Who replies: country × buyer type ~170
Reply rates of country × buyer type (importer, distributor, wholesaler, retailer, brand, manufacturer, clinic) from 2.2M real export emails, shrunk toward the average so small samples do not mislead, ranked by the low end of the 90% interval. 'proven' = beats the average even with bad luck; 'promising' = too few contacts to be sure but could reach 2× average.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_type | string | – | Optional buyer type filter. |
| country | string | – | Target country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. Optional. |
| limit | integer | – | Rows to return. |
| tier | string | – | Which confidence tiers to return. |
No output schema declared.
No examples provided.
channel_plan Channels, creators and live-data calls for a country ~579
GTM engineering plan for one country: creator platforms to seed on, marketplaces to research, buyer channels, local-language and disclosure rules, product compliance pointers (with an official source link), the official tariff lookup and Korea FTA, and the treg.to endpoint ids (with per-call prices and example request bodies) to run creator discovery, vetting, marketplace research, social listening, ad-library and buyer-contact steps. Estimated data cost included.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Target country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. |
| description | string | – | Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the ru… |
| item | string | – | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
| motion | string | – | Which part of the plan to return. 'all' adapts to the item: industrial goods get b2b, trade and search only. |
| traits | string | – | Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), co… |
No output schema declared.
No examples provided.
country_brief Market brief for one country ~533
Everything TradeGraph knows about one country: reply rate and best buyer types, the product's import size/growth/Korea share and supplier mix, why other Korean exporters chose it, reply rates by industry, top US states (for the US), and the sales/creator channels and disclosure rules to use there. With item, rules_coverage and rule_pointers say what rules TradeGraph holds for the product there.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Target country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. |
| description | string | – | Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the ru… |
| item | string | – | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
| traits | string | – | Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), co… |
No output schema declared.
No examples provided.
export_rank World export ranking for a product ~125
World exporters of a product (UN Comtrade, latest year), Korea's rank and value, and where Korea already sells it most.
| Name | Type | Req | Description |
|---|---|---|---|
| item | string | yes | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
No output schema declared.
No examples provided.
export_workflow Step-by-step export workflows (certification, FTA origin, documents, payment, buyer checks …) ~434
36 step-by-step expert workflows for the export jobs around the data — what exporters usually learn too late: export readiness check (blind spots, 90-day plan), certification and registration in each market (FDA, MoCRA, CPNP, NMPA, halal, CE, PSE …) and in whose name, labels, HS code, regulation watch, export control and sanctions screening, FTA origin and certificates of origin, export documents (PI, CI, packing list, L/C), logistics, Incoterms, samples and dangerous goods, pricing and quotes, payment terms, L/C and export credit insurance, duty drawback and zero-rated VAT, Korean export support programs (vouchers, certification and trade-show subsidies) and grant applications, buyer due diligence and fraud checks (changed bank details), trademarks, distribution agreements, claims and unpaid invoices, trade shows, buyer outreach, reply triage, sales kits, influencer seeding, marketplaces, cross-border e-commerce and creative. Call with job (what the user asked, in their words and language) to get the best-matching workflow in full plus the next matches; with name for a known one; with neither to list them all by stage. Follow the steps in order: each names the TradeGraph tools to call (gtm_plan, blind_spots, price_ladder …) and the official sources to check. The same text as TradeGraph's Agent Skills and Claude Code plugin. Free, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Optional, with name: a reference file the workflow mentions, e.g. 'references/sources.md'. |
| job | string | – | What the user wants done, in their own words and any language (e.g. '이 바이어 믿어도 돼? 입금 계좌가 바뀌었대', 'the US buyer wants an FTA certificate of origin', 'first export, what are we missing?'). Returns the b… |
| name | string | – | A workflow name (from the list, or a name a TradeGraph answer mentions such as certification-check). |
No output schema declared.
No examples provided.
find_item Find a product's HS code ~239
Resolve a product description (any of 10 languages, e.g. 'vegan sunscreen', '컵라면', 'kimchi', 'キムチ', '3304') to one of the 35 HS4 items TradeGraph covers, or to the usual HS4 code of ~60 other common consumer products (kimchi 2005, shampoo 3305, candy 1704, ginseng roots 1211, ginseng extract 1302…) that gtm_plan and market_scan take with live UN Comtrade data. Ingredient words alone (ginseng, vitamin, collagen) do not decide the item: 'ginseng cream' is cosmetics 3304, 'ginseng shampoo' hair care 3305. For ginseng the answer adds hs_by_form (roots, extract, mixed preparations, drinks); for electric beauty devices it adds hs_by_form too (LED masks and microcurrent 8543.70, vibrating massagers 9019.10, hair stylers 8516). Use before other tools when unsure of the HS code.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Product name, alias or HS digits. |
No output schema declared.
No examples provided.
gtm_plan Export GTM plan for a product ~1,857
START HERE. One call returns the export go-to-market plan for a product: which countries to sell to (UN Comtrade imports × reply rates from 2.2M real export emails, compared within the product's industry, plus the next-best markets to compare), which buyer types reply there, how many follow-ups to send, the channels (creator seeding and marketplaces for consumer goods; buyer lists and trade shows for industrial goods; see motion), compliance flags with an official source link (compliance_gate marks approvals that block the market until they pass; channel_plan.packaging adds EU packaging EPR), a before_you_sell checklist (sanctions, FTA and proof of origin, trademark, payment terms, holidays, re-export hubs), the official tariff lookup (tariff_by_market compares the markets side by side), data_first (where the data would start even when you pass a country), gated_markets (compared markets with such a gate), banned_markets (those of them closed outright by an ingredient ban, such as ingredients of human origin: no approval opens them, so data_first, the market the data picks and next_markets skip them), next_markets (where to move at week 13, by the same rule as data_first, skipping gated markets and exclude), English email drafts (first email, follow-ups, week-3 sample check-in, and quote_reply_email for when a buyer asks for a price first; for Japan the same drafts in Japanese as local_emails, first_email_variants included; offers TradeGraph cannot know you make are marked [CONFIRM: ...] unless you pass strengths, and first_email.localize gives the register, greeting and closing for translating to the market's language), reply_target (expected replies from the product's own industry in that market, sends for 10 replies, the week-13 rule; reply_pace checks your numbers against it each week), a 13-week schedule, buyer_sources (trade fairs with the next edition's dates, city and book_meetings_from, 6 weeks before; BuyKOREA, KOTRA), and the exact treg.to endpoints (ids…
| Name | Type | Req | Description |
|---|---|---|---|
| concepts | string | – | Optional: product concepts, comma-separated: halal, vegan, derma, men, kids, organic (premium or mass also set price_tier); halal_certified when the product holds a halal certificate. Also detected f… |
| country | string | – | Target country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. Optional: omit to let the data pick the market. |
| description | string | – | Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the ru… |
| detail | string | – | Optional: brief (about half the size, for chat clients with a result size limit) or full (default, every draft). |
| exclude | string | – | Optional: markets already tried, comma-separated ISO codes or names (e.g. 'DE,PL'); next_markets skips them. |
| item | string | yes | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
| origin | string | – | Optional: where the product is made, ISO alpha-2 (default KR, or the signed-in company's origin). TradeGraph's reply data comes from Korean exporters: another origin is left out of the markets and or… |
| price_tier | string | – | Optional: the product's price tier, for market fit (premium favours high-income markets). |
| product | string | – | Optional: the product's own name in English for the first-email draft (e.g. 'kimchi', 'sunscreen'), up to 60 characters. Defaults to the item name; for a live HS code without it the draft says 'produ… |
| product_local | string | – | Optional, Japan: the product's name in Japanese for the Japanese drafts (local_emails), e.g. 'カシミヤ混ニット'. A product written in Japanese is used there too. |
| selling_in | string | – | Optional: markets where the product already sells (ISO codes or names, e.g. 'US,JP'), from marketplaces or distributors. They become expansion paths ahead of new markets (entry_paths path expand). Al… |
| strengths | string | – | Optional: what your company actually offers partners, in English and your own words, up to 240 characters (e.g. 'CE and ISO 9001, 4-week lead time, MOQ 50 units, spare parts stocked in Germany'). The… |
| traits | string | – | Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), co… |
No output schema declared.
No examples provided.
image_studio Marketplace and ad images for a market ~698
Plan the product image set for one market: the marketplace's main-image rules (Amazon, Rakuten, Tmall, Shopee, TikTok Shop…), a 7-image gallery (real main image, local lifestyle, texture, how-to, benefits infographic, scale, trust) with edit-from-packshot prompts for treg.to image models, ad sizes per platform, AI and claims rules, and the estimated cost. Like video_studio it puts the market's sale gates (sale_gate), the rules that bind ads and listings (ad_rules) and wording to change (claims_check) first, and signed in it builds the trust image from the certifications the company actually holds there. Free, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| copy | string | – | Optional: your own ad copy, captions, voice-over script or listing text for this market; claims_check flags wording that does not fit the market's rules and says what to use instead. |
| country | string | yes | Target country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. |
| description | string | – | Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the ru… |
| item | string | – | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
| marketplace | string | – | Optional marketplace, e.g. 'amazon', 'rakuten', 'shopee'; defaults to the market's main one. |
| product | string | – | The product in plain English as it looks. |
| traits | string | – | Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), co… |
| variants | integer | – | Generated variants per frame. |
No output schema declared.
No examples provided.
live_tools Find live-data endpoints for a job ~163
Search the treg.to catalog (3,800+ endpoints across 110 providers) for the endpoints that do a job, e.g. 'find TikTok beauty creators', 'Amazon best sellers', 'verify buyer emails', '샤오홍슈 KOL 단가'. Returns endpoint ids, providers and per-call prices. Execute them with live_call when connected with a TradeGraph account (charged to its prepaid credits), or with the treg MCP server (https://treg.to/mcp/, tool `call`) / `treg call <id>` using the user's own treg token. Without an account TradeGraph never spends money.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | yes | What you want to do, in English or Korean. |
| limit | integer | – | Endpoints to return. |
No output schema declared.
No examples provided.
market_picks Where to sell a product ~725
Import markets for a product ranked by size, with 3-year growth, Korea's share and the reply rate Korean exporters of that industry actually got there (reply_scope: industry = compared with the industry's average; none = no emails from that industry yet, so not ranked). 'pick' marks the Pareto frontier: no other market is both bigger and replies better. entry_paths ranks the markets for this product and company with the same rule as gtm_plan (pass description, concepts, price_tier, selling_in). Korea (domestic) and sanctioned markets are excluded from picks; regional_hub flags re-export hubs whose imports overstate local demand.
| Name | Type | Req | Description |
|---|---|---|---|
| concepts | string | – | Optional: product concepts, comma-separated: halal, vegan, derma, men, kids, organic (premium or mass also set price_tier); halal_certified when the product holds a halal certificate. Also detected f… |
| description | string | – | Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the ru… |
| item | string | yes | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
| limit | integer | – | Markets to return. |
| price_tier | string | – | Optional: the product's price tier, for market fit (premium favours high-income markets). |
| selling_in | string | – | Optional: markets where the product already sells (ISO codes or names, e.g. 'US,JP'), from marketplaces or distributors. They become expansion paths ahead of new markets (entry_paths path expand). Al… |
| traits | string | – | Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), co… |
No output schema declared.
No examples provided.
market_scan Live import markets for any HS code ~169
For products outside TradeGraph's 35 items: live UN Comtrade imports by country for any 4-digit HS code (latest complete year, 3-year growth, Korea's exports there), joined with TradeGraph reply rates for the product's industry, with Pareto picks. gtm_plan accepts the same HS code for a full plan. Free, read-only; the first call for a code takes a few seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| hs | string | yes | 4-digit HS code, e.g. '1905' (biscuits, snacks), '2005' (kimchi), '1904' (instant rice), '2206' (makgeolli), '3305' (shampoo), '3303' (perfume). |
| limit | integer | – | Markets to return. |
No output schema declared.
No examples provided.
outreach_playbook How many emails, when, and what replies say ~90
Measured from 2.2M real export emails: replies per 10,000 emails at each follow-up step, the recommended number of emails, how many days to wait before the next one (follow_up_after_days), when replies arrive, what replies say (interest, questions, meeting requests…), and the funnel per 10,000 emails. Use to set a sequence's length and timing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price_ladder Export price ladder: FOB to shelf price ~1,748
Turn a FOB unit price into the landed cost, importer/distributor price and shelf price (incl. VAT) in a country — or, from a target shelf price, the highest FOB that reaches it. Channels: retail (importer-distributor → retailer), distributor (importer → distributor → retailer), marketplace (importer of record selling on a marketplace), cross_border (Japan only: you ship each order from Korea to the consumer, e.g. as a Qoo10 or Rakuten overseas seller; no importer, and no duty or import consumption tax while a parcel's customs value is ¥10,000 or less, 60% of the retail price for personal-use goods; cross_border says whether the price stays under that limit, flags goods Japan never exempts (knitwear, leather shoes, some leather bags and gloves, ski boots and sugars: excluded, excluded_some) and liquor or tobacco tax (excise), and what changes from 1 Apr 2028: items priced ¥10,000 or less before tax carry Japanese consumption tax paid by the seller or a designated marketplace (small_item, price_with_tax_jpy), and with the 60% rule gone dearer items pay duty and tax on delivery), b2b (importer-distributor → business end user such as a clinic or factory; the default for equipment, parts and medical devices) and b2b_dealer (importer → dealer → business end user). The b2b channels stop at the end-user price before VAT (price_point 'end_user'; shelf_usd then holds that price), because business buyers usually reclaim VAT. Uses standard VAT and food rates, Korea FTA status and typical margins by product group; duty defaults to the rate TradeGraph has checked where it has one (US Section 301 and its exceptions: us_duty; Japan's RCEP or general rate for seaweed, clothing, bags and shoes: jp_duty; Mexico's general tariff, as Korea has no FTA there, raised on 1 Jan 2026 for cosmetics, toys, bags and clothing: mx_duty), otherwise 0% with a note to look it up. compare lays the same FOB side by side in other markets, each with its own duty and VAT (compare 'auto' picks the item's…
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Route to the consumer or, for goods sold to businesses, to the end user. Default: retail, or b2b when the item is sold to businesses. cross_border is for Japan only. |
| compare | string | – | Optional: other markets to price the same FOB and channel in, each with its own duty and VAT defaults (your duty_pct and vat_pct stay with this country; margins, freight and import costs carry over).… |
| country | string | yes | Target country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. |
| dealer_margin_pct | number | – | Dealer margin, % of its selling price (channel 'b2b_dealer', default 25). |
| description | string | – | Optional: the product's own name or a short description (e.g. '김스낵', 'seasoned seaweed snack'). Product traits in it pick the US duty line, e.g. seaweed snacks under HS 2008 are on the Section 301 ex… |
| distributor_margin_pct | number | – | Distributor margin, % of its selling price (channel 'distributor'). |
| duty_pct | number | – | Import duty % of CIF for your tariff line (default 0, except the US: 12.5 — the combined duty on most Korean goods since 24 Jul 2026, KORUS included — or, when item is given, that HS code's US rate:… |
| fob_krw | number | – | FOB price per unit in Korean won (e.g. 6000 for ₩6,000) when the user quotes in won: converted to USD at the European Central Bank reference rate, and the answer says the rate (converted). Never put… |
| fob_usd | number | – | FOB price per unit in USD. Give this, fob_krw, target_shelf_usd or target_shelf_local. |
| freight_pct | number | – | Freight + insurance as % of FOB (default 8). |
| fulfillment_usd | number | – | Fulfilment per unit in USD for marketplace sales (default 4). |
| import_costs_pct | number | – | Broker, port, inland and labelling as % of CIF (default 4). |
| importer_margin_pct | number | – | Importer margin, % of its selling price (channel b2b: the importer-distributor selling to the end user, default 30, 35 for medical devices; b2b_dealer: 15, or 20 for medical devices). |
| item | string | – | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
| marketplace_fee_pct | number | – | Marketplace referral fee % (default 15). |
| parcel_usd | number | – | Channel cross_border: courier from Korea to the customer's door per unit in USD (default 5, an assumption; use your courier's quote). |
| retail_margin_pct | number | – | Retailer margin, % of its selling price. |
| seller_margin_pct | number | – | Your margin on marketplace sales, % of price (default 25). |
| target_shelf_local | number | – | The same target in the market's own currency (e.g. 2500 for ¥2,500 on Qoo10 Japan, 19.99 for €19.99 in Germany); converted at the ECB reference rate. Use it instead of target_shelf_usd. |
| target_shelf_usd | number | – | Shelf price you want per unit in USD (incl. VAT where VAT applies; for the b2b channels the end-user price before VAT); returns the highest FOB that reaches it. |
| targets | string | – | Optional: several shelf prices in USD to compare, comma-separated (e.g. "19.99,24.99,29.99", up to 6) — returns fob_at_targets, the highest FOB for each with the same assumptions. Use competitors' sh… |
| vat_pct | number | – | Override the VAT/GST rate. |
No output schema declared.
No examples provided.
reply_pace Are my replies on track? ~1,540
Weekly pace check for one market: pass the buyers emailed so far (each buyer once, first emails only), the buyers who replied (any reply, a no counts) and, if known, the week of the 13-week schedule and how many replies were interested (warm). Call it first in the weekly routine and act on it before anything else: relay risk_note first when present (sanctions or export controls on that market), then status_text, advice (or decision_text once the target is reached) and send_this_week as they are; find_buyers_type is this week's buyer type and email_draft the first email to use (first_email or a key of gtm_plan first_email_variants); changed lists the changes made so far, to pass back next week; they agree with each other and with the web plan, and each gives one change to make, not a choice. Returns: status (one of too_early, no_replies, below, change_now, decision_moves, behind_schedule, normal_range, few_interested, above, on_track, or the decision next_market, change_and_retry, keep_going; on_track only when the current rate reaches 10 replies at the target, sends are on schedule and the interested share is not low), status_text, advice, send_this_week (new buyers to add this week: the catch-up number when more than a week behind; at next_market the first 200 in send_this_week_in), the rate Korean exporters of this product usually get there (the same industry × market rate as gtm_plan reply_target, from 2.2M real export emails), the normal range for that many sends (Poisson 5–95%), projected_replies_at_target, alternative_buyer_type, behind_schedule (weeks 2–12), decision_moves (week 13 or later before the target: the week to decide), and from 95% of sends_for_10_replies the decision with decision_text (fewer than 5 replies → next_market, named only then; 5–9 → same market once more, the next buyer type with a new subject line for retry_batch.send more, then 10 or more in total keeps going and fewer moves on; 10 or more → keep going). Pass exclude with markets al…
| Name | Type | Req | Description |
|---|---|---|---|
| bounced | integer | – | Optional: buyers whose email bounced. Over 10% of sent holds a market switch until the list is verified (reach_check list_problem). |
| buyer_type | string | – | Optional: the buyer type the user sent to last week (last week's find_buyers_type); after a switch to the next type the check keeps it. |
| changed | string | – | Optional: changes already made in earlier weeks, as last week's changed (comma-separated: next_type, new_subject, new_subject_2, offer, retry, retry_type). A change once made is kept: the same verdic… |
| concepts | string | – | Optional: the same concepts passed to gtm_plan (halal, vegan, derma …). |
| country | string | yes | Target country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. |
| description | string | – | Optional: the same product description passed to gtm_plan, so next_market follows the same ranking (entry_paths). |
| exclude | string | – | Optional: markets already tried, comma-separated ISO codes or names (e.g. 'DE,PL'), skipped when naming the next market. |
| item | string | yes | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
| last_replies | integer | – | Optional: last week's replies total (replies lower than last_replies is rejected). |
| last_sent | integer | – | Optional: last week's sent total, to catch this week's numbers passed instead of running totals (sent lower than last_sent is rejected). |
| meetings | integer | – | Optional: buyers who agreed to a meeting or a call. |
| opened | integer | – | Optional: of the buyers emailed, how many opened at least one email, as the user's email tool reports it (unique opens). Below the share of delivered emails people open in TradeGraph's data, the emai… |
| orders | integer | – | Optional: buyers who placed an order (trial orders count). An order keeps the market even with few replies (pipeline). |
| price_tier | string | – | Optional: the same price tier passed to gtm_plan. |
| quotes | integer | – | Optional: buyers who asked for prices or a quote. |
| replies | integer | yes | Buyers who replied so far (any reply, including a no). |
| samples | integer | – | Optional: buyers who asked for samples. |
| selling_in | string | – | Optional: the same selling_in passed to gtm_plan (markets where the product already sells). |
| sent | integer | yes | Buyers emailed so far in this market (count each buyer once; follow-ups don't add). |
| warm | integer | – | Optional: of the replies, how many were interested (a question, a sample request or a meeting; not a no). Compared with the usual interested share of replies; from 5 replies a low share adds warm_not… |
| week | integer | – | Optional: the week of the 13-week schedule they are in (1 = the week of the first 200 emails), to flag sends behind schedule or a decision that moves past week 13. |
No output schema declared.
No examples provided.
video_studio Short-form video ads for a market (Higgsfield-style presets) ~931
Plan AI product videos for one market and platform, Higgsfield-style: preset formats (hero orbit, texture macro, unboxing POV, 3-step routine, local lifestyle, AI presenter) with camera moves, a shot list, keyframe and image-to-video prompts, ready request bodies for treg.to video models (draft Seedance 1 Lite, standard Hailuo 2.3, premium Veo 3.1 Fast; HeyGen avatar for presenters), hook variants for A/B tests, the platform spec (aspect, length, safe zone), voice-over language, music, AI-label and claims rules, and the estimated cost. Starts from the real packshot so the pack never changes. It reads the product's rules in that market first: sale gates to clear before spending on ads (sale_gate, e.g. a US sunscreen is an OTC drug), the rules that bind ads there (ad_rules, with official sources) and wording in the product name, description, company record or your copy that does not fit them (claims_check: what to say instead), plus local_words for captions and hashtags; signed in, it uses the company's brand, valid certifications, origin and proof points (company). Free, read-only — generation runs on the user's treg token.
| Name | Type | Req | Description |
|---|---|---|---|
| copy | string | – | Optional: your own ad copy, captions, voice-over script or listing text for this market; claims_check flags wording that does not fit the market's rules and says what to use instead. |
| country | string | yes | Target country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. |
| description | string | – | Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the ru… |
| has_packshot | boolean | – | Whether a real product photo exists (default true). Without one the plan asks for it first. |
| item | string | – | Product as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2… |
| platform | string | – | Where the video runs; auto = the market's first creator platform. |
| preset | string | – | Video format; auto = three presets that suit the product group. |
| product | string | – | The product in plain English as it looks, e.g. 'vegan sunscreen SPF50, 50 ml white tube with green cap'. Used in every prompt. |
| tier | string | – | Model tier: draft (cheap 480p tests), standard (Hailuo 2.3 768P), premium (Veo 3.1 Fast 1080p). |
| traits | string | – | Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), co… |
| variants | integer | – | Hook variants per preset (A/B test the first 2 seconds). |
No output schema declared.
No examples provided.
How do I install the TradeGraph MCP server?
TradeGraph is a hosted endpoint at https://tradegraph.rinda.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 · tradegraph.rinda.ai
claude mcp add --transport http ai-rinda-tradegraph-tradegraph 'https://tradegraph.rinda.ai/mcp'
What is the TradeGraph MCP server?
TradeGraph is an MCP server listed in the public MCP registry as ai.rinda.tradegraph/tradegraph. An export sales team for consumer brands, inside your AI: markets, buyers, emails and pricing. This page covers its hosted endpoint (https://tradegraph.rinda.ai/mcp).
Is the TradeGraph MCP server safe to use?
TradeGraph scores 76 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 TradeGraph MCP server expose?
TradeGraph exposes 16 tools: gtm_plan, blind_spots, reply_pace, find_item, market_picks, and 11 more. Their descriptions and schemas cost roughly 10,907 tokens of context every time the server is loaded.
Does the TradeGraph MCP server require authentication?
No. We connected to TradeGraph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TradeGraph MCP server still maintained?
TradeGraph is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.