Remote MCP · Endpoint

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

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

UpLast checked 2 hours 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
95 ms
Tools exposed
34 tools
Uptime, last 30 days
100% from 17 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
2 hours agoHandshake completed95 ms
2 days agoHandshake completed223 ms
4 days agoHandshake completed190 ms
5 days agoHandshake completed108 ms
7 days agoHandshake completed239 ms
8 days agoHandshake completed97 ms
9 days agoHandshake completed109 ms
12 days agoHandshake completed105 ms
13 days agoHandshake completed107 ms
15 days agoHandshake completed100 ms
17 days agoHandshake completed119 ms
18 days agoHandshake completed117 ms
19 days agoHandshake completed108 ms
20 days agoHandshake completed104 ms
20 days agoHandshake completed106 ms
21 days agoHandshake completed99 ms
23 days agoHandshake completed105 ms

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

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.