mcpbeat Sign in

SCModeling MCP Server

by scmodeling Your server? Claim it
answering

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

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

Uptime history 48 days of history
48 days agonow
100.0%
Uptime 24h
92 of 92 checks
12
Tools
read from the server
275 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 4

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

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 1 more, back to 11 September 2026

Nothing serious here today

Today is the operative word: we check SCModeling every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 3 min ago.

run in your terminal
claude mcp add public --transport http https://scmodeling.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "public": {
      "url": "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
{
  "mcpServers": {
    "public": {
      "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
Reference text on greenfield analysis — clean-slate facility-location math. Covers the weighted center-of-gravity (Weber) formulation, Weiszfeld's iterative algorithm, Lloyd's-style alternating location-allocation for N facilities, service constraints (% demand vs % customers within a distance band), and the inverse problem of solving for minimum N. Also covers when to use greenfield vs facility selection (the open/close MIP). Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does greenfield analysis work' or 'where would I put my DCs' question. ChiAha's GreenfieldAnalysis engine powers the US Greenfield Design demo on the sandbox.
explain_optimization
Reference text on supply-chain network optimization — mixed-integer programming (MIP), the structure of decision variables and constraints, the objective function for landed-cost minimization, and the common problem classes (facility selection, sourcing, flow constraints, multi-period, BOM/production, multi-objective). Also covers when to reach for optimization vs simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does network optimization work' question. ChiAha's AMOS optimizer (open-source, Odin, GLOP/CBC via OR-Tools) powers the Tariff and Coffee Co-pack demos on the sandbox.
explain_simulation
Reference text on supply-chain simulation — how a discrete-event model of a network behaves through time. Covers event-driven execution (future-event list, the consume / check-inventory / place-order / fill / ship / deliver vocabulary), why inventory POSITION rather than on-hand stock drives reordering, which KPIs the engine reports versus which this site derives from the raw order and shipment records, when to reach for simulation, for optimization, and for both together, and the honest limitations of these runs (single deterministic replication, cached results, warm-up inside the reported window, fixed sample parameters). Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does the simulation work', 'why did this DC stock out', or 'should I simulate or optimize' question rather than asking for a number; call run_simulation when they want actual figures.
describe
describe_greenfield_demo
Full detail on one greenfield demo — region, customer count, available dc_count values, and the score-curve elbow finding. Use this before get_greenfield_result to know what dc_count values are precomputed.
describe_opt_demo
Full detail on one optimization demo — controls, available scenario keys, sites, fixed parameters, citations, and the key finding the demo illustrates. Use this before get_opt_result to know what scenario_key values are accepted.
greenfield
get_greenfield_result
Get the precomputed result for one DC count of a greenfield demo. Returns sited DCs (lat/lon + city/state, nearest-city snapped), customer-to-DC assignments, and the score for that DC count. ANTI-FABRICATION: every result is verbatim engine output from greenfield-cli — quote them in your reply, do not round or fabricate cities.
list_greenfield_demos
List the bundled SCModeling greenfield demos. Returns id + label + one-line summary. Currently one demo (US, 189 customer points). Use this before describe_greenfield_demo or get_greenfield_result.
opt
get_opt_result
Get the precomputed result for one scenario of an optimization demo. Returns the verbatim engine output JSON (AMOS for tariff/coffee, SSO output for sso-basic) including the optimal sourcing/production/transport decisions, costs, and any open/close facility variables. ANTI-FABRICATION: every numeric result is verbatim from the optimization engine that ran offline — quote them in your reply, do not round or recompute. Call describe_opt_demo first to learn valid scenario_key formats for each demo.
list_opt_demos
List the bundled SCModeling optimization demos. Returns id + label + one-line summary for each (Tariff, Coffee Co-pack, SSO Basic). Use this before describe_opt_demo or get_opt_result to know which demo_id values are valid. All demos are precomputed sample-only fixtures — for optimization on real client data, the SCModeling desktop tool is the product.
models
list_models
List the bundled SCModeling sample supply-chain models. Returns a catalog with each model's id and a short description. Use this before run_simulation to know which model_id values are valid.
simulation
run_simulation
Run a supply-chain simulation on a bundled SCModeling sample model (sdi-db). Returns metrics, inventory time-series, orders, shipments, routing and BOM. ANTI-FABRICATION: the returned numbers come from a real discrete-event simulation run on the sc-sim engine. Quote them VERBATIM in your reply. Do not round, estimate, average, or compute derived figures from training-data recall. If the user asks a follow-up about the same model, re-call this tool rather than recalling numbers from earlier in the conversation.
theory
get_sc_theory
Reference guide to supply-chain simulation concepts: ordering policies, BOM, FDD formulas, event-driven simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does this work' question rather than asking for a number.

Endpoints

URLTransportStateLatencyChecked
https://scmodeling.com/mcp streamable-http answering 286 ms 3 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

72 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.

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

MCP server for Boolean network simulation and attractor analysis using MaBoSS

local only
Dingdawg Data Agent
by dingdawg

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

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

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

61 installs/wk local only
AgentSUMO
by mw-jeong

MCP server for LLM-driven SUMO traffic simulation, scenario design, and result analysis.

83 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 275 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 with the file path 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 275 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.