Registry-ready MCP

China market intelligence for AI agents

A narrow MCP surface for repeated China workflows where generic browsing is too fragile, too unstructured, or too difficult to budget at task level.

Explore capabilities Read docs

Three callable capability wrappers. One live registry-listed MCP server.

View registry listing

Live in MCP Registry streamable-http 3 capabilities decision-ready outputs x402-compatible

Example task

Run a China visibility check in one call

A compact example of the kind of repeatable task this MCP is built for: one narrow request, one decision-ready envelope, one clear next step.

Open docs View developer detail

{
  "tool": "brand_visibility_snapshot",
  "input": {
    "brand": "Example Brand",
    "market": "China"
  }
}

Returns in one response

where visibility is weak or missing

where signal is strongest

priority actions in one response

Why this surface exists

This is the shortest path from registry discovery to a usable, repeatable China intelligence task.

Structured China intelligence tasks are easier to automate than open-ended browsing loops.

Capability wrappers make cost and execution shape clearer than raw endpoint lists.

The output is designed to be decision-ready rather than just descriptive.

Flagship capabilities

Three wrappers at the center of the product surface

This layer packages capabilities rather than raw endpoint sprawl. Each wrapper is narrow, decision-ready, and directly usable in repeated China workflows.

orchestrated

Brand Visibility Snapshot

Diagnose where a brand is visible, weak, or missing across China-facing surfaces.

Useful when an agent needs one decision-ready read on discoverability, sentiment, and priority actions.

/v1/visibility/snapshot /v1/china/trends /v1/china/sentiment /v1/signals/brands/:brand_slug/snapshot

Capability: get_brand_visibility_snapshot
Execution: orchestrated
Typical wait: Up to 45s
Indicative price: $0.63

Use cases

Brand health checks
Competitive monitoring
Weekly visibility reviews

Input summary

Brand is required; category, scope, and context sharpen the read.

Output summary

Returns summary, score, strengths, gaps, actions, and source cues.

View capability See sample output

orchestrated

Destination Demand Snapshot

Read outbound China demand direction for one destination in one response.

Useful for destination, hospitality, and route-planning workflows that need a concise demand signal fast.

/v1/destination-demand/snapshot /v1/market-data/flights/summary /v1/market-data/spend/trends

Capability: get_destination_demand_snapshot
Execution: orchestrated
Typical wait: ~15s
Indicative price: $0.20

Use cases

Destination prioritisation
Travel monitoring
Market comparison

Input summary

Destination is required; window, segment, and origin market refine the signal.

Output summary

Returns direction, notable signals, risks, opportunities, and actions.

View capability See sample output

direct

KOL Shortlist

Generate a creator shortlist with rationale, risk flags, and next steps.

Useful for campaign planning when an agent needs candidate names and selection logic in one response.

/v1/kol/shortlist /v1/china/kols

Capability: get_kol_shortlist
Execution: direct
Typical wait: Up to 35s
Indicative price: $0.45

Use cases

Campaign planning
Creator discovery
Shortlist validation

Input summary

Brand and category are required; goal and platform focus tighten the shortlist.

Output summary

Returns candidate creators, rationale, risks, and next actions.

View capability See sample output

How it works with agents

A short path from discovery to a usable output

Built for repeated China workflows where stable input shape, predictable output, and clearer budgeting matter.

Discover

Registry discovery

Select

Capability selection

Call

Structured request

Receive

Decision-ready response

How it fits the site

How this fits the site

/mcp

Discover and use the capability surface

/agents

See task framing and workflow logic

/developers

Go deeper into routes, schemas, and payments

Why not just use search

A better fit for repeated workflows than generic browsing alone

This is not meant to replace broad search. It is meant to outperform it for repeated, narrow China workflows.

Measure

This MCP

Generic browsing

Output shape

Stable decision-ready envelopes with capability-level framing.

Flexible, but output shape often drifts.

Repeatability

Same recurring task maps to the same wrapper.

Prompting and evidence collection can vary by run.

Cost control

Per-task pricing is visible upfront.

Workflow-level budgeting is harder to predict.

Automation fit

Cleaner retries, branching, and downstream validation.

Often needs another parsing or cleanup step.

Workflow reliability

Clearer boundaries for input and output.

Open-ended flow is less reliable for repeated operational tasks.

Next steps

Choose the next layer based on the job you need to do

Explore capabilities

See the three flagship tasks, what they take in, and what they return.

Open capabilities

Read quickstart docs

Connect to the remote server, understand payment posture, and see first-call examples.

Open docs

View developer detail

Drop into route-level documentation when you need lower-level request and response contracts.

Open developer detail