Remote MCP · Endpoint

SCModeling MCP server

No. SCModeling answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://scmodeling.com/mcp

The last check completed an MCP handshake.

Registry name
com.scmodeling/public
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
38 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Supply-chain network design via simulation, optimization, and greenfield analysis.
Listing
From the official MCP registry (active).
Recent checks of SCModeling
CheckedResultHandshake
1 hour agoHandshake completed38 ms
2 days agoHandshake completed39 ms
4 days agoHandshake completed4.46 s
5 days agoHandshake completed4.83 s
7 days agoHandshake completed45 ms
8 days agoHandshake completed49 ms
9 days agoHandshake completed37 ms
12 days agoHandshake completed100 ms
13 days agoHandshake completed68 ms
15 days agoHandshake completed3.67 s
16 days agoHandshake completed101 ms
18 days agoHandshake completed55 ms
19 days agoHandshake completed73 ms
20 days agoHandshake completed31 ms
20 days agoHandshake completed34 ms
21 days agoHandshake completed27 ms
22 days agoHandshake completed41 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 SCModeling and makes no claim about it beyond what these checks measured.