Remote MCP · Endpoint

io.github.SupplyMaven-SCR/supply-chain-intelligence MCP server

No. io.github.SupplyMaven-SCR/supply-chain-intelligence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://supplymaven.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.SupplyMaven-SCR/supply-chain-intelligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
130 ms
Tools exposed
34 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Real-time supply chain risk intelligence — 24 tools, proprietary indices, predictive signals
Listing
From the official MCP registry (active).
Recent checks of io.github.SupplyMaven-SCR/supply-chain-intelligence
CheckedResultHandshake
1 hour agoHandshake completed130 ms
1 day agoHandshake completed113 ms
2 days agoHandshake completed141 ms
3 days agoHandshake completed107 ms
4 days agoHandshake completed158 ms
5 days agoHandshake completed324 ms
6 days agoHandshake completed159 ms
9 days agoHandshake completed141 ms
11 days agoHandshake completed679 ms
14 days agoHandshake completed132 ms
16 days agoHandshake completed98 ms
18 days agoHandshake completed92 ms
20 days agoHandshake completed95 ms
22 days agoHandshake completed223 ms
24 days agoHandshake completed190 ms
26 days agoHandshake completed108 ms
27 days agoHandshake completed239 ms
29 days agoHandshake completed97 ms

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

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 io.github.SupplyMaven-SCR/supply-chain-intelligence and makes no claim about it beyond what these checks measured.