mcpbeat Sign in

SCModeling MCP Server

by scmodeling Your server? Claim it
answering

SCModeling is answering right now. Last checked 2 min ago. It exposes 12 tools.

Supply-chain network design via simulation, optimization, and greenfield analysis.

Uptime history 91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
12
Tools
read from the server
301 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 31

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 September 2026. No other catalogue keeps this.

7 Nov a tool changed version5 times that day
5 Nov a tool changed version4 times that day
4 Nov 12 tool descriptions were rewritten describe_greenfield_demo, describe_opt_demo, explain_greenfield and 9 more
4 Nov 5 tools changed the parameters they ask for describe_greenfield_demo, describe_opt_demo, get_greenfield_result and 2 more
4 Nov a tool changed version
18 Sep a tool appeared explain_simulation
15 Sep a tool changed the parameters it asks for run_simulation
11 Sep a tool changed the parameters it asks for2 times that day run_simulation
and 8 more, back to 11 September 2026

SCModeling does not always answer

Over the last week it answered 48.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add public --transport http https://scmodeling.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://scmodeling.com/mcp
~/.codex/config.toml
[mcp_servers.public]
url = "https://scmodeling.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "public": {
      "url": "https://scmodeling.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "public": {
      "type": "http",
      "url": "https://scmodeling.com/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

explain
explain_greenfield
Primer on greenfield analysis: center-of-gravity (Weber) siting, Weiszfeld's algorithm, location-allocation for N facilities, service constraints, and when to use greenfield versus facility selection. Static text.
explain_optimization
Primer on supply chain network optimization: mixed-integer programming, decision variables and constraints, landed-cost objectives, the common problem classes, and when to optimize versus simulate. Static text.
explain_simulation
Primer on supply chain simulation: when to simulate, optimize or both, how a discrete-event network model works, which numbers the engine reports, and the limits of a single run. Static text; call run_simulation for figures.
describe
describe_greenfield_demo
Detail on one greenfield demo: region, customer count, the saved DC counts and the score curve. Use before get_greenfield_result.
describe_opt_demo
Detail on one optimization demo: what it shows, its source, and every saved scenario key. Use before get_opt_result.
greenfield
get_greenfield_result
Return the saved greenfield result for one DC count, verbatim: the sited DCs (lat/lon, nearest city) and which customers each serves. Quote the numbers verbatim.
list_greenfield_demos
List the saved greenfield siting demos with an id and summary each. Use before describe_greenfield_demo or get_greenfield_result.
opt
get_opt_result
Return the saved optimization result for one scenario of a demo, verbatim: sourcing, production and transport decisions, costs, and facility open/close decisions. Call describe_opt_demo first for the valid scenario keys. Quote the numbers verbatim.
list_opt_demos
List the saved optimization demos (Tariff sourcing, Coffee co-pack siting, Safety Stock Optimization) with an id and summary each. Use before describe_opt_demo or get_opt_result.
models
list_models
List the sample supply chain models run_simulation has a saved engine run for, with each model's id and a short description.
simulation
run_simulation
Return the saved SC Builder engine run of a sample supply chain model: metrics, orders, shipments, routing and inventory series, verbatim. This server runs no engine; a model without a saved run answers 'not available here'. Quote the numbers verbatim.
theory
get_sc_theory
Reference text from the SC Builder engine: event-driven model, ordering policies (pull, push, planned), the forecast-demand and order-point formulas, bill of materials, routing and supplier selection. Static text.

Endpoints

URLTransportStateLatencyChecked
https://scmodeling.com/mcp streamable-http answering 326 ms 2 min ago

Alternatives to SCModeling

same job, measured the same way
RASON
by frontlinesystems

Build, solve, and analyze RASON optimization, simulation, data science, and decision models

64 installs/wk local only
3DOptix
by 3doptix

Optical design, simulation and analysis with GPU-powered ray tracing. Import from Zemax and CAD.

answering
LensHH-LT Optical Design
by synapseoptics

Drive real optical lens design: ray tracing, optimization, MTF and aberration analysis.

local only
EPANET MCP Server
by applied-artificial-intelligence-eurecat

MCP server for EPANET water-distribution network simulation and scenario analysis.

147 installs/wk local only
MaBoSS Boolean Network Simulator
by marcorusc

MCP server for Boolean network simulation and attractor analysis using MaBoSS

local only
Dock Optimizer
by dockoptimizer

Supply chain operations: dock scheduling, check-in, doors, inventory, orders and freight.

answering
Dingdawg Data Agent
by dingdawg

AI data agent — schema analysis, query optimization, PII detection, pipelines.

55 installs/wk local only
Systemonomic — Work Domain Analysis & AI Task Suitability
by tonyc23

Model work domains, score tasks for AI suitability, and design organisations.

106 installs/wk local only

SCModeling — questions

Answers built from our own checks of this server.

What can SCModeling do?
It exposes 12 tools, read directly from the server on our last check. Among them: describe_greenfield_demo, describe_opt_demo, explain_greenfield, explain_optimization, explain_simulation, get_greenfield_result and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is SCModeling mostly used for?
Its tools cluster around explain, greenfield and opt. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is SCModeling working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 301 ms. The bar chart above shows every period we have measured.
How do I connect SCModeling?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does SCModeling need an API key?
No. SCModeling completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SCModeling?
It answers our handshake in 301 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.