Remote MCP · Endpoint

Trade Intelligence MCP server

No. Trade Intelligence answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://standardtrade.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.Standard-Trade/trade-evidence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
453 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Background checks on Chinese factories: is it real, can it meet your specs, who does it ship to?
Listing
From the official MCP registry (active).
Recent checks of Trade Intelligence
CheckedResultHandshake
52 minutes agoHandshake completed453 ms
3 days agoHandshake completed113 ms
12 days agoHandshake completed195 ms
13 days agoHandshake completed154 ms
14 days agoHandshake completed487 ms
15 days agoHandshake completed133 ms
17 days agoHandshake completed135 ms
18 days agoHandshake completed130 ms
18 days agoHandshake completed89 ms
20 days agoHandshake completed318 ms
22 days agoHandshake completed100 ms
25 days agoHandshake completed292 ms
27 days agoHandshake completed390 ms
29 days agoHandshake completed153 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Trade Intelligence and makes no claim about it beyond what these checks measured.