Remote MCP · Endpoint

Mati Logistics — supplier sourcing MCP server

No. Mati Logistics — supplier sourcing answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.matilogistics.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.matilogistics/sourcing
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
216 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find suppliers ranked for fit across customs records, catalogues and directories
Listing
From the official MCP registry (active).
Recent checks of Mati Logistics — supplier sourcing
CheckedResultHandshake
1 hour agoHandshake completed216 ms
2 days agoHandshake completed132 ms
4 days agoHandshake completed129 ms
6 days agoHandshake completed105 ms
8 days agoHandshake completed215 ms
11 days agoHandshake completed87 ms
13 days agoHandshake completed81 ms
14 days agoHandshake completed78 ms
16 days agoHandshake completed142 ms
17 days agoHandshake completed104 ms
18 days agoHandshake completed103 ms
21 days agoHandshake completed81 ms
22 days agoHandshake completed114 ms
24 days agoHandshake completed112 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 Mati Logistics — supplier sourcing and makes no claim about it beyond what these checks measured.